[
https://issues.apache.org/jira/browse/YARN-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882074#comment-15882074
]
Rohith Sharma K S commented on YARN-6027:
-----------------------------------------
bq. Is there a reason not to simply use it?
The row key encoding/decoding does not represent properly to user in string
format. For example, flow row key is
*cl%0$uster!���!��!%0$user!dummy_%0$flow%0$*. This decoding again will be an
issue.
# Bytes.toBytes(System.currentTimeMillis()) - converts to bytes, but when
changed to string, the format is unknown
# new String(Bytes.toBytes(System.currentTimeMillis()) OR
Bytes.toString(Bytes.toBytes(System.currentTimeMillis())) results it junk
characters *Zn�^�*
It is better to use as same as UID encoder. May be we can define new interface
as Varun suggested something like
{code}String encodeAsString(T key);
T decode(String[] bytes);
{code}
> Support fromid(offset) filter for /flows API
> --------------------------------------------
>
> Key: YARN-6027
> URL: https://issues.apache.org/jira/browse/YARN-6027
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Labels: yarn-5355-merge-blocker
> Attachments: YARN-6027-YARN-5355.0001.patch,
> YARN-6027-YARN-5355.0002.patch, YARN-6027-YARN-5355.0003.patch,
> YARN-6027-YARN-5355.0004.patch
>
>
> In YARN-5585 , fromId is supported for retrieving entities. We need similar
> filter for flows/flowRun apps and flow run and flow as well.
> Along with supporting fromId, this JIRA should also discuss following points
> * Should we throw an exception for entities/entity retrieval if duplicates
> found?
> * TimelieEntity :
> ** Should equals method also check for idPrefix?
> ** Does idPrefix is part of identifiers?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
