Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-2928 YARN Timeline Service v.2: alpha 1
  3. YARN-4025

Deal with byte representations of Longs in writer code

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments


    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.9.0, 3.0.0-alpha1
    • Component/s: timelineserver
    • Labels:


      Timestamps are being stored as Longs in hbase by the HBaseTimelineWriterImpl code. There seem to be some places in the code where there are conversions between Long to byte[] to String for easier argument passing between function calls. Then these values end up being converted back to byte[] while storing in hbase.

      It would be better to pass around byte[] or the Longs themselves as applicable.

      This may result in some api changes (store function) as well in adding a few more function calls like getColumnQualifier which accepts a pre-encoded byte array. It will be in addition to the existing api which accepts a String and the ColumnHelper to return a byte[] column name instead of a String one.

      Filing jira to track these changes.


        1. YARN-4025-YARN-2928.001.patch
          14 kB
          Vrushali C
        2. YARN-4025-YARN-2928.002.patch
          34 kB
          Sangjin Lee
        3. YARN-4025-YARN-2928.003.patch
          37 kB
          Sangjin Lee
        4. YARN-4025-YARN-2928.004.patch
          46 kB
          Sangjin Lee



            • Assignee:
              sjlee0 Sangjin Lee
              vrushalic Vrushali C


              • Created:

                Issue deployment