Joep Rottinghuis commented on YARN-3706:

Just realized an additional problem.
If we use the same separator character for compound column qualifiers 
(e!eventId!eventInfoKey) as well as in separator for values 
(relatedToKey->id7!id8!id9) then we have problems recognizing what is part of 
the key and what is the value.

I think I have to introduce a value separator and add an additional argument to 
the cleanse method for this....

> Generalize native HBase writer for additional tables
> ----------------------------------------------------
>                 Key: YARN-3706
>                 URL: https://issues.apache.org/jira/browse/YARN-3706
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Joep Rottinghuis
>            Assignee: Joep Rottinghuis
>            Priority: Minor
>         Attachments: YARN-3706-YARN-2928.001.patch
> When reviewing YARN-3411 we noticed that we could change the class hierarchy 
> a little in order to accommodate additional tables easily.
> In order to get ready for benchmark testing we left the original layout in 
> place, as performance would not be impacted by the code hierarchy.
> Here is a separate jira to address the hierarchy.

This message was sent by Atlassian JIRA

Reply via email to