REVIEW: http://review.gluster.org/12850 (tier/libgfdb/sql: Correcting logic in sql query for read) posted (#1) for review on master by Joseph Fernandes

REVIEW: http://review.gluster.org/12855 (tier/libgfdb/sql: Correcting logic in sql query for read) posted (#1) for review on release-3.7 by Joseph Fernandes

REVIEW: http://review.gluster.org/12855 (tier/libgfdb/sql: Correcting logic in sql query for read) posted (#2) for review on release-3.7 by Joseph Fernandes

REVIEW: http://review.gluster.org/12868 (tier/libgfdb/sql: Correcting logic in sql query for read) posted (#1) for review on release-3.7 by Joseph Fernandes

COMMIT: http://review.gluster.org/12868 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit d5df0db18b29b1db2577ac5ed388966c0eb203b0
Author: Joseph Fernandes <josferna>
Date:   Mon Nov 30 16:51:35 2015 +0530

    tier/libgfdb/sql: Correcting logic in sql query for read
    
    Correcting query in the  where clause
    
    from "a & b | c"
    
    to "a & (b | c)"
    
    where "a" is the condition to join the gf_file_tb and gf_flink_tb
    through gfids
    
    "b" is the condition for the write heat
    and "c" is the condition for read heat
    
    Backport of http://review.gluster.org/12823
    
    > Change-Id: I99226d82b0efb68fbef3a40f02b215bb2b4370d6
    > BUG: 1286656
    > Signed-off-by: Joseph Fernandes <josferna>
    > Signed-off-by: Dan Lambright <dlambrig>
    > Reviewed-on: http://review.gluster.org/12823
    > Tested-by: NetBSD Build System <jenkins.org>
    > Tested-by: Gluster Build System <jenkins.com>
    Signed-off-by: Joseph Fernandes <josferna>
    
    Change-Id: I70533c8589a6cd67e8737e110af0a23abed9013d
    BUG: 1287583
    Reviewed-on: http://review.gluster.org/12868
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>
    Tested-by: Dan Lambright <dlambrig>

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.7, please open a new bug report.

glusterfs-3.7.7 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user