Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Trivial Trivial
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Activity

        Hide
        Harsh J added a comment -

        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?

        Show
        Harsh J added a comment - 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?
        Hide
        stack added a comment -

        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.

        Show
        stack added a comment - 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.

          People

          • Assignee:
            Unassigned
            Reporter:
            Bryan Duxbury
          • Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development