[jira] [Assigned] (ATLAS-945) Minor typo in warning message while deleting terms

[Keval Bhatt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keval Bhatt reassigned ATLAS-945:
-

Assignee: Keval Bhatt

> Minor typo in warning message while deleting terms
> --
>
> Key: ATLAS-945
> URL: https://issues.apache.org/jira/browse/ATLAS-945
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Keval Bhatt
>Priority: Minor
>
> Create terms under Taxonomy tab on left pane. Select a term and delete. There 
> is an alert message that comes up saying: 
> {code}
> "Delete: `BusinessTaxonomy.term1.term12`?
> Assets map to this term will be unclassified
> {code}
> The 2nd line should read: Assets *mapped* to this term will be unclassified.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-945) Minor typo in warning message while deleting terms

[Keval Bhatt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keval Bhatt updated ATLAS-945:
--
Assignee: Kalyani Kashikar  (was: Keval Bhatt)

> Minor typo in warning message while deleting terms
> --
>
> Key: ATLAS-945
> URL: https://issues.apache.org/jira/browse/ATLAS-945
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Kalyani Kashikar
>Priority: Minor
>
> Create terms under Taxonomy tab on left pane. Select a term and delete. There 
> is an alert message that comes up saying: 
> {code}
> "Delete: `BusinessTaxonomy.term1.term12`?
> Assets map to this term will be unclassified
> {code}
> The 2nd line should read: Assets *mapped* to this term will be unclassified.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-954) Get hadoop classpath if command hadoop is in PATH

[Vimal Sharma (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vimal Sharma updated ATLAS-954:
---
Attachment: ATLAS-954.patch

> Get hadoop classpath if command hadoop is in PATH
> -
>
> Key: ATLAS-954
> URL: https://issues.apache.org/jira/browse/ATLAS-954
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-954.patch
>
>
> The script import_hive.sh expects Hadoop classpath.
> Environment variable HADOOP_HOME or HADOOP_CLASSPATH might not be set but 
> command hadoop may be in the PATH.
> Get hadoop classpath from hadoop command.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Vimal Sharma (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vimal Sharma updated ATLAS-688:
---
Attachment: (was: ATLAS-688-v4.patch)

> import-hive should depend on Hive CLASSPATH jars instead of packaging 
> everything
> 
>
> Key: ATLAS-688
> URL: https://issues.apache.org/jira/browse/ATLAS-688
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-688-v2.patch, ATLAS-688-v3.patch, ATLAS-688.patch
>
>
> Currently, import-hive.sh packages all hive, hadoop jars etc. Instead it 
> should depend on HIVE_CLASSPATH from which it can get the jars and should be 
> paakged along with hook on hive server m/cs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Vimal Sharma (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vimal Sharma resolved ATLAS-688.

Resolution: Fixed

> import-hive should depend on Hive CLASSPATH jars instead of packaging 
> everything
> 
>
> Key: ATLAS-688
> URL: https://issues.apache.org/jira/browse/ATLAS-688
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-688-v2.patch, ATLAS-688-v3.patch, ATLAS-688.patch
>
>
> Currently, import-hive.sh packages all hive, hadoop jars etc. Instead it 
> should depend on HIVE_CLASSPATH from which it can get the jars and should be 
> paakged along with hook on hive server m/cs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Vimal Sharma (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352365#comment-15352365
 ] 

Vimal Sharma commented on ATLAS-688:


Marking this issue as resolved since separate JIRAS ATLAS-954 and ATLAS-955 
have been created to track the follow up issues

> import-hive should depend on Hive CLASSPATH jars instead of packaging 
> everything
> 
>
> Key: ATLAS-688
> URL: https://issues.apache.org/jira/browse/ATLAS-688
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-688-v2.patch, ATLAS-688-v3.patch, 
> ATLAS-688-v4.patch, ATLAS-688.patch
>
>
> Currently, import-hive.sh packages all hive, hadoop jars etc. Instead it 
> should depend on HIVE_CLASSPATH from which it can get the jars and should be 
> paakged along with hook on hive server m/cs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-955) Hadoop classpath from hadoop command support in Windows environment

[Vimal Sharma (JIRA)]

Vimal Sharma created ATLAS-955:
--

 Summary: Hadoop classpath from hadoop command support in Windows 
environment
 Key: ATLAS-955
 URL: https://issues.apache.org/jira/browse/ATLAS-955
 Project: Atlas
  Issue Type: Bug
Reporter: Vimal Sharma
Assignee: Vimal Sharma
 Fix For: 0.8-incubating


The command to extract Hadoop classpath from command "hadoop" in PATH may not 
work in Windows environment. Verify and provide the fix(if any)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-954) Get hadoop classpath if command hadoop is in PATH

[Vimal Sharma (JIRA)]

Vimal Sharma created ATLAS-954:
--

 Summary: Get hadoop classpath if command hadoop is in PATH
 Key: ATLAS-954
 URL: https://issues.apache.org/jira/browse/ATLAS-954
 Project: Atlas
  Issue Type: Bug
Reporter: Vimal Sharma
Assignee: Vimal Sharma
 Fix For: 0.8-incubating


The script import_hive.sh expects Hadoop classpath.

Environment variable HADOOP_HOME or HADOOP_CLASSPATH might not be set but 
command hadoop may be in the PATH.

Get hadoop classpath from hadoop command.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-948) import-hive should allow an option to continue after failure

[Shwetha G S (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352313#comment-15352313
 ] 

Shwetha G S commented on ATLAS-948:
---

+1

> import-hive should allow an option to continue after failure
> 
>
> Key: ATLAS-948
> URL: https://issues.apache.org/jira/browse/ATLAS-948
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>Priority: Critical
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-948.patch
>
>
> Currently import-hive.sh aborts whenever a failure occurs during import of a 
> table. It should allow continuation after logging the failure which could be 
> checked and post processed later.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ATLAS-953) pyspark

[Hemanth Yamijala (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hemanth Yamijala resolved ATLAS-953.

Resolution: Invalid

This is not an Apache Atlas issue. Please create a new issue by selecting the 
correct project.

> pyspark
> ---
>
> Key: ATLAS-953
> URL: https://issues.apache.org/jira/browse/ATLAS-953
> Project: Atlas
>  Issue Type: Bug
>Reporter: Edward Ma
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-953) pyspark

[Edward Ma (JIRA)]

Edward Ma created ATLAS-953:
---

 Summary: pyspark
 Key: ATLAS-953
 URL: https://issues.apache.org/jira/browse/ATLAS-953
 Project: Atlas
  Issue Type: Bug
Reporter: Edward Ma






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-948) import-hive should allow an option to continue after failure

[ATLAS QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351999#comment-15351999
 ] 

ATLAS QA commented on ATLAS-948:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12813963/ATLAS-948.patch
  against master revision 0bf878d.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

+1 checkstyle.  The patch generated 0 code style errors.

{color:red}-1 findbugs{color}.  The patch appears to introduce 380 new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in :
   
org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest

Test results: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/369//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/369//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/369//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/369//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/369//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/369//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/369//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/369//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/369//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/369//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/369//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/369//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/369//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/369//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/369//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/369//console

This message is automatically generated.

> import-hive should allow an option to continue after failure
> 
>
> Key: ATLAS-948
> URL: https://issues.apache.org/jira/browse/ATLAS-948
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>Priority: Critical
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-948.patch
>
>
> Currently import-hive.sh aborts whenever a failure occurs during import of a 
> table. It should allow continuation after logging the failure which could be 
> checked and post processed later.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-948) import-hive should allow an option to continue after failure

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad updated ATLAS-948:
---
Attachment: ATLAS-948.patch

