[jira] [Commented] (ATLAS-622) Introduce soft delete

[ https://issues.apache.org/jira/browse/ATLAS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15242451#comment-15242451 ] ATLAS QA commented on ATLAS-622: {color:red}-1 overall{color}. Here are the results of testing the latest

Re: Review Request 46011: ATLAS-622 Introduce soft delete

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/46011/ --- (Updated April 15, 2016, 4:46 a.m.) Review request for atlas. Changes

Re: Review Request 46011: ATLAS-622 Introduce soft delete

> On April 14, 2016, 7:31 p.m., Suma Shivaprasad wrote: > > repository/src/test/java/org/apache/atlas/service/DefaultMetadataServiceTest.java, > > line 122 > > > > > > Didnt see the unique indexes being removed for

[jira] [Created] (ATLAS-676) Enforcing unique attribute values for struct/trait

Shwetha G S created ATLAS-676: - Summary: Enforcing unique attribute values for struct/trait Key: ATLAS-676 URL: https://issues.apache.org/jira/browse/ATLAS-676 Project: Atlas Issue Type:

[jira] [Updated] (ATLAS-622) Introduce soft delete

[ https://issues.apache.org/jira/browse/ATLAS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-622: -- Attachment: ATLAS-622-v5.patch Complete patch for review > Introduce soft delete >

Build failed in Jenkins: apache-atlas-nightly #243

See Changes: [sumasai.shivaprasad] ATLAS-594 alter table rename doesnt work across databases ( sumasai via -- [...truncated 5928 lines...] 127.0.0.1 - - [14/Apr/2016:19:45:26 +] "GET

Re: Review Request 46011: ATLAS-622 Introduce soft delete

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/46011/#review128963 ---

[jira] [Updated] (ATLAS-532) Change Data types of all timestamps(currently long)

[ https://issues.apache.org/jira/browse/ATLAS-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-532: --- Attachment: ATLAS-532.3.patch Addressed review comments > Change Data types of all

[jira] [Updated] (ATLAS-532) Change Data types of all timestamps(currently long)

[ https://issues.apache.org/jira/browse/ATLAS-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-532: --- Attachment: Screen Shot 2016-04-12 at 10.37.06 PM.png > Change Data types of all

[jira] [Updated] (ATLAS-532) Change Data types of all timestamps(currently long)

[ https://issues.apache.org/jira/browse/ATLAS-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-532: --- Attachment: Screen Shot 2016-04-08 at 2.40.24 PM.png > Change Data types of all

[jira] [Commented] (ATLAS-532) Change Data types of all timestamps(currently long)

[ https://issues.apache.org/jira/browse/ATLAS-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241736#comment-15241736 ] Suma Shivaprasad commented on ATLAS-532: Replies inline to [~yhemanth]'s review comments We have

[jira] [Updated] (ATLAS-532) Change Data types of all timestamps(currently long)

[ https://issues.apache.org/jira/browse/ATLAS-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-532: --- Attachment: (was: Screen Shot 2016-04-08 at 2.40.24 PM.png) > Change Data types of all

[jira] [Created] (ATLAS-675) Storm Hook should use timetsamps as Date type instead of Long

Suma Shivaprasad created ATLAS-675: -- Summary: Storm Hook should use timetsamps as Date type instead of Long Key: ATLAS-675 URL: https://issues.apache.org/jira/browse/ATLAS-675 Project: Atlas

[jira] [Created] (ATLAS-674) Falcon Hook should use timestamps instead of long

Suma Shivaprasad created ATLAS-674: -- Summary: Falcon Hook should use timestamps instead of long Key: ATLAS-674 URL: https://issues.apache.org/jira/browse/ATLAS-674 Project: Atlas Issue

Re: [ANNOUNCE] New Committer: Hemanth Yamijala

Congrats Hemanth! On Thu, Apr 14, 2016 at 7:05 AM, Erik Bergenholtz < ebergenho...@hortonworks.com> wrote: > That’s great news! Congrats & well deserved. > > Erik > > > On Apr 14, 2016, at 1:15 AM, Shwetha Shivalingamurthy < > sshivalingamur...@hortonworks.com> wrote: > > > > Hi All, > > > > The

[jira] [Commented] (ATLAS-673) Install Setup: Kafka & SOLR

[ https://issues.apache.org/jira/browse/ATLAS-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241354#comment-15241354 ] Erik Bergenholtz commented on ATLAS-673: [~yhemanth] - can you elaborate on the setup requirement

[jira] [Created] (ATLAS-673) Install Setup: Kafka & SOLR

Erik Bergenholtz created ATLAS-673: -- Summary: Install Setup: Kafka & SOLR Key: ATLAS-673 URL: https://issues.apache.org/jira/browse/ATLAS-673 Project: Atlas Issue Type: Task Affects

Re: Review Request 45929: ATLAS-628: Starting two Atlas instances at the same time causes exceptions in HA mode.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45929/ --- (Updated April 14, 2016, 3:24 p.m.) Review request for atlas. Changes

[jira] [Assigned] (ATLAS-559) Atlas should allow JSONs to be submitted that don't have optional attributes.

[ https://issues.apache.org/jira/browse/ATLAS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neeru Gupta reassigned ATLAS-559: - Assignee: Neeru Gupta > Atlas should allow JSONs to be submitted that don't have optional

Re: Review Request 46011: ATLAS-622 Introduce soft delete

> On April 12, 2016, 10:20 p.m., David Kantor wrote: > > repository/src/main/java/org/apache/atlas/RepositoryMetadataModule.java, > > line 90 > > > > > > Configuring hard deletes at the system level should be done

[jira] [Resolved] (ATLAS-436) Add LIMIT to search DSL

[ https://issues.apache.org/jira/browse/ATLAS-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neeru Gupta resolved ATLAS-436. --- Resolution: Duplicate Duplicate of ATLAS-435 > Add LIMIT to search DSL > --- > >

[jira] [Commented] (ATLAS-435) Add ORDER BY to search DSL

[ https://issues.apache.org/jira/browse/ATLAS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241224#comment-15241224 ] Neeru Gupta commented on ATLAS-435: --- [~suma.shivaprasad] Please review the changes for ATLAS-435 and

Re: Review Request 45499: ATLAS-436, ATLAS-435 order by and limit clause for DSL queries

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45499/ --- (Updated April 14, 2016, 2:11 p.m.) Review request for atlas, David Kantor and

[jira] [Commented] (ATLAS-672) UI: Make dashboard v2 the default UI implementation

[ https://issues.apache.org/jira/browse/ATLAS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241198#comment-15241198 ] Jean-Baptiste Onofré commented on ATLAS-672: By the way, I'm testing dashboard v2 now. > UI:

[jira] [Commented] (ATLAS-672) UI: Make dashboard v2 the default UI implementation

[ https://issues.apache.org/jira/browse/ATLAS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241191#comment-15241191 ] Jean-Baptiste Onofré commented on ATLAS-672: +1 > UI: Make dashboard v2 the default UI

[jira] [Created] (ATLAS-672) UI: Make dashboard v2 the default UI implementation

Erik Bergenholtz created ATLAS-672: -- Summary: UI: Make dashboard v2 the default UI implementation Key: ATLAS-672 URL: https://issues.apache.org/jira/browse/ATLAS-672 Project: Atlas Issue

Re: Review Request 45499: ATLAS-436, ATLAS-435 order by and limit clause for DSL queries

> On April 7, 2016, 7:55 p.m., Jeff Hagelberg wrote: > > repository/src/main/scala/org/apache/atlas/query/GremlinEvaluator.scala, > > line 99 > > > > > > I would suggest adding an intermediate variable here for the

Review Request 46197: ATLAS-658 : Improve Lineage with Backbone porting

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/46197/ --- Review request for atlas, Erik Bergenholtz, Gautam Borad, Mehul Parikh, Nixon

[jira] [Updated] (ATLAS-658) Improve Lineage with Backbone porting

[ https://issues.apache.org/jira/browse/ATLAS-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-658: -- Attachment: ATLAS-658.patch > Improve Lineage with Backbone porting >

[jira] [Created] (ATLAS-671) Include binary dist in release

Jean-Baptiste Onofré created ATLAS-671: -- Summary: Include binary dist in release Key: ATLAS-671 URL: https://issues.apache.org/jira/browse/ATLAS-671 Project: Atlas Issue Type: Task

[jira] [Created] (ATLAS-670) Entity update/delete operations shouldn't be supported on deleted entities

Shwetha G S created ATLAS-670: - Summary: Entity update/delete operations shouldn't be supported on deleted entities Key: ATLAS-670 URL: https://issues.apache.org/jira/browse/ATLAS-670 Project: Atlas

[jira] [Commented] (ATLAS-594) alter table rename doesnt work across databases

[ https://issues.apache.org/jira/browse/ATLAS-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241011#comment-15241011 ] Shwetha G S commented on ATLAS-594: --- +1 > alter table rename doesnt work across databases >

[jira] [Commented] (ATLAS-543) Entity Instance requests should not require ID element for new Entities

[ https://issues.apache.org/jira/browse/ATLAS-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15240998#comment-15240998 ] Shwetha G S commented on ATLAS-543: --- +1 > Entity Instance requests should not require ID element for new

[jira] [Updated] (ATLAS-494) UI Authentication

[ https://issues.apache.org/jira/browse/ATLAS-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-494: -- Summary: UI Authentication (was: Authentication ) > UI Authentication > -- > >

[jira] [Updated] (ATLAS-664) UI: Add Support for Versioning / History

[ https://issues.apache.org/jira/browse/ATLAS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-664: -- Assignee: Kalyani Kashikar (was: Keval Bhatt) > UI: Add Support for Versioning / History >

[jira] [Updated] (ATLAS-616) Zookeeper throws exceptions when trying to fire DSL queries at Atlas at large scale.

[ https://issues.apache.org/jira/browse/ATLAS-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-616: --- Attachment: heap.png An update: As described above, all indications to cause of the problem

Re: Review Request 46011: ATLAS-622 Introduce soft delete

> On April 13, 2016, 10:36 p.m., Suma Shivaprasad wrote: > > repository/src/main/java/org/apache/atlas/repository/graph/GraphHelper.java, > > line 184 > > > > > > There could be a way to get the sorted edge list

[jira] [Created] (ATLAS-669) GraphHelper.getEdgeForLabel() can use edge index

Shwetha G S created ATLAS-669: - Summary: GraphHelper.getEdgeForLabel() can use edge index Key: ATLAS-669 URL: https://issues.apache.org/jira/browse/ATLAS-669 Project: Atlas Issue Type: Bug

Re: Review Request 46011: ATLAS-622 Introduce soft delete

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/46011/ --- (Updated April 14, 2016, 10:29 a.m.) Review request for atlas. Changes

[jira] [Commented] (ATLAS-668) GraphHelper.addEdge() should add an edge only if there is no existing edge

[ https://issues.apache.org/jira/browse/ATLAS-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15240905#comment-15240905 ] Hemanth Yamijala commented on ATLAS-668: Yes, of course.. sorry I missed that. >

[jira] [Commented] (ATLAS-668) GraphHelper.addEdge() should add an edge only if there is no existing edge

[ https://issues.apache.org/jira/browse/ATLAS-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15240900#comment-15240900 ] Shwetha G S commented on ATLAS-668: --- GraphBackedTypeStore is just for type store. Entity store is in

[jira] [Assigned] (ATLAS-664) UI: Add Support for Versioning / History

[ https://issues.apache.org/jira/browse/ATLAS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-664: - Assignee: Keval Bhatt (was: Nixon Rodrigues) > UI: Add Support for Versioning / History >

Re: Review Request 46011: ATLAS-622 Introduce soft delete

> On April 12, 2016, 6:57 p.m., Suma Shivaprasad wrote: > > repository/src/main/java/org/apache/atlas/repository/graph/DeleteHandler.java, > > line 244 > > > > > > Please enable this check. Raising this to track so

[jira] [Commented] (ATLAS-668) GraphHelper.addEdge() should add an edge only if there is no existing edge

[ https://issues.apache.org/jira/browse/ATLAS-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15240847#comment-15240847 ] Hemanth Yamijala commented on ATLAS-668: Umm. As a fix for ATLAS-474, a check was added to

Re: Review Request 46011: ATLAS-622 Introduce soft delete

> On April 12, 2016, 7:51 p.m., Suma Shivaprasad wrote: > > repository/src/main/java/org/apache/atlas/repository/graph/DeleteHandler.java, > > line 111 > > > > > > Can you pls explain how deletion of edges works

Re: Review Request 46011: ATLAS-622 Introduce soft delete

> On April 12, 2016, 6:23 p.m., Suma Shivaprasad wrote: > > repository/src/main/java/org/apache/atlas/repository/graph/AtlasEdgeLabel.java, > > line 35 > > > > > > why is this removed? Its used even for trait edges

Re: Review Request 46011: ATLAS-622 Introduce soft delete

> On April 11, 2016, 10:11 p.m., Suma Shivaprasad wrote: > > repository/src/main/java/org/apache/atlas/RepositoryMetadataModule.java, > > line 90 > > > > > > How are we planing to make this configurable? This is

Re: Review Request 46011: ATLAS-622 Introduce soft delete

> On April 12, 2016, 10:20 p.m., David Kantor wrote: > > repository/src/main/java/org/apache/atlas/RepositoryMetadataModule.java, > > line 90 > > > > > > Configuring hard deletes at the system level should be done

Re: Review Request 46011: ATLAS-622 Introduce soft delete

> On April 13, 2016, 10:49 p.m., Suma Shivaprasad wrote: > > repository/src/main/java/org/apache/atlas/repository/graph/SoftDeleteHandler.java, > > line 42 > > > > > > Should we keep timestamp same for the entire

Re: Review Request 46011: ATLAS-622 Introduce soft delete

> On April 13, 2016, 9:13 p.m., Suma Shivaprasad wrote: > > repository/src/main/java/org/apache/atlas/repository/graph/DeleteHandler.java, > > line 67 > > > > > > when is state being cleared? In

[jira] [Created] (ATLAS-668) GraphHelper.addEdge() should add an edge only if there is no existing edge

Shwetha G S created ATLAS-668: - Summary: GraphHelper.addEdge() should add an edge only if there is no existing edge Key: ATLAS-668 URL: https://issues.apache.org/jira/browse/ATLAS-668 Project: Atlas

[jira] [Created] (ATLAS-667) Entity delete should check for required reverse references

Shwetha G S created ATLAS-667: - Summary: Entity delete should check for required reverse references Key: ATLAS-667 URL: https://issues.apache.org/jira/browse/ATLAS-667 Project: Atlas Issue Type:

[jira] [Commented] (ATLAS-532) Change Data types of all timestamps(currently long)

[ https://issues.apache.org/jira/browse/ATLAS-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15240824#comment-15240824 ] Hemanth Yamijala commented on ATLAS-532: A couple of comments / questions: * We have defined

Re: [ANNOUNCE] New Committer: Hemanth Yamijala

Congrats Hemanth. From: Seetharam Venkatesh To: dev@atlas.incubator.apache.org Date: 14/04/16 11:26 AM Subject:Re: [ANNOUNCE] New Committer: Hemanth Yamijala Thanks Shwetha for doing the honors and Congratulations Hemanth! On Wed, Apr 13, 2016 at