Return-Path: X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E583B18390 for ; Tue, 15 Dec 2015 09:24:48 +0000 (UTC) Received: (qmail 89428 invoked by uid 500); 15 Dec 2015 09:24:48 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 89383 invoked by uid 500); 15 Dec 2015 09:24:48 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 89372 invoked by uid 99); 15 Dec 2015 09:24:48 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2015 09:24:48 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 503101A0488 for ; Tue, 15 Dec 2015 09:24:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.226 X-Spam-Level: * X-Spam-Status: No, score=1.226 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.554] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id TEsJ037w6oKk for ; Tue, 15 Dec 2015 09:24:47 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with SMTP id 3C372429C4 for ; Tue, 15 Dec 2015 09:24:47 +0000 (UTC) Received: (qmail 89074 invoked by uid 99); 15 Dec 2015 09:24:46 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2015 09:24:46 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id A4AD52C1F6B for ; Tue, 15 Dec 2015 09:24:46 +0000 (UTC) Date: Tue, 15 Dec 2015 09:24:46 +0000 (UTC) From: "Peeyush Bishnoi (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FALCON-1661) Similar timestamp is getting added for Falcon instance vertex in GraphDB MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FALCON-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057696#comment-15057696 ] Peeyush Bishnoi commented on FALCON-1661: ----------------------------------------- Thanks [~pavan kumar] for the comment. I will set the instance actual time and nominal time as vertex property along with vertex creation "timestamp" in graphdb. > 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)