> import-hive should allow an option to continue after failure
> 
>
> Key: ATLAS-948
> URL: https://issues.apache.org/jira/browse/ATLAS-948
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>Priority: Critical
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-948.patch
>
>
> Currently import-hive.sh aborts whenever a failure occurs during import of a 
> table. It should allow continuation after logging the failure which could be 
> checked and post processed later.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-948) import-hive should allow an option to continue after failure

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad updated ATLAS-948:
---
Attachment: (was: ATLAS-948.patch)

> import-hive should allow an option to continue after failure
> 
>
> Key: ATLAS-948
> URL: https://issues.apache.org/jira/browse/ATLAS-948
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>Priority: Critical
> Fix For: 0.8-incubating
>
>
> Currently import-hive.sh aborts whenever a failure occurs during import of a 
> table. It should allow continuation after logging the failure which could be 
> checked and post processed later.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-948) import-hive should allow an option to continue after failure

[Suma Shivaprasad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351920#comment-15351920
 ] 

Suma Shivaprasad edited comment on ATLAS-948 at 6/27/16 10:00 PM:
--

Handling failures with a flag(failOnError) to abort on failure if specified 
while running import-hive.sh. this option is only for table imports and DB 
import failures will still continue to fail.


was (Author: suma.shivaprasad):
Handling failures with a flag(failOnError) to abort on failure if specified 
while running import-hive.sh

> import-hive should allow an option to continue after failure
> 
>
> Key: ATLAS-948
> URL: https://issues.apache.org/jira/browse/ATLAS-948
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>Priority: Critical
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-948.patch
>
>
> Currently import-hive.sh aborts whenever a failure occurs during import of a 
> table. It should allow continuation after logging the failure which could be 
> checked and post processed later.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-948) import-hive should allow an option to continue after failure

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad updated ATLAS-948:
---
Attachment: ATLAS-948.patch

