[jira] [Updated] (HBASE-13491) Issue in FuzzyRowFilter#getNextForFuzzyRule
[
https://issues.apache.org/jira/browse/HBASE-13491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-13491:
Fix Version/s: (was: 1.2.0)
Issue in FuzzyRowFilter#getNextForFuzzyRule
---
Key: HBASE-13491
URL: https://issues.apache.org/jira/browse/HBASE-13491
Project: HBase
Issue Type: Bug
Components: Filters
Affects Versions: 1.0.0
Reporter: Anoop Sam John
Assignee: Anoop Sam John
Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.13
Attachments: HBASE-13491-branch-1.1.patch,
HBASE-13491-branch-1.1.patch, HBASE-13491.patch
{code}
for (int i = 0; i result.length; i++) {
if (i = fuzzyKeyMeta.length || fuzzyKeyMeta[i] == 1) {
result[i] = row[offset + i];
if (!order.isMax(row[i])) {
// this is non-fixed position and is not at max value, hence we
can increase it
toInc = i;
}
}
{code}
See we take row bytes with out considering the row offset. The test cases
are passing as we pass 0 offset row bytes. Change in the test will reveal the
bug.
Came across this when I was working on HBASE-11425
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13491) Issue in FuzzyRowFilter#getNextForFuzzyRule
[
https://issues.apache.org/jira/browse/HBASE-13491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-13491:
---
Fix Version/s: 0.98.13
Cherry picked to 0.98.
Issue in FuzzyRowFilter#getNextForFuzzyRule
---
Key: HBASE-13491
URL: https://issues.apache.org/jira/browse/HBASE-13491
Project: HBase
Issue Type: Bug
Components: Filters
Affects Versions: 1.0.0
Reporter: Anoop Sam John
Assignee: Anoop Sam John
Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.13, 1.2.0
Attachments: HBASE-13491-branch-1.1.patch,
HBASE-13491-branch-1.1.patch, HBASE-13491.patch
{code}
for (int i = 0; i result.length; i++) {
if (i = fuzzyKeyMeta.length || fuzzyKeyMeta[i] == 1) {
result[i] = row[offset + i];
if (!order.isMax(row[i])) {
// this is non-fixed position and is not at max value, hence we
can increase it
toInc = i;
}
}
{code}
See we take row bytes with out considering the row offset. The test cases
are passing as we pass 0 offset row bytes. Change in the test will reveal the
bug.
Came across this when I was working on HBASE-11425
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13491) Issue in FuzzyRowFilter#getNextForFuzzyRule
[
https://issues.apache.org/jira/browse/HBASE-13491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John updated HBASE-13491:
---
Attachment: HBASE-13491.patch
Issue in FuzzyRowFilter#getNextForFuzzyRule
---
Key: HBASE-13491
URL: https://issues.apache.org/jira/browse/HBASE-13491
Project: HBase
Issue Type: Bug
Components: Filters
Reporter: Anoop Sam John
Assignee: Anoop Sam John
Attachments: HBASE-13491.patch
{code}
for (int i = 0; i result.length; i++) {
if (i = fuzzyKeyMeta.length || fuzzyKeyMeta[i] == 1) {
result[i] = row[offset + i];
if (!order.isMax(row[i])) {
// this is non-fixed position and is not at max value, hence we
can increase it
toInc = i;
}
}
{code}
See we take row bytes with out considering the row offset. The test cases
are passing as we pass 0 offset row bytes. Change in the test will reveal the
bug.
Came across this when I was working on HBASE-11425
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13491) Issue in FuzzyRowFilter#getNextForFuzzyRule
[
https://issues.apache.org/jira/browse/HBASE-13491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John updated HBASE-13491:
---
Status: Patch Available (was: Open)
Issue in FuzzyRowFilter#getNextForFuzzyRule
---
Key: HBASE-13491
URL: https://issues.apache.org/jira/browse/HBASE-13491
Project: HBase
Issue Type: Bug
Components: Filters
Reporter: Anoop Sam John
Assignee: Anoop Sam John
Attachments: HBASE-13491.patch
{code}
for (int i = 0; i result.length; i++) {
if (i = fuzzyKeyMeta.length || fuzzyKeyMeta[i] == 1) {
result[i] = row[offset + i];
if (!order.isMax(row[i])) {
// this is non-fixed position and is not at max value, hence we
can increase it
toInc = i;
}
}
{code}
See we take row bytes with out considering the row offset. The test cases
are passing as we pass 0 offset row bytes. Change in the test will reveal the
bug.
Came across this when I was working on HBASE-11425
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13491) Issue in FuzzyRowFilter#getNextForFuzzyRule
[
https://issues.apache.org/jira/browse/HBASE-13491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John updated HBASE-13491:
---
Affects Version/s: 1.0.0
Issue in FuzzyRowFilter#getNextForFuzzyRule
---
Key: HBASE-13491
URL: https://issues.apache.org/jira/browse/HBASE-13491
Project: HBase
Issue Type: Bug
Components: Filters
Affects Versions: 1.0.0
Reporter: Anoop Sam John
Assignee: Anoop Sam John
Attachments: HBASE-13491.patch
{code}
for (int i = 0; i result.length; i++) {
if (i = fuzzyKeyMeta.length || fuzzyKeyMeta[i] == 1) {
result[i] = row[offset + i];
if (!order.isMax(row[i])) {
// this is non-fixed position and is not at max value, hence we
can increase it
toInc = i;
}
}
{code}
See we take row bytes with out considering the row offset. The test cases
are passing as we pass 0 offset row bytes. Change in the test will reveal the
bug.
Came across this when I was working on HBASE-11425
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13491) Issue in FuzzyRowFilter#getNextForFuzzyRule
[
https://issues.apache.org/jira/browse/HBASE-13491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John updated HBASE-13491:
---
Fix Version/s: 1.2.0
1.1.0
1.0.1
2.0.0
Issue in FuzzyRowFilter#getNextForFuzzyRule
---
Key: HBASE-13491
URL: https://issues.apache.org/jira/browse/HBASE-13491
Project: HBase
Issue Type: Bug
Components: Filters
Affects Versions: 1.0.0
Reporter: Anoop Sam John
Assignee: Anoop Sam John
Fix For: 2.0.0, 1.0.1, 1.1.0, 1.2.0
Attachments: HBASE-13491.patch
{code}
for (int i = 0; i result.length; i++) {
if (i = fuzzyKeyMeta.length || fuzzyKeyMeta[i] == 1) {
result[i] = row[offset + i];
if (!order.isMax(row[i])) {
// this is non-fixed position and is not at max value, hence we
can increase it
toInc = i;
}
}
{code}
See we take row bytes with out considering the row offset. The test cases
are passing as we pass 0 offset row bytes. Change in the test will reveal the
bug.
Came across this when I was working on HBASE-11425
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13491) Issue in FuzzyRowFilter#getNextForFuzzyRule
[
https://issues.apache.org/jira/browse/HBASE-13491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-13491:
-
Attachment: HBASE-13491-branch-1.1.patch
Trying out the pre-commit job for branch-1.1.
Issue in FuzzyRowFilter#getNextForFuzzyRule
---
Key: HBASE-13491
URL: https://issues.apache.org/jira/browse/HBASE-13491
Project: HBase
Issue Type: Bug
Components: Filters
Affects Versions: 1.0.0
Reporter: Anoop Sam John
Assignee: Anoop Sam John
Fix For: 2.0.0, 1.0.1, 1.1.0, 1.2.0
Attachments: HBASE-13491-branch-1.1.patch, HBASE-13491.patch
{code}
for (int i = 0; i result.length; i++) {
if (i = fuzzyKeyMeta.length || fuzzyKeyMeta[i] == 1) {
result[i] = row[offset + i];
if (!order.isMax(row[i])) {
// this is non-fixed position and is not at max value, hence we
can increase it
toInc = i;
}
}
{code}
See we take row bytes with out considering the row offset. The test cases
are passing as we pass 0 offset row bytes. Change in the test will reveal the
bug.
Came across this when I was working on HBASE-11425
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13491) Issue in FuzzyRowFilter#getNextForFuzzyRule
[
https://issues.apache.org/jira/browse/HBASE-13491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-13491:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
I have committed this. Thanks Anoop.
Issue in FuzzyRowFilter#getNextForFuzzyRule
---
Key: HBASE-13491
URL: https://issues.apache.org/jira/browse/HBASE-13491
Project: HBase
Issue Type: Bug
Components: Filters
Affects Versions: 1.0.0
Reporter: Anoop Sam John
Assignee: Anoop Sam John
Fix For: 2.0.0, 1.0.1, 1.1.0, 1.2.0
Attachments: HBASE-13491-branch-1.1.patch,
HBASE-13491-branch-1.1.patch, HBASE-13491.patch
{code}
for (int i = 0; i result.length; i++) {
if (i = fuzzyKeyMeta.length || fuzzyKeyMeta[i] == 1) {
result[i] = row[offset + i];
if (!order.isMax(row[i])) {
// this is non-fixed position and is not at max value, hence we
can increase it
toInc = i;
}
}
{code}
See we take row bytes with out considering the row offset. The test cases
are passing as we pass 0 offset row bytes. Change in the test will reveal the
bug.
Came across this when I was working on HBASE-11425
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13491) Issue in FuzzyRowFilter#getNextForFuzzyRule
[
https://issues.apache.org/jira/browse/HBASE-13491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John updated HBASE-13491:
---
Attachment: HBASE-13491-branch-1.1.patch
Issue in FuzzyRowFilter#getNextForFuzzyRule
---
Key: HBASE-13491
URL: https://issues.apache.org/jira/browse/HBASE-13491
Project: HBase
Issue Type: Bug
Components: Filters
Affects Versions: 1.0.0
Reporter: Anoop Sam John
Assignee: Anoop Sam John
Fix For: 2.0.0, 1.0.1, 1.1.0, 1.2.0
Attachments: HBASE-13491-branch-1.1.patch,
HBASE-13491-branch-1.1.patch, HBASE-13491.patch
{code}
for (int i = 0; i result.length; i++) {
if (i = fuzzyKeyMeta.length || fuzzyKeyMeta[i] == 1) {
result[i] = row[offset + i];
if (!order.isMax(row[i])) {
// this is non-fixed position and is not at max value, hence we
can increase it
toInc = i;
}
}
{code}
See we take row bytes with out considering the row offset. The test cases
are passing as we pass 0 offset row bytes. Change in the test will reveal the
bug.
Came across this when I was working on HBASE-11425
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
