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

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-635:


Two minor review comments

1. Rename property aliasList to aliases
2. table name added to list should be in lower case

> Process showing old entity name where as actual entity is renamed.
> --
>
> Key: ATLAS-635
> URL: https://issues.apache.org/jira/browse/ATLAS-635
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Vimal Sharma
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-635-v2.patch, screenshot-1.png
>
>
> Process showing old entity name where as actual entity is renamed.
> Example:
> 1. Create table as select.
> 2. Rename the target table to new name.
> 3. Now check the lineage: The process is still showing the old table name 
> where as the target table is changed. This is confusing from customer 
> perspective.
> One possible solution is:
> Source >   Process(with old name) > Target(old entity name + marked 
> as delete) ---> Process(rename from old to new) ---> Target(with new entity 
> name).



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

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

[Vimal Sharma (JIRA)]

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

Vimal Sharma resolved ATLAS-804.

Resolution: Done

> For hive_db, "locationUri" field is renamed to "location" but the hive data 
> model json is still showing as "locationUri"
> 
>
> Key: ATLAS-804
> URL: https://issues.apache.org/jira/browse/ATLAS-804
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Vimal Sharma
> Fix For: 0.7-incubating
>
>
> As part of ATLAS-758, locationuri field is renamed to location. But the hive 
> data model is still pointing to Locationuri field.



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

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

[Vimal Sharma (JIRA)]

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

Vimal Sharma commented on ATLAS-804:


I tried to recreate the issue but looks like the issue has been already fixed.
[~ayubkhan] Can you please confirm. We can close this afterwards.

> For hive_db, "locationUri" field is renamed to "location" but the hive data 
> model json is still showing as "locationUri"
> 
>
> Key: ATLAS-804
> URL: https://issues.apache.org/jira/browse/ATLAS-804
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Vimal Sharma
> Fix For: 0.7-incubating
>
>
> As part of ATLAS-758, locationuri field is renamed to location. But the hive 
> data model is still pointing to Locationuri field.



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

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

[Vimal Sharma (JIRA)]

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

Vimal Sharma updated ATLAS-635:
---
Attachment: ATLAS-635-v2.patch

> Process showing old entity name where as actual entity is renamed.
> --
>
> Key: ATLAS-635
> URL: https://issues.apache.org/jira/browse/ATLAS-635
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Vimal Sharma
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-635-v2.patch, screenshot-1.png
>
>
> Process showing old entity name where as actual entity is renamed.
> Example:
> 1. Create table as select.
> 2. Rename the target table to new name.
> 3. Now check the lineage: The process is still showing the old table name 
> where as the target table is changed. This is confusing from customer 
> perspective.
> One possible solution is:
> Source >   Process(with old name) > Target(old entity name + marked 
> as delete) ---> Process(rename from old to new) ---> Target(with new entity 
> name).



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

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

[Apache Jenkins Server]

See 

Changes:

