[ https://issues.apache.org/jira/browse/HBASE-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-587. ------------------------- Resolution: Won't Fix Doing as Harsh suggests. Hard to do this feature in a scalable way. If wanted, we could do something like cassandra's time-based UUID to mint UUIDs that go in a chronological direction if that'd help. > 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