Handling failures with a flag(failOnError) to abort on failure if specified 
while running import-hive.sh

> import-hive should allow an option to continue after failure
> 
>
> Key: ATLAS-948
> URL: https://issues.apache.org/jira/browse/ATLAS-948
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating, 0.8-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>Priority: Critical
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-948.patch
>
>
> Currently import-hive.sh aborts whenever a failure occurs during import of a 
> table. It should allow continuation after logging the failure which could be 
> checked and post processed later.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-919) UI : Deleted references should be shown in red or filtered out

[Suma Shivaprasad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351919#comment-15351919
 ] 

Suma Shivaprasad commented on ATLAS-919:


[~kevalbhatt18] Took a look at the patch. Can you use "qualifiedName" if "name" 
is not available to display the link for references. And if "qualifiedName" is 
not available, only then use "typeName". Please make these changes . Rest looks 
fine.

> UI : Deleted references should be shown in red or filtered out
> --
>
> Key: ATLAS-919
> URL: https://issues.apache.org/jira/browse/ATLAS-919
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json, 
> ATLAS-919.1.patch, ATLAS-919.2.patch, ATLAS-919.patch, 
> ATLAS-919.rebased.patch, Screen Shot 2016-06-20 at 3.56.33 PM.png, Screen 
> Shot 2016-06-23 at 11.26.17 AM.png
>
>
> Foe eg: In a hive_table one of the columns could be dropped in which case the 
> columns array will have the deleted column as well. This could be completely 
> filtered out in the UI. The way to identify this is to check if the entity 
> state is DELETED when going through the references.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Atlas .7 build fails at the repository step: HMasterCannot assign requested address

[Dave Kantor]

Hi Ernie,

Not sure why this is happening on your system and not others who have
tested 0.7, but to work around this issue, add -DskipTests to your mvn
command line to avoid running the failing test (and all other tests).

Regards,
Dave

David Kantor
IBM Software Group
Phone: 978-899-2072 (T/L: 276-2072)
Email: dkan...@us.ibm.com



From:   Ernie Ostic/Newark/IBM@IBMUS
To: atlas 
Date:   06/27/2016 05:05 AM
Subject:Atlas .7 build fails at the repository step:   HMasterCannot
assign requested address





Hi Everyone...

Trying to get the build to work, in this case on a redhat machine, and
after reviewing various threads and increasing heap size to 1.5G and moving
to a faster disk.that resolved some of the earlier errors, but the
build still continues to fail at this part of the repository step:


Running org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest
Tests run: 6, Failures: 4, Errors: 0, Skipped: 2, Time elapsed: 1.425 sec
<<< FAILURE! - in
org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest
setup(org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest)
Time elapsed: 1.383 sec  <<< FAILURE!
java.lang.RuntimeException: Failed construction of Master: class
org.apache.hadoop.hbase.master.HMasterCannot assign requested address
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at sun.nio.ch.ServerSocketChannelImpl.bind
(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at org.apache.hadoop.hbase.ipc.RpcServer.bind(RpcServer.java:2495)
at org.apache.hadoop.hbase.ipc.RpcServer$Listener.
(RpcServer.java:580)
at org.apache.hadoop.hbase.ipc.RpcServer.(RpcServer.java:1982)
at org.apache.hadoop.hbase.regionserver.RSRpcServices.
(RSRpcServices.java:863)
at org.apache.hadoop.hbase.master.MasterRpcServices.
(MasterRpcServices.java:210)
.
.
.

Currently I am looking in the environment to see what ports might be in use
or in conflict, but open to all ideas.Thank you in advance for any
thoughts on debugging this scenario.

Ernie






Ernie Ostic

WW Product Specialist, Information Server
IBM Analytics
Cell: (617) 331 8238
---
Open IGC is here!

Extend the Catalog with custom objects and lineage definitions!
https://dsrealtime.wordpress.com/2015/07/29/open-igc-is-here/

[jira] [Commented] (ATLAS-918) UI : Deleted entities show status as DELETED and Datasets should be differentiable in lineage

[Suma Shivaprasad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351829#comment-15351829
 ] 

Suma Shivaprasad commented on ATLAS-918:


[~kevalbhatt18] ATLAS-947(State information) is available now on master to 
finish this jira. Please refer that jira for sample json.

> UI : Deleted entities show status as DELETED and Datasets should be 
> differentiable in lineage
> -
>
> Key: ATLAS-918
> URL: https://issues.apache.org/jira/browse/ATLAS-918
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: Screen Shot 2016-06-20 at 2.20.32 PM.png
>
>
> Keval,
> This jira is to track showing deleted entities with a diff color in lineage. 
> Is there anything missing in the lineage API to implement this? We need to 
> take care of this since no one looks at lineage via a process and will be 
> mostly looking at lineage from a table or  a dataset. Also a table can be 
> dropped and recreated in hive, leading to linage showing as attached in 
> screen shot
> Also can we show the property (status)__status for deleted entities  as 
> "DELETED" . We could display that in "properties" section.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ATLAS-952) Drill plugin for Cassandra

