hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-587) Add auto-primary-key feature
Date Sun, 01 Jan 2012 20:33:30 GMT

    [ https://issues.apache.org/jira/browse/HBASE-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178223#comment-13178223
] 

Harsh J commented on HBASE-587:
-------------------------------

I guess ImportTSV has provided this for the generic TSV files at least. I'm not sure if trying
to build something more generic would be worth it. Most have complex key structures by the
looks of it today and I think its best left in the way of folks building out their own keys.

Should we resolve this as Won't Fix / Later?
                
> Add auto-primary-key feature
> ----------------------------
>
>                 Key: HBASE-587
>                 URL: https://issues.apache.org/jira/browse/HBASE-587
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Bryan Duxbury
>            Priority: Trivial
>
> Some folks seem to be interested in having their row keys automatically generated in
a unique fashion. Maybe we could do something like allow the user to specify they want an
automatic key, and then we'll generate a GUID that's unique for that table and return it as
part of the commit. Not sure what the mechanics would look like exactly, but seems doable
and it's going to be a more prevalent use case as people start to put data into HBase first
without touching another system or pushing data without a natural unique primary key.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message