[
https://issues.apache.org/jira/browse/FALCON-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057244#comment-15057244
]
Ajay Yadava commented on FALCON-1661:
-------------------------------------
[~peeyushb] I am assuming that you are getting some ties on sorting on the
basis of nominalTime. However, I am not sure why that is a problem. If it is
desired to have an ordering among the ties also then we can sort on the basis
of first nominal time & then on some other key like actual time. Will this not
work for your use case? If not, then can you please share your use case?
The problem with a current system time timestamp, apart from it being
semantically void is that it will break the order in which you want to see the
instances. For example, most users will want to see the instances based on
nominal time, as they want to see a couple of particular instances. Since
instances are not guaranteed to be available in the order of their nominal
time, it will create a usability issue for those users.
> Similar timestamp is getting added for Falcon instance vertex in GraphDB
> ------------------------------------------------------------------------
>
> Key: FALCON-1661
> URL: https://issues.apache.org/jira/browse/FALCON-1661
> Project: Falcon
> Issue Type: Bug
> Components: common
> Reporter: Peeyush Bishnoi
> Assignee: Peeyush Bishnoi
> Fix For: 0.9
>
>
> When working on FALCON-1643, I found that same "timestamp" is getting set
> upon adding Falcon instances vertices in GraphDB. Due to this while trying to
> sort the vertices on timestamp many instances are not getting sorted properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