[Suma Shivaprasad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suma Shivaprasad resolved ATLAS-952.

Resolution: Invalid

Wrong project

> Drill plugin for Cassandra
> --
>
> Key: ATLAS-952
> URL: https://issues.apache.org/jira/browse/ATLAS-952
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Lokesh Ceeba
>
> Adapter or Drill plugin for Cassandra



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Suma Shivaprasad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351493#comment-15351493
 ] 

Suma Shivaprasad commented on ATLAS-688:


The above change may not work on windows. Can you file a bug to track it?

> import-hive should depend on Hive CLASSPATH jars instead of packaging 
> everything
> 
>
> Key: ATLAS-688
> URL: https://issues.apache.org/jira/browse/ATLAS-688
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-688-v2.patch, ATLAS-688-v3.patch, 
> ATLAS-688-v4.patch, ATLAS-688.patch
>
>
> Currently, import-hive.sh packages all hive, hadoop jars etc. Instead it 
> should depend on HIVE_CLASSPATH from which it can get the jars and should be 
> paakged along with hook on hive server m/cs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Suma Shivaprasad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351486#comment-15351486
 ] 

Suma Shivaprasad commented on ATLAS-688:


+1

> import-hive should depend on Hive CLASSPATH jars instead of packaging 
> everything
> 
>
> Key: ATLAS-688
> URL: https://issues.apache.org/jira/browse/ATLAS-688
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-688-v2.patch, ATLAS-688-v3.patch, 
> ATLAS-688-v4.patch, ATLAS-688.patch
>
>
> Currently, import-hive.sh packages all hive, hadoop jars etc. Instead it 
> should depend on HIVE_CLASSPATH from which it can get the jars and should be 
> paakged along with hook on hive server m/cs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-952) Drill plugin for Cassandra

[Lokesh Ceeba (JIRA)]

Lokesh Ceeba created ATLAS-952:
--

 Summary: Drill plugin for Cassandra
 Key: ATLAS-952
 URL: https://issues.apache.org/jira/browse/ATLAS-952
 Project: Atlas
  Issue Type: Improvement
Reporter: Lokesh Ceeba


Adapter or Drill plugin for Cassandra



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Shwetha G S (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351386#comment-15351386
 ] 

Shwetha G S commented on ATLAS-435:
---

[~guptaneeru]/[~dkantor], in gremlin translator, why was toLowercase() added to 
the property value? If the orderby property is not set, the condition fails

> Add ORDER BY and Limit  to search DSL 
> --
>
> Key: ATLAS-435
> URL: https://issues.apache.org/jira/browse/ATLAS-435
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: David Kantor
>Assignee: Neeru Gupta
> Fix For: 0.7-incubating
>
> Attachments: rb45499(2).patch, rb45499(3).patch
>
>
> Add support for Limit and ORDER BY to Atlas search DSL. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-919) UI : Deleted references should be shown in red or filtered out

[Keval Bhatt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keval Bhatt updated ATLAS-919:
--
Attachment: ATLAS-919.2.patch

Above issue is handled in updated patch

> UI : Deleted references should be shown in red or filtered out
> --
>
> Key: ATLAS-919
> URL: https://issues.apache.org/jira/browse/ATLAS-919
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json, 
> ATLAS-919.1.patch, ATLAS-919.2.patch, ATLAS-919.patch, 
> ATLAS-919.rebased.patch, Screen Shot 2016-06-20 at 3.56.33 PM.png, Screen 
> Shot 2016-06-23 at 11.26.17 AM.png
>
>
> Foe eg: In a hive_table one of the columns could be dropped in which case the 
> columns array will have the deleted column as well. This could be completely 
> filtered out in the UI. The way to identify this is to check if the entity 
> state is DELETED when going through the references.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Apache Jenkins Server]

See 

Changes:

[hyamijala] ATLAS-927 aboutAtlas_tmpl.html has hard-coded project version

--
[...truncated 3050 lines...]
Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

[INFO] Executing: /bin/sh -c cd 
' && 'git' 
'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
atlas-repository ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-repository ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 9 Scala sources and 49 Java sources to 

[WARNING] 
:134:
 warning: non-varargs call of varargs method with inexact argument type for 
