You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2009/11/11 07:20:27 UTC
[jira] Created: (HBASE-1970) Export does one version only; make it
configurable how many it does
Export does one version only; make it configurable how many it does
-------------------------------------------------------------------
Key: HBASE-1970
URL: https://issues.apache.org/jira/browse/HBASE-1970
Project: Hadoop HBase
Issue Type: Improvement
Reporter: stack
Priority: Trivial
Attachments: allversions.patch
I was playing with Export to backup all of a table. A small change on the Scan saying save all versions was all it took to back up all versions. As is the Import did the right thing. Wouldn't take much to add versions and/or timerange as little config. on the Export MR job.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1970) Export does one version only; make it
configurable how many it does
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-1970:
-------------------------
Fix Version/s: 0.20.3
Assignee: stack
Add this in once 0.20.2 clears.
> Export does one version only; make it configurable how many it does
> -------------------------------------------------------------------
>
> Key: HBASE-1970
> URL: https://issues.apache.org/jira/browse/HBASE-1970
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Assignee: stack
> Priority: Trivial
> Fix For: 0.20.3
>
> Attachments: allversions.patch, exporter-v3.patch, timerange-v2.patch, timerange.patch
>
>
> I was playing with Export to backup all of a table. A small change on the Scan saying save all versions was all it took to back up all versions. As is the Import did the right thing. Wouldn't take much to add versions and/or timerange as little config. on the Export MR job.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1970) Export does one version only; make it
configurable how many it does
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-1970:
-------------------------
Attachment: timerange-v2.patch
Add timerange as optional params. There is something wrong though with scanning with a TimeRange. Need to figure what it is. Will do as part of this issue.
> Export does one version only; make it configurable how many it does
> -------------------------------------------------------------------
>
> Key: HBASE-1970
> URL: https://issues.apache.org/jira/browse/HBASE-1970
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Priority: Trivial
> Attachments: allversions.patch, timerange-v2.patch, timerange.patch
>
>
> I was playing with Export to backup all of a table. A small change on the Scan saying save all versions was all it took to back up all versions. As is the Import did the right thing. Wouldn't take much to add versions and/or timerange as little config. on the Export MR job.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1970) Export does one version only; make it
configurable how many it does
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-1970:
-------------------------
Attachment: allversions.patch
Here is all it takes to change Export to get all versions.
> Export does one version only; make it configurable how many it does
> -------------------------------------------------------------------
>
> Key: HBASE-1970
> URL: https://issues.apache.org/jira/browse/HBASE-1970
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Priority: Trivial
> Attachments: allversions.patch
>
>
> I was playing with Export to backup all of a table. A small change on the Scan saying save all versions was all it took to back up all versions. As is the Import did the right thing. Wouldn't take much to add versions and/or timerange as little config. on the Export MR job.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1970) Export does one version only; make it
configurable how many it does
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-1970:
-------------------------
Attachment: exporter-v3.patch
This patch adds versions, starttime, and endtime optional arguments to the Exporter MR job. I tested it. I got burned by the fact that versions default is 1 so couldn't figure why only one version returned no matter how I set times but figured it in the end. I improved javadoc around the setTimeRange in Scan to note this. I added tests to TestStoreScanner to prove TimeRange works as expected too.
> Export does one version only; make it configurable how many it does
> -------------------------------------------------------------------
>
> Key: HBASE-1970
> URL: https://issues.apache.org/jira/browse/HBASE-1970
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Priority: Trivial
> Attachments: allversions.patch, exporter-v3.patch, timerange-v2.patch, timerange.patch
>
>
> I was playing with Export to backup all of a table. A small change on the Scan saying save all versions was all it took to back up all versions. As is the Import did the right thing. Wouldn't take much to add versions and/or timerange as little config. on the Export MR job.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-1970) Export does one version only; make it
configurable how many it does
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-1970.
--------------------------
Resolution: Fixed
Committed branch and trunk.
> Export does one version only; make it configurable how many it does
> -------------------------------------------------------------------
>
> Key: HBASE-1970
> URL: https://issues.apache.org/jira/browse/HBASE-1970
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Assignee: stack
> Priority: Trivial
> Fix For: 0.20.3
>
> Attachments: allversions.patch, exporter-v3.patch, timerange-v2.patch, timerange.patch
>
>
> I was playing with Export to backup all of a table. A small change on the Scan saying save all versions was all it took to back up all versions. As is the Import did the right thing. Wouldn't take much to add versions and/or timerange as little config. on the Export MR job.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1970) Export does one version only; make it
configurable how many it does
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-1970:
-------------------------
Attachment: timerange.patch
... or time range.
> Export does one version only; make it configurable how many it does
> -------------------------------------------------------------------
>
> Key: HBASE-1970
> URL: https://issues.apache.org/jira/browse/HBASE-1970
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Priority: Trivial
> Attachments: allversions.patch, timerange.patch
>
>
> I was playing with Export to backup all of a table. A small change on the Scan saying save all versions was all it took to back up all versions. As is the Import did the right thing. Wouldn't take much to add versions and/or timerange as little config. on the Export MR job.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.