[hyamijala] ATLAS-821 Atlas UI - Add arrow to navigate to child term 
(kevalbhatt18

--
[...truncated 5870 lines...]
[INFO] Copying 3 resources
[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 55 Java sources to 

[WARNING] Note: 

 uses or overrides a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[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:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 55 source files to 

[WARNING] 
:
 

 uses or overrides a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[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-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 40 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-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 40 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

[INFO] Webapp assembled in [1587 msecs]
[INFO] Building war: 

[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-webapp ---
[WARNING] The parameter forkMode is deprecated since version 2.14. Use 
forkCount and reuseForks instead.
[INFO] Surefire report directory: 

[INFO] Using configured provider org.apache.maven.surefire.testng.TestNGProvider
[WARNING] file.encoding 

[jira] [Created] (ATLAS-831) Search issues with business terms

[Hemanth Yamijala (JIRA)]

Hemanth Yamijala created ATLAS-831:
--

 Summary: Search issues with business terms
 Key: ATLAS-831
 URL: https://issues.apache.org/jira/browse/ATLAS-831
 Project: Atlas
  Issue Type: Bug
Reporter: Hemanth Yamijala
Priority: Critical


With ATLAS-821 in, there are a couple of issues that we need to think from the 
business terms search perspective. This might involve changes between core, 
taxonomy API and UI. Hence, not filing against any one area.

* Searching for assets associated with a business term returns the taxonomy 
object it is assigned to. This is an artifact of our associating the 'master 
copy' of the business term against the taxonomy object - to root it for lookups.
* More importantly, searching for assets associated to a parent path in the 
business term does not return assets associated to the children. For e.g. if a 
term 'a.b.c' is associated with an asset A, then searching for 'a.b' does not 
return A.



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

[jira] [Resolved] (ATLAS-821) Atlas UI - Add arrow to navigate to child term

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala resolved ATLAS-821.

Resolution: Fixed

I just committed this. Thanks, [~kevalbhatt18]!

> Atlas UI - Add arrow to navigate to child term
> --
>
> Key: ATLAS-821
> URL: https://issues.apache.org/jira/browse/ATLAS-821
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-821.1.patch, ATLAS-821.patch
>
>
> In taxonomy of new UI,  Currently double click is the only way to navigate to 
> child terms, this is not intuitive for end users. 
> In order to make it user friendly for end users, we need to show arrow so 
> that users can use the collapse / expand feature to view terms. 
>  



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

[jira] [Commented] (ATLAS-793) Business Catalog Delete

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-793:


Will start looking at this.

> Business Catalog Delete
> ---
>
> Key: ATLAS-793
> URL: https://issues.apache.org/jira/browse/ATLAS-793
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-793.patch
>
>
> Business Catalog API should support deletion of Terms.



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

[jira] [Updated] (ATLAS-821) Atlas UI - Add arrow to navigate to child term

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala updated ATLAS-821:
---
Attachment: ATLAS-821.1.patch

Attaching the latest patch on behalf of [~kevalbhatt18].

> Atlas UI - Add arrow to navigate to child term
> --
>
> Key: ATLAS-821
> URL: https://issues.apache.org/jira/browse/ATLAS-821
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-821.1.patch, ATLAS-821.patch
>
>
> In taxonomy of new UI,  Currently double click is the only way to navigate to 
> child terms, this is not intuitive for end users. 
> In order to make it user friendly for end users, we need to show arrow so 
> that users can use the collapse / expand feature to view terms. 
>  



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

Podling Report Reminder - June 2016

[johndament]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 15 June 2016, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, June 1st).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.

This should be appended to the Incubator Wiki page at:

http://wiki.apache.org/incubator/May2016

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Review Request 47782: Atlas should use external HBase and SOLR

[Tom Beerbower]

> On May 26, 2016, 6:04 p.m., Shwetha GS wrote:
> > distro/src/conf/hbase_solr-atlas-application.properties, line 2
> > 
> >
> > Instead of adding new files, where configs can go out of sync. Can you 
> > use single file and use resource filtering to populate the values 
> > correctly. Have added ATLAS-823-modified.patch on the jira, check if it 
> > makes sense
> 
> Tom Beerbower wrote:
> Yeah, the replacement values is better.  One question with that... since 
> you are specifying the values for both profiles (dist and embedded_services) 
> which one wins if both profiles are used for the build?  Should the default 
> values (berkeley, elasticsearch) be specified at a global level and then just 
> overridden for the embedded_services profile?  I'll try it out and update the 
> patch.  Thanks.

Updated diff to included changes from your patch.  Thanks.


- Tom


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


On May 26, 2016, 7:14 p.m., Tom Beerbower wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47782/
> ---
> 
> (Updated May 26, 2016, 7:14 p.m.)
> 
> 
> Review request for atlas and Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-823
> https://issues.apache.org/jira/browse/ATLAS-823
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Use of embedded HBase and SOLR is not preferred due to multiple concerns, 
> including:
> 
> 1. lack of support by Ambari makes it difficult to handle kerberization, 
> upgrade/migration, start/stop
> 2. not suitable for production use - no HA, local-storage
> 
> Atlas should remove support for embedded HBase and SOLR. Instead Atlas should 
> be updated to use external HBase and SOLR.
> 
> 
> Diffs
> -
> 
>   distro/pom.xml 1ab092d 
>   distro/src/bin/atlas_config.py 8f3479c 
>   distro/src/bin/atlas_start.py cb869bb 
>   distro/src/conf/atlas-application.properties 26f84e9 
>   distro/src/conf/atlas-env.sh 4f1f46c 
>   distro/src/main/assemblies/standalone-package.xml 09ff47d 
>   docs/src/site/twiki/Configuration.twiki 879c06c 
>   docs/src/site/twiki/InstallationSteps.twiki 006e1e8 
> 
> Diff: https://reviews.apache.org/r/47782/diff/
> 
> 
> Testing
> ---
> 
> updated unit test
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Tom Beerbower
> 
>

Re: Review Request 47782: Atlas should use external HBase and SOLR

[Tom Beerbower]

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

(Updated May 26, 2016, 7:14 p.m.)


Review request for atlas and Hemanth Yamijala.


Bugs: ATLAS-823
https://issues.apache.org/jira/browse/ATLAS-823


Repository: atlas


Description
---

Use of embedded HBase and SOLR is not preferred due to multiple concerns, 
including:

1. lack of support by Ambari makes it difficult to handle kerberization, 
upgrade/migration, start/stop
2. not suitable for production use - no HA, local-storage

Atlas should remove support for embedded HBase and SOLR. Instead Atlas should 
be updated to use external HBase and SOLR.


Diffs (updated)
-

  distro/pom.xml 1ab092d 
  distro/src/bin/atlas_config.py 8f3479c 
  distro/src/bin/atlas_start.py cb869bb 
  distro/src/conf/atlas-application.properties 26f84e9 
  distro/src/conf/atlas-env.sh 4f1f46c 
  distro/src/main/assemblies/standalone-package.xml 09ff47d 
  docs/src/site/twiki/Configuration.twiki 879c06c 
  docs/src/site/twiki/InstallationSteps.twiki 006e1e8 

Diff: https://reviews.apache.org/r/47782/diff/


Testing
---

updated unit test

mvn clean test


Thanks,

Tom Beerbower

[jira] [Commented] (ATLAS-823) Atlas should use external HBase and SOLR

[ATLAS QA (JIRA)]

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

ATLAS QA commented on ATLAS-823:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  
http://issues.apache.org/jira/secure/attachment/12806443/ATLAS-823-modified.patch
  against master revision 705014e.

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

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{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 379 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/256//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/256//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/256//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/256//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/256//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/256//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/256//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/256//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/256//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/256//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/256//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/256//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/256//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/256//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/256//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/256//console

This message is automatically generated.

> Atlas should use external HBase and SOLR
> 
>
> Key: ATLAS-823
> URL: https://issues.apache.org/jira/browse/ATLAS-823
> Project: Atlas
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: ATLAS-823-modified.patch
>
>
> Use of embedded HBase and SOLR is not preferred due to multiple concerns, 
> including:
> # lack of support by Ambari makes it difficult to handle kerberization, 
> upgrade/migration, start/stop
> # not suitable for production use - no HA, local-storage
> Atlas should remove support for embedded HBase and SOLR. Instead Atlas should 
> be updated to use external HBase and SOLR. 



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

Re: Review Request 47782: Atlas should use external HBase and SOLR

[Tom Beerbower]

> On May 26, 2016, 6:04 p.m., Shwetha GS wrote:
> > distro/src/conf/hbase_solr-atlas-application.properties, line 2
> > 
> >
> > Instead of adding new files, where configs can go out of sync. Can you 
> > use single file and use resource filtering to populate the values 
> > correctly. Have added ATLAS-823-modified.patch on the jira, check if it 
> > makes sense

Yeah, the replacement values is better.  One question with that... since you 
are specifying the values for both profiles (dist and embedded_services) which 
one wins if both profiles are used for the build?  Should the default values 
(berkeley, elasticsearch) be specified at a global level and then just 
overridden for the embedded_services profile?  I'll try it out and update the 
patch.  Thanks.


- Tom


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


On May 26, 2016, 2:17 p.m., Tom Beerbower wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47782/
> ---
> 
> (Updated May 26, 2016, 2:17 p.m.)
> 
> 
> Review request for atlas and Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-823
> https://issues.apache.org/jira/browse/ATLAS-823
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Use of embedded HBase and SOLR is not preferred due to multiple concerns, 
> including:
> 
> 1. lack of support by Ambari makes it difficult to handle kerberization, 
> upgrade/migration, start/stop
> 2. not suitable for production use - no HA, local-storage
> 
> Atlas should remove support for embedded HBase and SOLR. Instead Atlas should 
> be updated to use external HBase and SOLR.
> 
> 
> Diffs
> -
> 
>   distro/pom.xml 1ab092d 
>   distro/src/bin/atlas_config.py 8f3479c 
>   distro/src/bin/atlas_start.py cb869bb 
>   distro/src/conf/atlas-application.properties 26f84e9 
>   distro/src/conf/hbase_solr-atlas-application.properties PRE-CREATION 
>   distro/src/conf/hbase_solr-atlas-env.sh PRE-CREATION 
>   distro/src/main/assemblies/standalone-package.xml 09ff47d 
>   docs/src/site/twiki/Configuration.twiki 879c06c 
>   docs/src/site/twiki/InstallationSteps.twiki 006e1e8 
> 
> Diff: https://reviews.apache.org/r/47782/diff/
> 
> 
> Testing
> ---
> 
> updated unit test
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Tom Beerbower
> 
>

Re: Review Request 47782: Atlas should use external HBase and SOLR

[Tom Beerbower]

On May 26, 2016, 6:04 p.m., Tom Beerbower wrote:
> > In the package built using  '-Pdist,embedded_services', atlas_start doesn't 
> > start embedded hbase and solr. is that expected?

You have to run atlas-env.sh first.


- Tom


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


On May 26, 2016, 2:17 p.m., Tom Beerbower wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47782/
> ---
> 
> (Updated May 26, 2016, 2:17 p.m.)
> 
> 
> Review request for atlas and Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-823
> https://issues.apache.org/jira/browse/ATLAS-823
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Use of embedded HBase and SOLR is not preferred due to multiple concerns, 
> including:
> 
> 1. lack of support by Ambari makes it difficult to handle kerberization, 
> upgrade/migration, start/stop
> 2. not suitable for production use - no HA, local-storage
> 
> Atlas should remove support for embedded HBase and SOLR. Instead Atlas should 
> be updated to use external HBase and SOLR.
> 
> 
> Diffs
> -
> 
>   distro/pom.xml 1ab092d 
>   distro/src/bin/atlas_config.py 8f3479c 
>   distro/src/bin/atlas_start.py cb869bb 
>   distro/src/conf/atlas-application.properties 26f84e9 
>   distro/src/conf/hbase_solr-atlas-application.properties PRE-CREATION 
>   distro/src/conf/hbase_solr-atlas-env.sh PRE-CREATION 
>   distro/src/main/assemblies/standalone-package.xml 09ff47d 
>   docs/src/site/twiki/Configuration.twiki 879c06c 
>   docs/src/site/twiki/InstallationSteps.twiki 006e1e8 
> 
> Diff: https://reviews.apache.org/r/47782/diff/
> 
> 
> Testing
> ---
> 
> updated unit test
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Tom Beerbower
> 
>

Review Request 47910: ATLAS-635 Create new propery in Hive table entity to store table alias name(after table operation)

[Vimal Sharma]

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

Review request for atlas, Shwetha GS and Suma Shivaprasad.


Bugs: ATLAS-635
https://issues.apache.org/jira/browse/ATLAS-635


Repository: atlas


Description
---

Store the most recent table alias name in property "aliasList" of a table 
entity. All the previous tablenames can be retrieved using the table entity 
audit.


Diffs
-

  addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
418e755 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/model/HiveDataModelGenerator.java
 347405c 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/model/HiveDataTypes.java 
f376e6e 
  addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
70100f1 

Diff: https://reviews.apache.org/r/47910/diff/


Testing
---

Yes


Thanks,

Vimal Sharma

[jira] [Updated] (ATLAS-826) Add support for singleton traits

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-826:
--
Attachment: (was: ATLAS-826.patch)

> Add support for singleton traits
> 
>
> Key: ATLAS-826
> URL: https://issues.apache.org/jira/browse/ATLAS-826
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
>
> Currently, new trait instance is created everytime the trait is associated 
> with an entity. For cases, where there are no trait attributes, its optimal 
> for storage to share the same trait instance. There can also be cases where 
> the trait instances need to be shared(for example, business catalog where 
> terms are modeled as traits). The concept of singleton trait where single 
> instance of trait is shared is useful in these cases



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

[jira] [Updated] (ATLAS-823) Atlas should use external HBase and SOLR

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-823:
--
Attachment: ATLAS-823-modified.patch

> Atlas should use external HBase and SOLR
> 
>
> Key: ATLAS-823
> URL: https://issues.apache.org/jira/browse/ATLAS-823
> Project: Atlas
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: ATLAS-823-modified.patch
>
>
> Use of embedded HBase and SOLR is not preferred due to multiple concerns, 
> including:
> # lack of support by Ambari makes it difficult to handle kerberization, 
> upgrade/migration, start/stop
> # not suitable for production use - no HA, local-storage
> Atlas should remove support for embedded HBase and SOLR. Instead Atlas should 
> be updated to use external HBase and SOLR. 



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

Re: Review Request 47782: Atlas should use external HBase and SOLR

[Shwetha GS]

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




distro/src/conf/hbase_solr-atlas-application.properties (line 2)


Instead of adding new files, where configs can go out of sync. Can you use 
single file and use resource filtering to populate the values correctly. Have 
added ATLAS-823-modified.patch on the jira, check if it makes sense


In the package built using  '-Pdist,embedded_services', atlas_start doesn't 
start embedded hbase and solr. is that expected?

- Shwetha GS


On May 26, 2016, 2:17 p.m., Tom Beerbower wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47782/
> ---
> 
> (Updated May 26, 2016, 2:17 p.m.)
> 
> 
> Review request for atlas and Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-823
> https://issues.apache.org/jira/browse/ATLAS-823
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Use of embedded HBase and SOLR is not preferred due to multiple concerns, 
> including:
> 
> 1. lack of support by Ambari makes it difficult to handle kerberization, 
> upgrade/migration, start/stop
> 2. not suitable for production use - no HA, local-storage
> 
> Atlas should remove support for embedded HBase and SOLR. Instead Atlas should 
> be updated to use external HBase and SOLR.
> 
> 
> Diffs
> -
> 
>   distro/pom.xml 1ab092d 
>   distro/src/bin/atlas_config.py 8f3479c 
>   distro/src/bin/atlas_start.py cb869bb 
>   distro/src/conf/atlas-application.properties 26f84e9 
>   distro/src/conf/hbase_solr-atlas-application.properties PRE-CREATION 
>   distro/src/conf/hbase_solr-atlas-env.sh PRE-CREATION 
>   distro/src/main/assemblies/standalone-package.xml 09ff47d 
>   docs/src/site/twiki/Configuration.twiki 879c06c 
>   docs/src/site/twiki/InstallationSteps.twiki 006e1e8 
> 
> Diff: https://reviews.apache.org/r/47782/diff/
> 
> 
> Testing
> ---
> 
> updated unit test
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Tom Beerbower
> 
>

Re: Review Request 47638: ATLAS-752 Column rename in Hive should retain traits/tags associated with it

[Vimal Sharma]

> On May 26, 2016, 3:25 a.m., Suma Shivaprasad wrote:
> > addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java, 
> > line 345
> > 
> >
> > its better to load the newTable from metastore here instead of directly 
> > passing it. The reason is some flags and properties on the table are 
> > incorrect/incomplete when they are not reloaded from hive metastore? Any 
> > reason this was done?
> 
> Vimal Sharma wrote:
> If we load newTable from Hive metaStore, it will end up creating a new 
> entity for the table and all its columns. As a result, the traits associated 
> with the column are lost and the test testTraitsPreservedOnColumnRename() 
> fails.
> 
> Suma Shivaprasad wrote:
> Oh ok. I was a bit confused since we were passing in newTable to the 
> function. If we intend to create the old state of table, then should we pass 
> in oldTable(even though it is the same currently but if hive interface 
> changes and starts passing new column state in newTable, there will be 
> unexpected issues later on) or is there any issue with that?

Passing oldTable makes sense considering hive interface might change and start 
passing new column state. Thanks for the observation Suma.
I have made the change in the latest patch.


- Vimal


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


On May 26, 2016, 6:04 p.m., Vimal Sharma wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47638/
> ---
> 
> (Updated May 26, 2016, 6:04 p.m.)
> 
> 
> Review request for atlas and Shwetha GS.
> 
> 
> Bugs: ATLAS-752
> https://issues.apache.org/jira/browse/ATLAS-752
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-752 When a column is renamed, the traits associted with it are lost. 
> The traits should be retained with the new column
> 
> 
> Diffs
> -
> 
>   addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
> 418e755 
>   addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
> 70100f1 
> 
> Diff: https://reviews.apache.org/r/47638/diff/
> 
> 
> Testing
> ---
> 
> 
> File Attachments
> 
> 
> Revised Patch
>   
> https://reviews.apache.org/media/uploaded/files/2016/05/20/a3ab9b8c-4ffc-4ec6-92d7-1f84db246c6a__ATLAS-752-v3.patch
> 
> 
> Thanks,
> 
> Vimal Sharma
> 
>

Re: Review Request 47638: ATLAS-752 Column rename in Hive should retain traits/tags associated with it

[Vimal Sharma]

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

(Updated May 26, 2016, 6:04 p.m.)


Review request for atlas and Shwetha GS.


Bugs: ATLAS-752
https://issues.apache.org/jira/browse/ATLAS-752


Repository: atlas


Description
---

ATLAS-752 When a column is renamed, the traits associted with it are lost. The 
traits should be retained with the new column


Diffs (updated)
-

  addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
418e755 
  addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
70100f1 

Diff: https://reviews.apache.org/r/47638/diff/


Testing
---


File Attachments


Revised Patch
  
https://reviews.apache.org/media/uploaded/files/2016/05/20/a3ab9b8c-4ffc-4ec6-92d7-1f84db246c6a__ATLAS-752-v3.patch


Thanks,

Vimal Sharma

[jira] [Updated] (ATLAS-830) Beeline ignores the command that follows a semicolon and comment

[Muthu Manickam (JIRA)]

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

Muthu Manickam updated ATLAS-830:
-
Description: 
Beeline ignores the next line/command that follows a command with semicolon and 
comments.

Example 1:
select *
from table1; -- comments
select * from table2;

In this case, only the first command is executed.. second command "select * 
from table2" is not executed.

--

Example 2:
select *
from table1; -- comments
select * from table2;
select * from table3;
In this case, first command and third command is executed. second command 
"select * from table2" is not executed.

  was:
Beeline ignores the next line/command that follows a command with semicolon and 
comments.

Example 1:
select *
from table1; -- comments
select * from table2;

In this case, only the first command is executed.. second command "select * 
from table2" is not executed.

Example 2:
select *
from table1; -- comments
select * from table2;
select * from table3;
In this case, first command third command is executed. second command "select * 
from table2" is not executed.


> Beeline ignores the command that follows a semicolon and comment
> 
>
> Key: ATLAS-830
> URL: https://issues.apache.org/jira/browse/ATLAS-830
> Project: Atlas
>  Issue Type: Bug
>Reporter: Muthu Manickam
>
> Beeline ignores the next line/command that follows a command with semicolon 
> and comments.
> Example 1:
> select *
> from table1; -- comments
> select * from table2;
> In this case, only the first command is executed.. second command "select * 
> from table2" is not executed.
> --
> Example 2:
> select *
> from table1; -- comments
> select * from table2;
> select * from table3;
> In this case, first command and third command is executed. second command 
> "select * from table2" is not executed.



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

[jira] [Updated] (ATLAS-830) Beeline ignores the command that follows a semicolon and comment

[Muthu Manickam (JIRA)]

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

Muthu Manickam updated ATLAS-830:
-
Description: 
Beeline ignores the next line/command that follows a command with semicolon and 
comments.

Example 1:
select *
from table1; -- comments
select * from table2;

In this case, only the first command is executed.. second command "select * 
from table2" is not executed.

Example 2:
select *
from table1; -- comments
select * from table2;
select * from table3;
In this case, first command third command is executed. second command "select * 
from table2" is not executed.

> Beeline ignores the command that follows a semicolon and comment
> 
>
> Key: ATLAS-830
> URL: https://issues.apache.org/jira/browse/ATLAS-830
> Project: Atlas
>  Issue Type: Bug
>Reporter: Muthu Manickam
>
> Beeline ignores the next line/command that follows a command with semicolon 
> and comments.
> Example 1:
> select *
> from table1; -- comments
> select * from table2;
> In this case, only the first command is executed.. second command "select * 
> from table2" is not executed.
> Example 2:
> select *
> from table1; -- comments
> select * from table2;
> select * from table3;
> In this case, first command third command is executed. second command "select 
> * from table2" is not executed.



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

[jira] [Updated] (ATLAS-830) Beeline ignores the command that follows a semicolon and comment

[Muthu Manickam (JIRA)]

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

Muthu Manickam updated ATLAS-830:
-
Summary: Beeline ignores the command that follows a semicolon and comment  
(was: Beeline ignores everything that falls after comments at end of line)

> Beeline ignores the command that follows a semicolon and comment
> 
>
> Key: ATLAS-830
> URL: https://issues.apache.org/jira/browse/ATLAS-830
> Project: Atlas
>  Issue Type: Bug
>Reporter: Muthu Manickam
>




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

[jira] [Created] (ATLAS-830) Beeline ignores everything that falls after comments at end of line

[Muthu Manickam (JIRA)]

Muthu Manickam created ATLAS-830:


 Summary: Beeline ignores everything that falls after comments at 
end of line
 Key: ATLAS-830
 URL: https://issues.apache.org/jira/browse/ATLAS-830
 Project: Atlas
  Issue Type: Bug
Reporter: Muthu Manickam






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

[jira] [Commented] (ATLAS-793) Business Catalog Delete

[ATLAS QA (JIRA)]

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

ATLAS QA commented on ATLAS-793:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12806409/ATLAS-793.patch
  against master revision 705014e.

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

{color:green}+1 tests included{color}.  The patch appears to include 5 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 379 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/255//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/255//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/255//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/255//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/255//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/255//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/255//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/255//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/255//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/255//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/255//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/255//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/255//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/255//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/255//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/255//console

This message is automatically generated.

> Business Catalog Delete
> ---
>
> Key: ATLAS-793
> URL: https://issues.apache.org/jira/browse/ATLAS-793
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-793.patch
>
>
> Business Catalog API should support deletion of Terms.



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

[jira] [Commented] (ATLAS-793) Business Catalog Delete

[John Speidel (JIRA)]

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

John Speidel commented on ATLAS-793:


This patch doesn't delete term 'types' because this functionality isn't exposed 
in MetadataService or MetadataRepository.
This doesn't effect business catalog but if users query /types after deleting 
terms in a taxonomy, the type will still exist. 

> Business Catalog Delete
> ---
>
> Key: ATLAS-793
> URL: https://issues.apache.org/jira/browse/ATLAS-793
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: John Speidel
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-793.patch
>
>
> Business Catalog API should support deletion of Terms.



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

Review Request 47898: Implement Business Catalog Delete

[John Speidel]

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

Review request for atlas and Hemanth Yamijala.


Bugs: ATLAS-793
https://issues.apache.org/jira/browse/ATLAS-793


Repository: atlas


Description
---

Provide support for deletion of taxonomies, terms and tags


Diffs
-

  catalog/src/main/java/org/apache/atlas/catalog/AtlasTypeSystem.java 6f2e0be 
  catalog/src/main/java/org/apache/atlas/catalog/BaseRequest.java f3376b0 
  catalog/src/main/java/org/apache/atlas/catalog/BaseResourceProvider.java 
517eaf6 
  catalog/src/main/java/org/apache/atlas/catalog/DefaultTypeSystem.java f71c061 
  catalog/src/main/java/org/apache/atlas/catalog/EntityTagResourceProvider.java 
dc4ab0d 
  catalog/src/main/java/org/apache/atlas/catalog/ResourceProvider.java 4c4319c 
  catalog/src/main/java/org/apache/atlas/catalog/TaxonomyResourceProvider.java 
7a46f5d 
  catalog/src/main/java/org/apache/atlas/catalog/TermResourceProvider.java 
431b06d 
  catalog/src/main/java/org/apache/atlas/catalog/projection/BaseRelation.java 
PRE-CREATION 
  
catalog/src/main/java/org/apache/atlas/catalog/projection/GenericRelation.java 
5f59bea 
  catalog/src/main/java/org/apache/atlas/catalog/projection/TagRelation.java 
a5e15c6 
  catalog/src/main/java/org/apache/atlas/catalog/projection/TraitRelation.java 
5f11474 
  catalog/src/main/java/org/apache/atlas/catalog/query/AtlasEntityQuery.java 
e2bc597 
  catalog/src/main/java/org/apache/atlas/catalog/query/AtlasEntityTagQuery.java 
013bb8a 
  catalog/src/main/java/org/apache/atlas/catalog/query/AtlasTaxonomyQuery.java 
787f734 
  catalog/src/main/java/org/apache/atlas/catalog/query/AtlasTermQuery.java 
0065101 
  catalog/src/main/java/org/apache/atlas/catalog/query/BaseQuery.java c2eabf7 
  
catalog/src/test/java/org/apache/atlas/catalog/EntityTagResourceProviderTest.java
 a95b966 
  
catalog/src/test/java/org/apache/atlas/catalog/TaxonomyResourceProviderTest.java
 9cf3d12 
  catalog/src/test/java/org/apache/atlas/catalog/TermResourceProviderTest.java 
34222ca 
  
catalog/src/test/java/org/apache/atlas/catalog/projection/TagRelationTest.java 
PRE-CREATION 
  
catalog/src/test/java/org/apache/atlas/catalog/query/AtlasEntityQueryTest.java 
838d4c1 
  server-api/src/main/java/org/apache/atlas/services/MetadataService.java 
6bca3df 
  webapp/src/main/java/org/apache/atlas/web/resources/BaseService.java 3982df8 
  webapp/src/main/java/org/apache/atlas/web/resources/EntityService.java 
0e3f4c4 
  webapp/src/main/java/org/apache/atlas/web/resources/TaxonomyService.java 
ccd0b62 

Diff: https://reviews.apache.org/r/47898/diff/


Testing
---

- Added new unit tests
- Ran all existing unit tests
- Manual functional testing of all new functionality


Thanks,

John Speidel

Re: Review Request 47782: Atlas should use external HBase and SOLR

[Tom Beerbower]

> On May 25, 2016, 10:28 a.m., Shwetha GS wrote:
> > 1. Change distro/atlas-application.properties to use berkleydb and 
> > elasticsearch
> > 2. Remove packaging of hbase and solr
> 
> Tom Beerbower wrote:
> So we want to completely revert the embedded HBase and SOLR patches?
> 
> Madhan Neethiraj wrote:
> Yes, I think we should remove HBase and Solr from packaging.
> 
> Shwetha GS wrote:
> Alternatively, we can move the packaging to another profile. But we 
> should revert the config changes, so that default packaging with default 
> configs works

Updated the diff to move the packaging to a different profile.  Berkeley and 
ElasticSearch are the defaults.


- Tom


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


On May 26, 2016, 2:17 p.m., Tom Beerbower wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47782/
> ---
> 
> (Updated May 26, 2016, 2:17 p.m.)
> 
> 
> Review request for atlas and Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-823
> https://issues.apache.org/jira/browse/ATLAS-823
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Use of embedded HBase and SOLR is not preferred due to multiple concerns, 
> including:
> 
> 1. lack of support by Ambari makes it difficult to handle kerberization, 
> upgrade/migration, start/stop
> 2. not suitable for production use - no HA, local-storage
> 
> Atlas should remove support for embedded HBase and SOLR. Instead Atlas should 
> be updated to use external HBase and SOLR.
> 
> 
> Diffs
> -
> 
>   distro/pom.xml 1ab092d 
>   distro/src/bin/atlas_config.py 8f3479c 
>   distro/src/bin/atlas_start.py cb869bb 
>   distro/src/conf/atlas-application.properties 26f84e9 
>   distro/src/conf/hbase_solr-atlas-application.properties PRE-CREATION 
>   distro/src/conf/hbase_solr-atlas-env.sh PRE-CREATION 
>   distro/src/main/assemblies/standalone-package.xml 09ff47d 
>   docs/src/site/twiki/Configuration.twiki 879c06c 
>   docs/src/site/twiki/InstallationSteps.twiki 006e1e8 
> 
> Diff: https://reviews.apache.org/r/47782/diff/
> 
> 
> Testing
> ---
> 
> updated unit test
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Tom Beerbower
> 
>

[jira] [Created] (ATLAS-829) When moved from embedded to standalone hbase, HBASE_CONF_DIR should point to the standalone instance of hbase, otherwise atlas fails to comeup

[Ayub Khan (JIRA)]

Ayub Khan created ATLAS-829:
---

 Summary: When moved from embedded to standalone hbase, 
HBASE_CONF_DIR should point to the standalone instance of hbase, otherwise 
atlas fails to comeup
 Key: ATLAS-829
 URL: https://issues.apache.org/jira/browse/ATLAS-829
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
Reporter: Ayub Khan
 Fix For: 0.7-incubating


When moved from embedded to standalone hbase, HBASE_CONF_DIR in atlas-env.sh 
should point to the standalone instance of hbase, otherwise atlas fails to 
comeup.


{noformat}
2016-05-26 08:35:13,642 INFO  - 
[main-SendThread(os-r7-wbucju-atlas-re-1.openstacklocal:2181):] ~ Session 
establishment complete on server 
os-r7-wbucju-atlas-re-1.openstacklocal/172.22.90.58:2181, sessionid = 
0x154e76760e90022, negotiated timeout = 4 (ClientCnxn:1279)
2016-05-26 08:35:13,661 INFO  - [main:] ~ ClusterId read in ZooKeeper is null 
(ZooKeeperRegistry:107)
2016-05-26 08:35:13,853 WARN  - [main:] ~ Unexpected exception during 
getDeployment() (HBaseStoreManager:397)
java.lang.RuntimeException: java.lang.NullPointerException
at 
org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:208)
at 
org.apache.hadoop.hbase.client.ClientScanner.call(ClientScanner.java:326)
at 
org.apache.hadoop.hbase.client.ClientScanner.nextScanner(ClientScanner.java:301)
at 
org.apache.hadoop.hbase.client.ClientScanner.initializeScannerInConstruction(ClientScanner.java:166)
at 
org.apache.hadoop.hbase.client.ClientScanner.(ClientScanner.java:161)
at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:821)
at 
org.apache.hadoop.hbase.MetaTableAccessor.fullScan(MetaTableAccessor.java:602)
at 
org.apache.hadoop.hbase.MetaTableAccessor.tableExists(MetaTableAccessor.java:366)
at 
org.apache.hadoop.hbase.client.HBaseAdmin.tableExists(HBaseAdmin.java:397)
at 
com.thinkaurelius.titan.diskstorage.hbase.HBaseAdmin1_0.tableExists(HBaseAdmin1_0.java:78)
at 
com.thinkaurelius.titan.diskstorage.hbase.HBaseStoreManager.ensureTableExists(HBaseStoreManager.java:708)
at 
com.thinkaurelius.titan.diskstorage.hbase.HBaseStoreManager.getLocalKeyPartition(HBaseStoreManager.java:511)
at 
com.thinkaurelius.titan.diskstorage.hbase.HBaseStoreManager.getDeployment(HBaseStoreManager.java:352)
at 
com.thinkaurelius.titan.diskstorage.hbase.HBaseStoreManager.getFeatures(HBaseStoreManager.java:395)
at 
com.thinkaurelius.titan.graphdb.configuration.GraphDatabaseConfiguration.(GraphDatabaseConfiguration.java:1276)
at com.thinkaurelius.titan.core.TitanFactory.open(TitanFactory.java:93)
at com.thinkaurelius.titan.core.TitanFactory.open(TitanFactory.java:73)
at 
org.apache.atlas.repository.graph.TitanGraphProvider.getGraphInstance(TitanGraphProvider.java:105)
at 
org.apache.atlas.repository.graph.GraphHelper.(GraphHelper.java:64)
at 
org.apache.atlas.repository.graph.DeleteHandler.(DeleteHandler.java:50)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:190)
at 
org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:102)
at 
org.apache.atlas.RepositoryMetadataModule.getDeleteHandler(RepositoryMetadataModule.java:115)
at 
org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:90)
at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
at 
com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
at com.google.inject.spi.Elements.getElements(Elements.java:110)
at 
com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
at 
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
at com.google.inject.Guice.createInjector(Guice.java:96)
at com.google.inject.Guice.createInjector(Guice.java:73)
at com.google.inject.Guice.createInjector(Guice.java:62)
at 
org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:78)
at 
com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
at 
org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:147)
at 
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
at 
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
at 
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
at 
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
at 

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