last parameter;
[WARNING] LOG.debug("adding entities={}", entities);
[WARNING] ^
[WARNING]   cast to Object for a varargs call
[WARNING]   cast to Object[] for a non-varargs call and to suppress this warning
[WARNING] 
:297:
 warning: non-varargs call of varargs method with inexact argument type for 
last parameter;
[WARNING] LOG.debug("updating entity {}", entitiesUpdated);
[WARNING] ^
[WARNING]   cast to Object for a varargs call
[WARNING]   cast to Object[] for a non-varargs call and to suppress this warning
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[WARNING] 2 warnings
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 49 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-repository ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 8 Scala sources and 27 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 27 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-repository 
---
[WARNING] The parameter forkMode is deprecated since version 2.14. Use 
forkCount and reuseForks 

[jira] [Commented] (ATLAS-735) UI showing incorrect results if two queries are executed.(first query succeeds but second should fail)

[Ayub Khan (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351149#comment-15351149
 ] 

Ayub Khan commented on ATLAS-735:
-

[~yhemanth] This seems to be not happening on new UI, not sure what changed. I 
have tried with 3000 hive tables and search query taking more than 1 minute.

> UI showing incorrect results if two queries are executed.(first query 
> succeeds but second should fail)
> --
>
> Key: ATLAS-735
> URL: https://issues.apache.org/jira/browse/ATLAS-735
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Keval Bhatt
> Attachments: ATLAS-735.patch, DSL-query.gif
>
>
> Steps to repro:
> 1. Through search tab, fire a valid dsl search query(eg: hive_table) and make 
> sure this query response takes time(~30 seconds)
> 2. Before the response comes for the first query, search for another invalid 
> query.(this will fail with 400 error).
> 3. Now when the response for first query returns, the UI still renders the 
> first query's response as if it is a response to second query which seems 
> incorrect. And this might lead to a confusion from a customer's perspective.
> This can be an issue from a customer's perspective and the probability of 
> happening in production is pretty high.
> If the above steps are not clear, I am attaching a GIF which captures the 
> steps to repro. Please take a look.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-735) UI showing incorrect results if two queries are executed.(first query succeeds but second should fail)

[Ayub Khan (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351149#comment-15351149
 ] 

Ayub Khan edited comment on ATLAS-735 at 6/27/16 2:35 PM:
--

[~yhemanth] This seems to be not happening on new UI, not sure what changed. I 
have tried with 3000 hive tables and search query taking more than 30 seconds.


was (Author: ayubkhan):
[~yhemanth] This seems to be not happening on new UI, not sure what changed. I 
have tried with 3000 hive tables and search query taking more than 1 minute.

> UI showing incorrect results if two queries are executed.(first query 
> succeeds but second should fail)
> --
>
> Key: ATLAS-735
> URL: https://issues.apache.org/jira/browse/ATLAS-735
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Keval Bhatt
> Attachments: ATLAS-735.patch, DSL-query.gif
>
>
> Steps to repro:
> 1. Through search tab, fire a valid dsl search query(eg: hive_table) and make 
> sure this query response takes time(~30 seconds)
> 2. Before the response comes for the first query, search for another invalid 
> query.(this will fail with 400 error).
> 3. Now when the response for first query returns, the UI still renders the 
> first query's response as if it is a response to second query which seems 
> incorrect. And this might lead to a confusion from a customer's perspective.
> This can be an issue from a customer's perspective and the probability of 
> happening in production is pretty high.
> If the above steps are not clear, I am attaching a GIF which captures the 
> steps to repro. Please take a look.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-927) aboutAtlas_tmpl.html has hard-coded project version

[Hemanth Yamijala (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350971#comment-15350971
 ] 

Hemanth Yamijala commented on ATLAS-927:


Looks good to me. I can see only one call now. +1.

> aboutAtlas_tmpl.html has hard-coded project version
> ---
>
> Key: ATLAS-927
> URL: https://issues.apache.org/jira/browse/ATLAS-927
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-927.1.patch, ATLAS-927.2.patch, ATLAS-927.patch
>
>
> dashboardv2/public/js/templates/common/aboutAtlas_tmpl.html has hard coded 
> version:
> {code}
> Version :  
> 0.7-incubating-SNAPSHOT-ra2cc01c4342ace7f7a3e3e254d7ede781f990318
> {code}
> Instead, it should use mvn resource filtering to set the version to project 
> version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-735) UI showing incorrect results if two queries are executed.(first query succeeds but second should fail)

