You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2008/08/04 08:53:44 UTC
[jira] Created: (HBASE-793) HTable.getStartKeys() ignores table
names when matching columns
HTable.getStartKeys() ignores table names when matching columns
---------------------------------------------------------------
Key: HBASE-793
URL: https://issues.apache.org/jira/browse/HBASE-793
Project: Hadoop HBase
Issue Type: Bug
Components: mapred
Affects Versions: 0.2.0
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 0.2.0
Dru Jensen wrote on hbase-user@
> I found what is causing the same rows being sent to multiple map tasks.
> If you have the same column family name in other tables, the Test will
> send the same rows to multiple map reducers.
Stack wrote in response:
> Indeed, a bug in getStartKeys will make us process all tables that have
> a column family name in common.
[...]
> The above Visitor is visiting the meta table. Its checking column
> family name. Any region that is not offlined or split gets added to the
> list of regions. Its not checking that the region belongs to the wanted
> table.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-793) HTable.getStartKeys() ignores table
names when matching columns
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-793:
---------------------------------
Status: Patch Available (was: Open)
Patch attached. Passes all tests:
[mkdir] Created dir: /usr/src/Hadoop/hbase/build/test/logs
[junit] Running org.apache.hadoop.hbase.TestClassMigration
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.077 sec
[junit] Running org.apache.hadoop.hbase.TestCompare
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.021 sec
[junit] Running org.apache.hadoop.hbase.TestEmptyMetaInfo
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 32.513 sec
[junit] Running org.apache.hadoop.hbase.TestGlobalMemcacheLimit
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 49.011 sec
[junit] Running org.apache.hadoop.hbase.TestHBaseCluster
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 41.314 sec
[junit] Running org.apache.hadoop.hbase.TestInfoServers
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 15.607 sec
[junit] Running org.apache.hadoop.hbase.TestMasterAdmin
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 24.418 sec
[junit] Running org.apache.hadoop.hbase.TestMergeMeta
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 42.511 sec
[junit] Running org.apache.hadoop.hbase.TestMergeTable
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 29.667 sec
[junit] Running org.apache.hadoop.hbase.TestRegionRebalancing
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 58.732 sec
[junit] Running org.apache.hadoop.hbase.TestScanMultipleVersions
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 19.332 sec
[junit] Running org.apache.hadoop.hbase.TestScannerAPI
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 19.325 sec
[junit] Running org.apache.hadoop.hbase.TestSerialization
[junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.311 sec
[junit] Running org.apache.hadoop.hbase.TestTable
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 406.798 sec
[junit] Running org.apache.hadoop.hbase.TestToString
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.046 sec
[junit] Running org.apache.hadoop.hbase.client.TestBatchUpdate
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 385.186 sec
[junit] Running org.apache.hadoop.hbase.client.TestHTable
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 74.031 sec
[junit] Running org.apache.hadoop.hbase.client.TestListTables
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 28.258 sec
[junit] Running org.apache.hadoop.hbase.client.TestScannerTimes
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 21.383 sec
[junit] Running org.apache.hadoop.hbase.client.TestTimestamp
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 19.354 sec
[junit] Running org.apache.hadoop.hbase.filter.TestInclusiveStopRowFilter
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.01 sec
[junit] Running org.apache.hadoop.hbase.filter.TestPageRowFilter
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.02 sec
[junit] Running org.apache.hadoop.hbase.filter.TestRegExpRowFilter
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.025 sec
[junit] Running org.apache.hadoop.hbase.filter.TestRowFilterAfterWrite
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 24.204 sec
[junit] Running org.apache.hadoop.hbase.filter.TestRowFilterOnMultipleFamilies
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 19.355 sec
[junit] Running org.apache.hadoop.hbase.filter.TestRowFilterSet
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.092 sec
[junit] Running org.apache.hadoop.hbase.filter.TestStopRowFilter
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.008 sec
[junit] Running org.apache.hadoop.hbase.filter.TestWhileMatchRowFilter
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.013 sec
[junit] Running org.apache.hadoop.hbase.io.TestHbaseObjectWritable
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.094 sec
[junit] Running org.apache.hadoop.hbase.mapred.TestTableIndex
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 37.092 sec
[junit] Running org.apache.hadoop.hbase.mapred.TestTableMapReduce
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 41.634 sec
[junit] Running org.apache.hadoop.hbase.regionserver.TestBloomFilters
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 29.346 sec
[junit] Running org.apache.hadoop.hbase.regionserver.TestCompaction
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 12.23 sec
[junit] Running org.apache.hadoop.hbase.regionserver.TestDeleteAll
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 5.149 sec
[junit] Running org.apache.hadoop.hbase.regionserver.TestDeleteFamily
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4.8 sec
[junit] Running org.apache.hadoop.hbase.regionserver.TestGet
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 11.252 sec
[junit] Running org.apache.hadoop.hbase.regionserver.TestGet2
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 28.702 sec
[junit] Running org.apache.hadoop.hbase.regionserver.TestHLog
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 15.949 sec
[junit] Running org.apache.hadoop.hbase.regionserver.TestHMemcache
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.321 sec
[junit] Running org.apache.hadoop.hbase.regionserver.TestHRegion
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 12.309 sec
[junit] Running org.apache.hadoop.hbase.regionserver.TestHRegionInfo
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.122 sec
[junit] Running org.apache.hadoop.hbase.regionserver.TestHStoreFile
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 17.201 sec
[junit] Running org.apache.hadoop.hbase.regionserver.TestLogRolling
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 58.354 sec
[junit] Running org.apache.hadoop.hbase.regionserver.TestScanner
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 5.271 sec
[junit] Running org.apache.hadoop.hbase.regionserver.TestSplit
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 30.478 sec
[junit] Running org.apache.hadoop.hbase.regionserver.TestTimestamp
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 27.111 sec
[junit] Running org.apache.hadoop.hbase.util.TestBase64
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.067 sec
[junit] Running org.apache.hadoop.hbase.util.TestKeying
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.007 sec
[junit] Running org.apache.hadoop.hbase.util.TestMergeTool
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 19.225 sec
[junit] Running org.apache.hadoop.hbase.util.TestMigrate
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 33.421 sec
[junit] Running org.apache.hadoop.hbase.util.TestRootPath
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.014 sec
[junit] Running org.onelab.test.TestFilter
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.031 sec
BUILD SUCCESSFUL
Total time: 28 minutes 44 seconds
> HTable.getStartKeys() ignores table names when matching columns
> ---------------------------------------------------------------
>
> Key: HBASE-793
> URL: https://issues.apache.org/jira/browse/HBASE-793
> Project: Hadoop HBase
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.2.0
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.2.0
>
> Attachments: 0.2.0-793.patch
>
>
> Dru Jensen wrote on hbase-user@
> > I found what is causing the same rows being sent to multiple map tasks.
> > If you have the same column family name in other tables, the Test will
> > send the same rows to multiple map reducers.
> Stack wrote in response:
> > Indeed, a bug in getStartKeys will make us process all tables that have
> > a column family name in common.
> [...]
> > The above Visitor is visiting the meta table. Its checking column
> > family name. Any region that is not offlined or split gets added to the
> > list of regions. Its not checking that the region belongs to the wanted
> > table.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-793) HTable.getStartKeys() ignores table
names when matching columns
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-793:
---------------------------------
Attachment: 0.2.0-793.patch
> HTable.getStartKeys() ignores table names when matching columns
> ---------------------------------------------------------------
>
> Key: HBASE-793
> URL: https://issues.apache.org/jira/browse/HBASE-793
> Project: Hadoop HBase
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.2.0
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.2.0
>
> Attachments: 0.2.0-793.patch
>
>
> Dru Jensen wrote on hbase-user@
> > I found what is causing the same rows being sent to multiple map tasks.
> > If you have the same column family name in other tables, the Test will
> > send the same rows to multiple map reducers.
> Stack wrote in response:
> > Indeed, a bug in getStartKeys will make us process all tables that have
> > a column family name in common.
> [...]
> > The above Visitor is visiting the meta table. Its checking column
> > family name. Any region that is not offlined or split gets added to the
> > list of regions. Its not checking that the region belongs to the wanted
> > table.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-793) HTable.getStartKeys() ignores table
names when matching columns
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-793:
------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks Andrew for the patch (and Dru for figuring the bug). Committed.
> HTable.getStartKeys() ignores table names when matching columns
> ---------------------------------------------------------------
>
> Key: HBASE-793
> URL: https://issues.apache.org/jira/browse/HBASE-793
> Project: Hadoop HBase
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.2.0
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.2.0
>
> Attachments: 0.2.0-793.patch
>
>
> Dru Jensen wrote on hbase-user@
> > I found what is causing the same rows being sent to multiple map tasks.
> > If you have the same column family name in other tables, the Test will
> > send the same rows to multiple map reducers.
> Stack wrote in response:
> > Indeed, a bug in getStartKeys will make us process all tables that have
> > a column family name in common.
> [...]
> > The above Visitor is visiting the meta table. Its checking column
> > family name. Any region that is not offlined or split gets added to the
> > list of regions. Its not checking that the region belongs to the wanted
> > table.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.