[Keval Bhatt (JIRA)]

 [ 
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: Kalyani Kashikar)

> UI: Add Support for Versioning / History
> 
>
> Key: ATLAS-664
> URL: https://issues.apache.org/jira/browse/ATLAS-664
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Keval Bhatt
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-664.patch
>
>
> ATLAS-540 adds REST API support for fetching information about changes to 
> entities stored in Atlas (this is being referred to as versioning). For each 
> detailed page in Atlas, we need to expose the information provided by the 
> REST API in tabular format.
> It makes sense to create a separate tab (next to "tags") on the entity 
> detailed page where this information is displayed.
> The API is straightforward and can be accessed by {guid}/audit
> For more information see:
> https://github.com/apache/incubator-atlas/blob/master/webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java#L612



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

Re: Review Request 47638: ATLAS-752 Column rename in Hive should retain traits/tags associated with it

[Vimal Sharma]

> On May 26, 2016, 3:25 a.m., Suma Shivaprasad wrote:
> > addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java, 
> > line 345
> > 
> >
> > its better to load the newTable from metastore here instead of directly 
> > passing it. The reason is some flags and properties on the table are 
> > incorrect/incomplete when they are not reloaded from hive metastore? Any 
> > reason this was done?

If we load newTable from Hive metaStore, it will end up creating a new entity 
for the table and all its columns. As a result, the traits associated with the 
column are lost and the test testTraitsPreservedOnColumnRename() fails.