[Hemanth Yamijala (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350938#comment-15350938
 ] 

Hemanth Yamijala commented on ATLAS-735:


[~kevalbhatt18] / [~ayubkhan], I cannot reproduce this bug (without the patch) 
on my machine. I mean, if I perform these quick searches, the older results are 
not getting displayed, even if I fire two queries. Since [~ayubkhan] has a 
scenario where this is happening, can you probably take this for a spin?

> UI showing incorrect results if two queries are executed.(first query 
> succeeds but second should fail)
> --
>
> Key: ATLAS-735
> URL: https://issues.apache.org/jira/browse/ATLAS-735
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Keval Bhatt
> Attachments: ATLAS-735.patch, DSL-query.gif
>
>
> Steps to repro:
> 1. Through search tab, fire a valid dsl search query(eg: hive_table) and make 
> sure this query response takes time(~30 seconds)
> 2. Before the response comes for the first query, search for another invalid 
> query.(this will fail with 400 error).
> 3. Now when the response for first query returns, the UI still renders the 
> first query's response as if it is a response to second query which seems 
> incorrect. And this might lead to a confusion from a customer's perspective.
> This can be an issue from a customer's perspective and the probability of 
> happening in production is pretty high.
> If the above steps are not clear, I am attaching a GIF which captures the 
> steps to repro. Please take a look.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-927) aboutAtlas_tmpl.html has hard-coded project version

[Kalyani Kashikar (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350930#comment-15350930
 ] 

Kalyani Kashikar commented on ATLAS-927:


[~yhemanth] Thanks for reviewing, new patch handles above scenario.

> aboutAtlas_tmpl.html has hard-coded project version
> ---
>
> Key: ATLAS-927
> URL: https://issues.apache.org/jira/browse/ATLAS-927
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-927.1.patch, ATLAS-927.2.patch, ATLAS-927.patch
>
>
> dashboardv2/public/js/templates/common/aboutAtlas_tmpl.html has hard coded 
> version:
> {code}
> Version :  
> 0.7-incubating-SNAPSHOT-ra2cc01c4342ace7f7a3e3e254d7ede781f990318
> {code}
> Instead, it should use mvn resource filtering to set the version to project 
> version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-927) aboutAtlas_tmpl.html has hard-coded project version

