[jira] [Updated] (ATLAS-619) Queries should be normalized when tracking lineage at table

[ https://issues.apache.org/jira/browse/ATLAS-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-619: --- Attachment: ATLAS-619.patch > Queries should be normalized when tracking lineage at ta

[jira] [Commented] (ATLAS-619) Queries should be normalized when tracking lineage at table

[ https://issues.apache.org/jira/browse/ATLAS-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15276032#comment-15276032 ] Suma Shivaprasad commented on ATLAS-619: https://reviews.apache.org/r/4

[jira] [Commented] (ATLAS-754) InstanceSerialization does not serialize Reference in the values array of Reference.

[ https://issues.apache.org/jira/browse/ATLAS-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277087#comment-15277087 ] Suma Shivaprasad commented on ATLAS-754: +1 > InstanceSerialization d

[jira] [Updated] (ATLAS-758) hdfs location of hive table is pointing to old location even after rename.

[ https://issues.apache.org/jira/browse/ATLAS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-758: --- Attachment: ATLAS-758.patch > hdfs location of hive table is pointing to old location e

[jira] [Commented] (ATLAS-758) hdfs location of hive table is pointing to old location even after rename.

[ https://issues.apache.org/jira/browse/ATLAS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278577#comment-15278577 ] Suma Shivaprasad commented on ATLAS-758: The issue was the the DB being set on

[jira] [Updated] (ATLAS-66) Enable distributed tests with Hbase and solr

[ https://issues.apache.org/jira/browse/ATLAS-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-66: -- Affects Version/s: 0.6-incubating Fix Version/s: 0.6-incubating > Enable distribu

[jira] [Resolved] (ATLAS-66) Enable distributed tests with Hbase and solr

[ https://issues.apache.org/jira/browse/ATLAS-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad resolved ATLAS-66. --- Resolution: Fixed > Enable distributed tests with Hbase and s

[jira] [Resolved] (ATLAS-84) Support testing with embedded solr

[ https://issues.apache.org/jira/browse/ATLAS-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad resolved ATLAS-84. --- Resolution: Duplicate Fix Version/s: 0.6-incubating > Support testing with embedded s

[jira] [Resolved] (ATLAS-373) Renew TGT from KeyTab for ATLAS service principal

[ https://issues.apache.org/jira/browse/ATLAS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad resolved ATLAS-373. Resolution: Won't Fix Fix Version/s: 0.6-incubating This is not required since e

[jira] [Comment Edited] (ATLAS-373) Renew TGT from KeyTab for ATLAS service principal

[ https://issues.apache.org/jira/browse/ATLAS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278620#comment-15278620 ] Suma Shivaprasad edited comment on ATLAS-373 at 5/10/16 6:1

[jira] [Updated] (ATLAS-758) hdfs location of hive table is pointing to old location even after rename.

[ https://issues.apache.org/jira/browse/ATLAS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-758: --- Attachment: ATLAS-758.1.patch > hdfs location of hive table is pointing to old location e

[jira] [Commented] (ATLAS-758) hdfs location of hive table is pointing to old location even after rename.

[ https://issues.apache.org/jira/browse/ATLAS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279102#comment-15279102 ] Suma Shivaprasad commented on ATLAS-758: Rebased with trunk > hdfs loca

[jira] [Updated] (ATLAS-542) Make qualifiedName and name consistent across all Datasets andProcess

[ https://issues.apache.org/jira/browse/ATLAS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-542: --- Summary: Make qualifiedName and name consistent across all Datasets andProcess (was: Make

[jira] [Updated] (ATLAS-542) Make qualifiedName and name consistent across all Datasets and Process

[ https://issues.apache.org/jira/browse/ATLAS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-542: --- Summary: Make qualifiedName and name consistent across all Datasets and Process (was: Make

[jira] [Updated] (ATLAS-542) Make qualifiedName and name consistent across all Datasets and Process

[ https://issues.apache.org/jira/browse/ATLAS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-542: --- Description: Currently hive_db, hive_column has qualifiedName holding the fully qualified

[jira] [Assigned] (ATLAS-542) Make qualifiedName and name consistent across all Datasets and Process

[ https://issues.apache.org/jira/browse/ATLAS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad reassigned ATLAS-542: -- Assignee: Suma Shivaprasad > Make qualifiedName and name consistent across all Datas

[jira] [Commented] (ATLAS-752) Column renames should retain traits/tags

[ https://issues.apache.org/jira/browse/ATLAS-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280331#comment-15280331 ] Suma Shivaprasad commented on ATLAS-752: [~svimal2106] by RENAME COLUMN, you

[jira] [Comment Edited] (ATLAS-752) Column renames should retain traits/tags

[ https://issues.apache.org/jira/browse/ATLAS-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280331#comment-15280331 ] Suma Shivaprasad edited comment on ATLAS-752 at 5/11/16 4:0

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

[ https://issues.apache.org/jira/browse/ATLAS-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282362#comment-15282362 ] Suma Shivaprasad commented on ATLAS-667: +1 > Entity delete should ch

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

[ https://issues.apache.org/jira/browse/ATLAS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282373#comment-15282373 ] Suma Shivaprasad commented on ATLAS-435: This requires a push to the docs

[jira] [Created] (ATLAS-781) Solr collection creation script should take care of resharding/replica changes

Suma Shivaprasad created ATLAS-781: -- Summary: Solr collection creation script should take care of resharding/replica changes Key: ATLAS-781 URL: https://issues.apache.org/jira/browse/ATLAS-781

[jira] [Commented] (ATLAS-781) Solr collection creation script should take care of resharding/replica changes

[ https://issues.apache.org/jira/browse/ATLAS-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282386#comment-15282386 ] Suma Shivaprasad commented on ATLAS-781: This is needed by users if they ch

[jira] [Created] (ATLAS-782) Hive Hook : Append to list of recentQueries instead of replacing

Suma Shivaprasad created ATLAS-782: -- Summary: Hive Hook : Append to list of recentQueries instead of replacing Key: ATLAS-782 URL: https://issues.apache.org/jira/browse/ATLAS-782 Project: Atlas

[jira] [Updated] (ATLAS-619) Queries should be normalized when tracking lineage at table

[ https://issues.apache.org/jira/browse/ATLAS-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-619: --- Attachment: ATLAS-619.4.patch Latest patch committed > Queries should be normalized w

[jira] [Updated] (ATLAS-673) Install Setup: SOLR

[ https://issues.apache.org/jira/browse/ATLAS-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-673: --- Attachment: ATLAS-673-2.patch Latest patch from RB > Install Setup: S

[jira] [Updated] (ATLAS-635) Process showing old entity name where as actual entity is renamed.

[ https://issues.apache.org/jira/browse/ATLAS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-635: --- Assignee: Vimal Sharma (was: Suma Shivaprasad) > Process showing old entity name where

[jira] [Commented] (ATLAS-752) Column renames should retain traits/tags

[ https://issues.apache.org/jira/browse/ATLAS-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291890#comment-15291890 ] Suma Shivaprasad commented on ATLAS-752: [~svimal2106] Can you pls upload patc

[jira] [Commented] (ATLAS-752) Column renames should retain traits/tags

[ https://issues.apache.org/jira/browse/ATLAS-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291901#comment-15291901 ] Suma Shivaprasad commented on ATLAS-752: Initial set of questions/comments 1

[jira] [Commented] (ATLAS-804) For hive_db, "locationUri" field is renamed to "location" but the hive data model json is still showing as "locationUri"

[ https://issues.apache.org/jira/browse/ATLAS-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15292060#comment-15292060 ] Suma Shivaprasad commented on ATLAS-804: [~ayubkhan] Can you pls let me know

[jira] [Commented] (ATLAS-526) Verify insert into select results in table lineage

[ https://issues.apache.org/jira/browse/ATLAS-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296903#comment-15296903 ] Suma Shivaprasad commented on ATLAS-526: This has been fixed as part of ATLAS

[jira] [Resolved] (ATLAS-526) Verify insert into select results in table lineage

[ https://issues.apache.org/jira/browse/ATLAS-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad resolved ATLAS-526. Resolution: Fixed Assignee: Suma Shivaprasad > Verify insert into select results

[jira] [Updated] (ATLAS-686) Truncate table, insert into local dir, load from local dir , update, delete command should be easily trackable

[ https://issues.apache.org/jira/browse/ATLAS-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-686: --- Summary: Truncate table, insert into local dir, load from local dir , update, delete command

[jira] [Commented] (ATLAS-686) Truncate table, insert into local dir, load from local dir , update, delete command should be easily trackable

[ https://issues.apache.org/jira/browse/ATLAS-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296908#comment-15296908 ] Suma Shivaprasad commented on ATLAS-686: Currently these commands that

[jira] [Updated] (ATLAS-686) Truncate table, insert into local dir, load from local dir , update, delete commands should be easily trackable from a table

[ https://issues.apache.org/jira/browse/ATLAS-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-686: --- Summary: Truncate table, insert into local dir, load from local dir , update, delete commands

[jira] [Updated] (ATLAS-641) Lineage for a view created from a view seems to be confusing(from user's perspective).

[ https://issues.apache.org/jira/browse/ATLAS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-641: --- Summary: Lineage for a view created from a view seems to be confusing(from user's perspe

[jira] [Updated] (ATLAS-642) import hive should create the lineage for external tables

[ https://issues.apache.org/jira/browse/ATLAS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-642: --- Summary: import hive should create the lineage for external tables (was: import hive should

[jira] [Comment Edited] (ATLAS-686) Truncate table, insert into local dir, load from local dir , update, delete commands should be easily trackable from a table

[ https://issues.apache.org/jira/browse/ATLAS-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296908#comment-15296908 ] Suma Shivaprasad edited comment on ATLAS-686 at 5/24/16 5:1

[jira] [Commented] (ATLAS-503) Not all Hive tables are not imported into Atlas when interrupted with search queries while importing.

[ https://issues.apache.org/jira/browse/ATLAS-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299451#comment-15299451 ] Suma Shivaprasad commented on ATLAS-503: [~yhemanth] Is it trying to cr

[jira] [Comment Edited] (ATLAS-597) Cluster Name should be changed to cluster Id

[ https://issues.apache.org/jira/browse/ATLAS-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272560#comment-15272560 ] Suma Shivaprasad edited comment on ATLAS-597 at 5/25/16 6:1

[jira] [Commented] (ATLAS-597) Cluster Name should be changed to cluster Id

[ https://issues.apache.org/jira/browse/ATLAS-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299530#comment-15299530 ] Suma Shivaprasad commented on ATLAS-597: The cluster entity will have

[jira] [Commented] (ATLAS-751) Add support for primary key constraint on class types

[ https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300708#comment-15300708 ] Suma Shivaprasad commented on ATLAS-751: The proposal is to a

[jira] [Updated] (ATLAS-751) Add support for primary key constraint on class types

[ https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-751: --- Summary: Add support for primary key constraint on class types (was: Make qualifiedName an

[jira] [Updated] (ATLAS-751) Add support for primary key constraint on class types

[ https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-751: --- Description: Persisting the qualified Name for an entity has multiple issues 1. In case of

[jira] [Comment Edited] (ATLAS-751) Add support for primary key constraint on class types

[ https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300708#comment-15300708 ] Suma Shivaprasad edited comment on ATLAS-751 at 5/25/16 7:3

[jira] [Assigned] (ATLAS-751) Add support for primary key constraint on class types

[ https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad reassigned ATLAS-751: -- Assignee: Suma Shivaprasad > Add support for primary key constraint on class ty

[jira] [Comment Edited] (ATLAS-751) Add support for primary key constraint on class types

[ https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300708#comment-15300708 ] Suma Shivaprasad edited comment on ATLAS-751 at 5/25/16 7:4

[jira] [Commented] (ATLAS-751) Add support for primary key constraint on class types

[ https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301454#comment-15301454 ] Suma Shivaprasad commented on ATLAS-751: Initial Primary Key constraint

[jira] [Updated] (ATLAS-751) Add support for primary key constraint on class types

[ https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-751: --- Attachment: ATLAS-751.1.patch > Add support for primary key constraint on class ty

[jira] [Updated] (ATLAS-751) Add support for primary key constraint on class types

[ https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-751: --- Attachment: (was: ATLAS-751.1.patch) > Add support for primary key constraint on cl

[jira] [Updated] (ATLAS-751) Add support for primary key constraint on class types

[ https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-751: --- Attachment: ATLAS-751.1.patch > Add support for primary key constraint on class ty

[jira] [Commented] (ATLAS-635) Process showing old entity name where as actual entity is renamed.

[ https://issues.apache.org/jira/browse/ATLAS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303569#comment-15303569 ] Suma Shivaprasad commented on ATLAS-635: Two minor review comments 1. Re

[jira] [Updated] (ATLAS-835) Falcon Integration with Atlas

[ https://issues.apache.org/jira/browse/ATLAS-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-835: --- Assignee: Sowmya Ramesh > Falcon Integration with At

[jira] [Updated] (ATLAS-834) Handle exceptions from HiveHook executor.submit()

[ https://issues.apache.org/jira/browse/ATLAS-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-834: --- Attachment: ATLAS-834.patch > Handle exceptions from HiveHook executor.sub

[jira] [Commented] (ATLAS-503) Lock exceptions occurring due to concurrent updates to backend stores

[ https://issues.apache.org/jira/browse/ATLAS-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311010#comment-15311010 ] Suma Shivaprasad commented on ATLAS-503: +1 > Lock exceptions occurring

[jira] [Commented] (ATLAS-836) Add timeout for kafka notifications

[ https://issues.apache.org/jira/browse/ATLAS-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313176#comment-15313176 ] Suma Shivaprasad commented on ATLAS-836: [~shwethags] [~yhemanth] Looks

[jira] [Commented] (ATLAS-801) Atlas hooks would lose messages if Kafka is down for extended period of time

[ https://issues.apache.org/jira/browse/ATLAS-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313210#comment-15313210 ] Suma Shivaprasad commented on ATLAS-801: Given that the current hooks themse

[jira] [Commented] (ATLAS-845) Atlas UI to delete terms using API

[ https://issues.apache.org/jira/browse/ATLAS-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314673#comment-15314673 ] Suma Shivaprasad commented on ATLAS-845: [~Kalyanikashikar] Can you pls rebase

[jira] [Commented] (ATLAS-730) Change titan hbase table name

[ https://issues.apache.org/jira/browse/ATLAS-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319261#comment-15319261 ] Suma Shivaprasad commented on ATLAS-730: Can we add the details in documenta

[jira] [Commented] (ATLAS-867) Excessive logs: default log level should be set to 'info'; currently it is 'debug'

[ https://issues.apache.org/jira/browse/ATLAS-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319258#comment-15319258 ] Suma Shivaprasad commented on ATLAS-867: +1 > Excessive logs: default lo

[jira] [Updated] (ATLAS-751) Add support for primary key constraint on class types

[ https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-751: --- Attachment: ATLAS-751.1.patch > Add support for primary key constraint on class ty

[jira] [Commented] (ATLAS-751) Add support for primary key constraint on class types

[ https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319793#comment-15319793 ] Suma Shivaprasad commented on ATLAS-751: Attached latest patch (Yet to fix

[jira] [Commented] (ATLAS-642) import-hive should create the lineage for external tables

[ https://issues.apache.org/jira/browse/ATLAS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320969#comment-15320969 ] Suma Shivaprasad commented on ATLAS-642: lineageProcess

[jira] [Comment Edited] (ATLAS-642) import-hive should create the lineage for external tables

[ https://issues.apache.org/jira/browse/ATLAS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320969#comment-15320969 ] Suma Shivaprasad edited comment on ATLAS-642 at 6/8/16 5:1

[jira] [Commented] (ATLAS-642) import-hive should create the lineage for external tables

[ https://issues.apache.org/jira/browse/ATLAS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321121#comment-15321121 ] Suma Shivaprasad commented on ATLAS-642: Also, creating a process Referenceabl

[jira] [Created] (ATLAS-884) Process registration should call Entity update instead of create

Suma Shivaprasad created ATLAS-884: -- Summary: Process registration should call Entity update instead of create Key: ATLAS-884 URL: https://issues.apache.org/jira/browse/ATLAS-884 Project: Atlas

[jira] [Commented] (ATLAS-751) Add support for primary key constraint on class types

[ https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321398#comment-15321398 ] Suma Shivaprasad commented on ATLAS-751: Changes completed 1. Type sy

[jira] [Commented] (ATLAS-642) import-hive should create the lineage for external tables

[ https://issues.apache.org/jira/browse/ATLAS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321498#comment-15321498 ] Suma Shivaprasad commented on ATLAS-642: Can we use the template for create t

[jira] [Updated] (ATLAS-884) Process registration should call Entity update instead of create

[ https://issues.apache.org/jira/browse/ATLAS-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-884: --- Attachment: ATLAS-884.patch > Process registration should call Entity update instead of cre

[jira] [Updated] (ATLAS-597) Cluster Name should be changed to cluster Id

[ https://issues.apache.org/jira/browse/ATLAS-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-597: --- Fix Version/s: (was: 0.7-incubating) > Cluster Name should be changed to cluster

[jira] [Updated] (ATLAS-686) Truncate table, insert into local dir, load from local dir , update, delete commands should be easily trackable from a table

[ https://issues.apache.org/jira/browse/ATLAS-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-686: --- Fix Version/s: (was: 0.7-incubating) > Truncate table, insert into local dir, load f

[jira] [Updated] (ATLAS-641) Lineage for a view created from a view seems to be confusing(from user's perspective).

[ https://issues.apache.org/jira/browse/ATLAS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-641: --- Fix Version/s: (was: trunk) > Lineage for a view created from a view seems to be confus

[jira] [Commented] (ATLAS-884) Process registration should call Entity update instead of create

[ https://issues.apache.org/jira/browse/ATLAS-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322779#comment-15322779 ] Suma Shivaprasad commented on ATLAS-884: We have to address the issue

[jira] [Commented] (ATLAS-642) import-hive should create the lineage for external tables

[ https://issues.apache.org/jira/browse/ATLAS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323021#comment-15323021 ] Suma Shivaprasad commented on ATLAS-642: [~svimal2106] Thats fine for now. We

[jira] [Commented] (ATLAS-642) import-hive should create the lineage for external tables

[ https://issues.apache.org/jira/browse/ATLAS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323024#comment-15323024 ] Suma Shivaprasad commented on ATLAS-642: Can you add a test for these an

[jira] [Comment Edited] (ATLAS-884) Process registration should call Entity update instead of create

[ https://issues.apache.org/jira/browse/ATLAS-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322779#comment-15322779 ] Suma Shivaprasad edited comment on ATLAS-884 at 6/9/16 8:5

[jira] [Comment Edited] (ATLAS-884) Process registration should call Entity update instead of create

[ https://issues.apache.org/jira/browse/ATLAS-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322779#comment-15322779 ] Suma Shivaprasad edited comment on ATLAS-884 at 6/9/16 8:5

[jira] [Commented] (ATLAS-730) Change titan hbase table name

[ https://issues.apache.org/jira/browse/ATLAS-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323350#comment-15323350 ] Suma Shivaprasad commented on ATLAS-730: [~shwethags] Should we take care of h

[jira] [Created] (ATLAS-888) NPE in NotificationHookConsumer

Suma Shivaprasad created ATLAS-888: -- Summary: NPE in NotificationHookConsumer Key: ATLAS-888 URL: https://issues.apache.org/jira/browse/ATLAS-888 Project: Atlas Issue Type: Bug

[jira] [Updated] (ATLAS-888) NPE in NotificationHookConsumer

[ https://issues.apache.org/jira/browse/ATLAS-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-888: --- Assignee: Suma Shivaprasad Affects Version/s: 0.7-incubating Priority

[jira] [Commented] (ATLAS-888) NPE in NotificationHookConsumer

[ https://issues.apache.org/jira/browse/ATLAS-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323449#comment-15323449 ] Suma Shivaprasad commented on ATLAS-888: This is occurring due to UriInfo b

[jira] [Updated] (ATLAS-542) Make qualifiedName and name consistent across all Datasets and Process

[ https://issues.apache.org/jira/browse/ATLAS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-542: --- Attachment: ATLAS-542.patch > Make qualifiedName and name consistent across all Datasets

[jira] [Created] (ATLAS-889) alter table touch is not handled

Suma Shivaprasad created ATLAS-889: -- Summary: alter table touch is not handled Key: ATLAS-889 URL: https://issues.apache.org/jira/browse/ATLAS-889 Project: Atlas Issue Type: Bug Affects

[jira] [Updated] (ATLAS-889) alter table touch is not handled

[ https://issues.apache.org/jira/browse/ATLAS-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-889: --- Description: Alter table touch could be used to cause atlas to import a table which could have

[jira] [Updated] (ATLAS-889) alter table touch is not handled

[ https://issues.apache.org/jira/browse/ATLAS-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-889: --- Description: Alter table touch could be used to cause atlas to import a table which could have

[jira] [Commented] (ATLAS-889) alter table touch is not handled

[ https://issues.apache.org/jira/browse/ATLAS-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323652#comment-15323652 ] Suma Shivaprasad commented on ATLAS-889: from hive docs, TOUCH reads the meta

[jira] [Created] (ATLAS-890) Log received messages in case of error in Notification Hook Consumer

Suma Shivaprasad created ATLAS-890: -- Summary: Log received messages in case of error in Notification Hook Consumer Key: ATLAS-890 URL: https://issues.apache.org/jira/browse/ATLAS-890 Project: Atlas

[jira] [Updated] (ATLAS-890) Log received messages in case of error in Notification Hook Consumer

[ https://issues.apache.org/jira/browse/ATLAS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-890: --- Affects Version/s: 0.7-incubating Fix Version/s: 0.7-incubating > Log recei

[jira] [Comment Edited] (ATLAS-890) Log received messages in case of error in Notification Hook Consumer

[ https://issues.apache.org/jira/browse/ATLAS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323671#comment-15323671 ] Suma Shivaprasad edited comment on ATLAS-890 at 6/10/16 12:5

[jira] [Commented] (ATLAS-890) Log received messages in case of error in Notification Hook Consumer

[ https://issues.apache.org/jira/browse/ATLAS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323671#comment-15323671 ] Suma Shivaprasad commented on ATLAS-890: toString is missing in all

[jira] [Commented] (ATLAS-730) Change titan hbase table name

[ https://issues.apache.org/jira/browse/ATLAS-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325088#comment-15325088 ] Suma Shivaprasad commented on ATLAS-730: [~svimal2106] Thanks for clarif

[jira] [Comment Edited] (ATLAS-542) Make qualifiedName and name consistent across all Datasets and Process

[ https://issues.apache.org/jira/browse/ATLAS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323854#comment-15323854 ] Suma Shivaprasad edited comment on ATLAS-542 at 6/10/16 7:0

[jira] [Updated] (ATLAS-542) Make qualifiedName and name consistent across all Datasets and Process

[ https://issues.apache.org/jira/browse/ATLAS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-542: --- Attachment: ATLAS-542.1.patch > Make qualifiedName and name consistent across all Datasets

[jira] [Commented] (ATLAS-688) import-hive should depend on Hive CLASSPATH jars instead of packaging everything

[ https://issues.apache.org/jira/browse/ATLAS-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327922#comment-15327922 ] Suma Shivaprasad commented on ATLAS-688: @Vimal Sharma pom.xml also need

[jira] [Comment Edited] (ATLAS-688) import-hive should depend on Hive CLASSPATH jars instead of packaging everything

[ https://issues.apache.org/jira/browse/ATLAS-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327922#comment-15327922 ] Suma Shivaprasad edited comment on ATLAS-688 at 6/13/16 6:5

[jira] [Updated] (ATLAS-542) Make qualifiedName and name consistent across all Datasets and Process

[ https://issues.apache.org/jira/browse/ATLAS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-542: --- Attachment: ATLAS-542.2.patch Thanks [~yhemanth] . Fixed review comments > Make qualifiedN

[jira] [Updated] (ATLAS-888) NPE in NotificationHookConsumer

[ https://issues.apache.org/jira/browse/ATLAS-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-888: --- Attachment: ATLAS-888.patch > NPE in NotificationHookConsu

[jira] [Updated] (ATLAS-542) Make qualifiedName and name consistent across all Datasets and Process

[ https://issues.apache.org/jira/browse/ATLAS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-542: --- Attachment: ATLAS-542.3.patch Fixed some documentation issues as well > Make qualifiedN

[jira] [Updated] (ATLAS-890) Log received messages in case of error

[ https://issues.apache.org/jira/browse/ATLAS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-890: --- Summary: Log received messages in case of error (was: Log received messages in case of error

[jira] [Updated] (ATLAS-890) Log received messages in case of error

[ https://issues.apache.org/jira/browse/ATLAS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-890: --- Description: This will be useful for further debugging whenever an error occurs on ATLAS

[jira] [Commented] (ATLAS-688) import-hive should depend on Hive CLASSPATH jars instead of packaging everything

[ https://issues.apache.org/jira/browse/ATLAS-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328253#comment-15328253 ] Suma Shivaprasad commented on ATLAS-688: Also pls update documentation to

<    2   3   4   5   6   7   8   9   10   11   >