- Vimal


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


On May 25, 2016, 6:41 p.m., Vimal Sharma wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47638/
> ---
> 
> (Updated May 25, 2016, 6:41 p.m.)
> 
> 
> Review request for atlas and Shwetha GS.
> 
> 
> Bugs: ATLAS-752
> https://issues.apache.org/jira/browse/ATLAS-752
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-752 When a column is renamed, the traits associted with it are lost. 
> The traits should be retained with the new column
> 
> 
> Diffs
> -
> 
>   addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
> 418e755 
>   addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
> 70100f1 
> 
> Diff: https://reviews.apache.org/r/47638/diff/
> 
> 
> Testing
> ---
> 
> 
> File Attachments
> 
> 
> Revised Patch
>   
> https://reviews.apache.org/media/uploaded/files/2016/05/20/a3ab9b8c-4ffc-4ec6-92d7-1f84db246c6a__ATLAS-752-v3.patch
> 
> 
> Thanks,
> 
> Vimal Sharma
> 
>

[jira] [Commented] (ATLAS-821) Atlas UI - Add arrow to navigate to child term

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-821:


Tested this patch.

One clear issue is that the search is still not being fired correctly. If the 
taxonomy is default > orgs > legal, then the search should be 
{{`default.org.legal`}}. Note that the back-tick (`) is mandatory. I spoke 
offline with [~kevalbhatt18] to show this.

The other issue I am seeing is that lineage is behaving a bit funny. Sometimes 
it is hanging with a javascript error, and sometimes shows empty. Not sure if 
this has anything to do with the patch or my environment. I am trying to verify 
this with master to check once.

> Atlas UI - Add arrow to navigate to child term
> --
>
> Key: ATLAS-821
> URL: https://issues.apache.org/jira/browse/ATLAS-821
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-821.patch
>
>
> In taxonomy of new UI,  Currently double click is the only way to navigate to 
> child terms, this is not intuitive for end users. 
> In order to make it user friendly for end users, we need to show arrow so 
> that users can use the collapse / expand feature to view terms. 
>  



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

[jira] [Created] (ATLAS-828) Entity audit creates lot of records for unchanged entities or irrelevant updates

[Hemanth Yamijala (JIRA)]

Hemanth Yamijala created ATLAS-828:
--

 Summary: Entity audit creates lot of records for unchanged 
entities or irrelevant updates
 Key: ATLAS-828
 URL: https://issues.apache.org/jira/browse/ATLAS-828
 Project: Atlas
  Issue Type: Bug
Reporter: Hemanth Yamijala
 Fix For: 0.7-incubating


Run a script to create 100 hive_tables in the same database.

There will be about 100 audit records for the database indicating there was an 
entity update on it. The information in each update is the same (probably 
there's some timestamp that's changing, haven't looked very carefully).

This is not very useful information, and is likely to make users miss more 
relevant updates to the DB entity.



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

[jira] [Created] (ATLAS-827) Add audit implementation for non-hbase environment

[Shwetha G S (JIRA)]

Shwetha G S created ATLAS-827:
-

 Summary: Add audit implementation for non-hbase environment
 Key: ATLAS-827
 URL: https://issues.apache.org/jira/browse/ATLAS-827
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S
 Fix For: 0.7-incubating


Currently there is HBaseBasedAuditRepository which is hbase based 
implementation for audit store. In the case that hbase is not used for titan, 
there is no alternative implementation



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

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

[Kalyani Kashikar (JIRA)]

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

Kalyani Kashikar commented on ATLAS-664:


Hi [~yhemanth] - wanted clarification on below given comments: 

2) For Tag add event, we don't show any details. The API is passing the added 
tag in the audit response. This can be parsed and shown. 
3) In general, if there is a failure to parse any detail, it is better to show 
the entry as a string, than not to show anything.
>> You mean we do not show Details button for ADD_TAG action? 

6) A usability suggestion. Would it be better to show the actions as "Added 
entity", "Added tag", "Updated entity" instead of the technical looking 
ENTITY_ADDED?
>> Can I please  have list of all the actions and corresponding simplified 
>> labels for the same?

> UI: Add Support for Versioning / History
> 
>
> Key: ATLAS-664
> URL: https://issues.apache.org/jira/browse/ATLAS-664
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Kalyani Kashikar
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-664.patch
>
>
> ATLAS-540 adds REST API support for fetching information about changes to 
> entities stored in Atlas (this is being referred to as versioning). For each 
> detailed page in Atlas, we need to expose the information provided by the 
> REST API in tabular format.
> It makes sense to create a separate tab (next to "tags") on the entity 
> detailed page where this information is displayed.
> The API is straightforward and can be accessed by {guid}/audit
> For more information see:
> https://github.com/apache/incubator-atlas/blob/master/webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java#L612



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

[jira] [Commented] (ATLAS-823) Atlas should use external HBase and SOLR

[Shwetha G S (JIRA)]

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

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

There is InMemoryEntityAuditRepository, we can enable it for now, which is of 
course limited functionality. But for 0.7, we should add either derby/graph 
based one by default (for non-hbase usecases)

> Atlas should use external HBase and SOLR
> 
>
> Key: ATLAS-823
> URL: https://issues.apache.org/jira/browse/ATLAS-823
> Project: Atlas
>  Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> Use of embedded HBase and SOLR is not preferred due to multiple concerns, 
> including:
> # lack of support by Ambari makes it difficult to handle kerberization, 
> upgrade/migration, start/stop
> # not suitable for production use - no HA, local-storage
> Atlas should remove support for embedded HBase and SOLR. Instead Atlas should 
> be updated to use external HBase and SOLR. 



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

Re: Review Request 47782: Atlas should use external HBase and SOLR

[Shwetha GS]

> On May 25, 2016, 10:28 a.m., Shwetha GS wrote:
> > 1. Change distro/atlas-application.properties to use berkleydb and 
> > elasticsearch
> > 2. Remove packaging of hbase and solr
> 
> Tom Beerbower wrote:
> So we want to completely revert the embedded HBase and SOLR patches?
> 
> Madhan Neethiraj wrote:
> Yes, I think we should remove HBase and Solr from packaging.

Alternatively, we can move the packaging to another profile. But we should 
revert the config changes, so that default packaging with default configs works


- Shwetha


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


On May 24, 2016, 5:42 p.m., Tom Beerbower wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47782/
> ---
> 
> (Updated May 24, 2016, 5:42 p.m.)
> 
> 
> Review request for atlas and Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-823
> https://issues.apache.org/jira/browse/ATLAS-823
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Use of embedded HBase and SOLR is not preferred due to multiple concerns, 
> including:
> 
> 1. lack of support by Ambari makes it difficult to handle kerberization, 
> upgrade/migration, start/stop
> 2. not suitable for production use - no HA, local-storage
> 
> Atlas should remove support for embedded HBase and SOLR. Instead Atlas should 
> be updated to use external HBase and SOLR.
> 
> 
> Diffs
> -
> 
>   distro/src/bin/atlas_start.py cb869bb 
>   distro/src/bin/atlas_stop.py a72c724 
>   distro/src/test/python/scripts/TestMetadata.py 00ca3e2 
>   docs/src/site/twiki/Configuration.twiki 879c06c 
>   docs/src/site/twiki/InstallationSteps.twiki 006e1e8 
> 
> Diff: https://reviews.apache.org/r/47782/diff/
> 
> 
> Testing
> ---
> 
> updated unit test
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Tom Beerbower
> 
>