[Kalyani Kashikar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kalyani Kashikar updated ATLAS-927:
---
Attachment: ATLAS-927.2.patch

> aboutAtlas_tmpl.html has hard-coded project version
> ---
>
> Key: ATLAS-927
> URL: https://issues.apache.org/jira/browse/ATLAS-927
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-927.1.patch, ATLAS-927.2.patch, ATLAS-927.patch
>
>
> dashboardv2/public/js/templates/common/aboutAtlas_tmpl.html has hard coded 
> version:
> {code}
> Version :  
> 0.7-incubating-SNAPSHOT-ra2cc01c4342ace7f7a3e3e254d7ede781f990318
> {code}
> Instead, it should use mvn resource filtering to set the version to project 
> version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Vimal Sharma (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vimal Sharma updated ATLAS-688:
---
Attachment: ATLAS-688-v4.patch

> import-hive should depend on Hive CLASSPATH jars instead of packaging 
> everything
> 
>
> Key: ATLAS-688
> URL: https://issues.apache.org/jira/browse/ATLAS-688
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-688-v2.patch, ATLAS-688-v3.patch, 
> ATLAS-688-v4.patch, ATLAS-688.patch
>
>
> Currently, import-hive.sh packages all hive, hadoop jars etc. Instead it 
> should depend on HIVE_CLASSPATH from which it can get the jars and should be 
> paakged along with hook on hive server m/cs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Vimal Sharma (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vimal Sharma reopened ATLAS-688:


Environment variable HADOOP_HOME or HADOOP_CLASSPATH might not be set but 
command hadoop may be in the PATH. 

Adding a condition to handle this case

> import-hive should depend on Hive CLASSPATH jars instead of packaging 
> everything
> 
>
> Key: ATLAS-688
> URL: https://issues.apache.org/jira/browse/ATLAS-688
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-688-v2.patch, ATLAS-688-v3.patch, ATLAS-688.patch
>
>
> Currently, import-hive.sh packages all hive, hadoop jars etc. Instead it 
> should depend on HIVE_CLASSPATH from which it can get the jars and should be 
> paakged along with hook on hive server m/cs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-927) aboutAtlas_tmpl.html has hard-coded project version

[Hemanth Yamijala (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350896#comment-15350896
 ] 

Hemanth Yamijala commented on ATLAS-927:


Overall functionality looks fine. Just one minor nit: I see that when I select 
the About menu from the UI, it results in two calls being fired for the 
/api/atlas/admin/version URL. This is not a big deal, but would be good to 
avoid in case its hiding any other issue. Can you please check?

> aboutAtlas_tmpl.html has hard-coded project version
> ---
>
> Key: ATLAS-927
> URL: https://issues.apache.org/jira/browse/ATLAS-927
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-927.1.patch, ATLAS-927.patch
>
>
> dashboardv2/public/js/templates/common/aboutAtlas_tmpl.html has hard coded 
> version:
> {code}
> Version :  
> 0.7-incubating-SNAPSHOT-ra2cc01c4342ace7f7a3e3e254d7ede781f990318
> {code}
> Instead, it should use mvn resource filtering to set the version to project 
> version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Apache Jenkins Server]

See 

Changes:

[hyamijala] ATLAS-624 UI: Clicking a tag hyperlink should always result in DSL

--
[...truncated 3050 lines...]
Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

[INFO] Executing: /bin/sh -c cd 
' && 'git' 
'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
atlas-repository ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-repository ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 9 Scala sources and 49 Java sources to 

[WARNING] 
:134:
 warning: non-varargs call of varargs method with inexact argument type for 
last parameter;
[WARNING] LOG.debug("adding entities={}", entities);
[WARNING] ^
[WARNING]   cast to Object for a varargs call
[WARNING]   cast to Object[] for a non-varargs call and to suppress this warning
[WARNING] 
:297:
 warning: non-varargs call of varargs method with inexact argument type for 
last parameter;
[WARNING] LOG.debug("updating entity {}", entitiesUpdated);
[WARNING] ^
[WARNING]   cast to Object for a varargs call
[WARNING]   cast to Object[] for a non-varargs call and to suppress this warning
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[WARNING] 2 warnings
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 49 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-repository ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 8 Scala sources and 27 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 27 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-repository 
---
[WARNING] The parameter forkMode is deprecated since version 2.14. Use 
forkCount and 

[jira] [Commented] (ATLAS-847) UI: Audit versioning does not paginate details from Atlas server

[Kalyani Kashikar (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350839#comment-15350839
 ] 

Kalyani Kashikar commented on ATLAS-847:


[~shwethags] Thanks for suggestion. I will implement next previous button 
instead of page number and I will put page size as 25.

> UI: Audit versioning does not paginate details from Atlas server
> 
>
> Key: ATLAS-847
> URL: https://issues.apache.org/jira/browse/ATLAS-847
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: Kalyani Kashikar
>
> In ATLAS-664, the capability to view Audit events was added to the Atlas 
> admin UI. However, currently, the API call made only fetches the first 100 
> events (which is the default if no count is sent). In order to fetch the next 
> set of events, further API calls need to be made to the Audit API, by 
> providing additional parameters in the API. This JIRA is to track the 
> required changes in UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ATLAS-624) UI: Clicking a tag hyperlink should always result in DSL search. In some cases, results in full-text search.

[Hemanth Yamijala (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hemanth Yamijala resolved ATLAS-624.

   Resolution: Fixed
Fix Version/s: 0.8-incubating

I just committed this. Thanks, [~Kalyanikashikar] for the patch, and 
[~ayubkhan] for reporting it.

> UI: Clicking a tag hyperlink should always result in DSL search. In some 
> cases, results in full-text search.
> 
>
> Key: ATLAS-624
> URL: https://issues.apache.org/jira/browse/ATLAS-624
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Kalyani Kashikar
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-624.1.patch, ATLAS-624.2.patch, ATLAS-624.patch
>
>
> UI: Clicking a tag hyperlink should always result in DSL search.
> 1. Create a hive table with a column, Attach a tag to the column.
> 2. Now navigate to the schema tab of hive_table search result.
> 3. Click on the attached tag - This will result in full-text query search of 
> that tag, which will always return empty response. This should be ideally a 
> DSL search query which will show all the entities associated with that tag.
> Ideally, this should be true in all cases. i.e; Whenever a tag hyperlink is 
> clicked on atlas UI, this should result in DSL search only.
> UI snapshot for reference: 
> https://monosnap.com/file/QKWcuSeG85UI3NDXakvR7iD9LJd1RC



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-624) UI: Clicking a tag hyperlink should always result in DSL search. In some cases, results in full-text search.

[Hemanth Yamijala (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350779#comment-15350779
 ] 

Hemanth Yamijala commented on ATLAS-624:


Looks good to me. I don't know why I saw the difference in the earlier patch, 
but it is working fine now. +1. Will commit.

> UI: Clicking a tag hyperlink should always result in DSL search. In some 
> cases, results in full-text search.
> 
>
> Key: ATLAS-624
> URL: https://issues.apache.org/jira/browse/ATLAS-624
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-624.1.patch, ATLAS-624.2.patch, ATLAS-624.patch
>
>
> UI: Clicking a tag hyperlink should always result in DSL search.
> 1. Create a hive table with a column, Attach a tag to the column.
> 2. Now navigate to the schema tab of hive_table search result.
> 3. Click on the attached tag - This will result in full-text query search of 
> that tag, which will always return empty response. This should be ideally a 
> DSL search query which will show all the entities associated with that tag.
> Ideally, this should be true in all cases. i.e; Whenever a tag hyperlink is 
> clicked on atlas UI, this should result in DSL search only.
> UI snapshot for reference: 
> https://monosnap.com/file/QKWcuSeG85UI3NDXakvR7iD9LJd1RC



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Atlas .7 build fails at the repository step: HMasterCannot assign requested address

[Ernie Ostic]

Hi Everyone...

Trying to get the build to work, in this case on a redhat machine, and
after reviewing various threads and increasing heap size to 1.5G and moving
to a faster disk.that resolved some of the earlier errors, but the
build still continues to fail at this part of the repository step:


Running org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest
Tests run: 6, Failures: 4, Errors: 0, Skipped: 2, Time elapsed: 1.425 sec
<<< FAILURE! - in
org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest
setup(org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest)
Time elapsed: 1.383 sec  <<< FAILURE!
java.lang.RuntimeException: Failed construction of Master: class
org.apache.hadoop.hbase.master.HMasterCannot assign requested address
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at sun.nio.ch.ServerSocketChannelImpl.bind
(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at org.apache.hadoop.hbase.ipc.RpcServer.bind(RpcServer.java:2495)
at org.apache.hadoop.hbase.ipc.RpcServer$Listener.
(RpcServer.java:580)
at org.apache.hadoop.hbase.ipc.RpcServer.(RpcServer.java:1982)
at org.apache.hadoop.hbase.regionserver.RSRpcServices.
(RSRpcServices.java:863)
at org.apache.hadoop.hbase.master.MasterRpcServices.
(MasterRpcServices.java:210)
.
.
.

Currently I am looking in the environment to see what ports might be in use
or in conflict, but open to all ideas.Thank you in advance for any
thoughts on debugging this scenario.

Ernie






Ernie Ostic

WW Product Specialist, Information Server
IBM Analytics
Cell: (617) 331 8238
---
Open IGC is here!

Extend the Catalog with custom objects and lineage definitions!
https://dsrealtime.wordpress.com/2015/07/29/open-igc-is-here/

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

[Apache Jenkins Server]

See 

Changes:

[sshivalingamurthy] ATLAS-947 Return state information in inputs and outputs 
lineage API

[hyamijala] ATLAS-950 Atlas should support Solr that requires Kerberos

--
[...truncated 7252 lines...]
Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

[INFO] Executing: /bin/sh -c cd 
' && 'git' 
'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
atlas-repository ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-repository ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 9 Scala sources and 49 Java sources to 

[WARNING] 
:134:
 warning: non-varargs call of varargs method with inexact argument type for 
last parameter;
[WARNING] LOG.debug("adding entities={}", entities);
[WARNING] ^
[WARNING]   cast to Object for a varargs call
[WARNING]   cast to Object[] for a non-varargs call and to suppress this warning
[WARNING] 
:297:
 warning: non-varargs call of varargs method with inexact argument type for 
last parameter;
[WARNING] LOG.debug("updating entity {}", entitiesUpdated);
[WARNING] ^
[WARNING]   cast to Object for a varargs call
[WARNING]   cast to Object[] for a non-varargs call and to suppress this warning
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[WARNING] 2 warnings
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 49 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-repository ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 8 Scala sources and 27 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 27 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-repository 
---
[WARNING] 

[jira] [Updated] (ATLAS-647) entityText property should be prefixed with __

[Shwetha G S (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shwetha G S updated ATLAS-647:
--
Assignee: (was: Shwetha G S)

> entityText property should be prefixed with __
> --
>
> Key: ATLAS-647
> URL: https://issues.apache.org/jira/browse/ATLAS-647
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>
> All internal properties for the vertex in the repository are prefixed with __ 
> to avoid conflicts with user defined attribute names. Looks like entityText 
> is missed out



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-919) UI : Deleted references should be shown in red or filtered out

[Shwetha G S (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350456#comment-15350456
 ] 

Shwetha G S commented on ATLAS-919:
---

When a deleted table is viewed, sd is displayed for me, but is not marked as 
deleted. Also, when sd is clicked, the sd entity shown is not marked as 
deleted. The API has the deleted state in all these cases

> UI : Deleted references should be shown in red or filtered out
> --
>
> Key: ATLAS-919
> URL: https://issues.apache.org/jira/browse/ATLAS-919
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json, 
> ATLAS-919.1.patch, ATLAS-919.patch, ATLAS-919.rebased.patch, Screen Shot 
> 2016-06-20 at 3.56.33 PM.png, Screen Shot 2016-06-23 at 11.26.17 AM.png
>
>
> Foe eg: In a hive_table one of the columns could be dropped in which case the 
> columns array will have the deleted column as well. This could be completely 
> filtered out in the UI. The way to identify this is to check if the entity 
> state is DELETED when going through the references.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)