[jira] [Created] (ATLAS-1886) DSL queries with LIKE fail for composite searches

[Hemanth Yamijala (JIRA)]

Hemanth Yamijala created ATLAS-1886:
---

 Summary: DSL queries with LIKE fail for composite searches
 Key: ATLAS-1886
 URL: https://issues.apache.org/jira/browse/ATLAS-1886
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Affects Versions: 0.9-incubating
Reporter: Hemanth Yamijala


Search DSL was enhanced to support the LIKE query in ATLAS-1807. This was a 
great enhancement from a usability point of view and works as expected for 
String attributes of a type - like hive_table.name, hive_table.owner etc.

Another type of query that is useful is composite searches - for e.g. 
hive_tables in a DB (given a DB name). This query currently works - hive_table 
where db.name='xyz'.

However, when we try a 'like' operator here, it fails - i.e. hive_table where 
db.name LIKE '*xyz*' - this returns an error: Discovery query failed 
`hive_table` db.name LIKE '*financ*'

Can this be looked into if its an easy fix?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Incubator report for June 2017 - Draft for review

[Hemanth Yamijala]

Thanks a lot, Chris.

On Wed, Jun 7, 2017 at 9:45 AM, Chris Douglas <cdoug...@apache.org> wrote:
> Signed off. The PODLINGNAMESEARCH JIRA [1] also closed. -C
>
> [1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-118
>
> On Mon, Jun 5, 2017 at 9:34 PM, Hemanth Yamijala <yhema...@gmail.com> wrote:
>> Mentors,
>>
>> May I request you to please sign off on the Incubator report here:
>> https://wiki.apache.org/incubator/June2017. Tomorrow is the last date
>> for submission.
>>
>> Thank you!
>> Hemanth
>>
>> On Sun, Jun 4, 2017 at 12:00 PM, Hemanth Yamijala
>> <hyamij...@hortonworks.com> wrote:
>>> s/Mentor/Mentors/g - apologies for the typo.
>>> 
>>> From: Hemanth Yamijala <hyamij...@hortonworks.com>
>>> Sent: Sunday, June 04, 2017 11:58 AM
>>> To: dev@atlas.incubator.apache.org
>>> Subject: Re: Incubator report for June 2017 - Draft for review
>>>
>>> Atlas community,
>>>
>>> The report has been submitted to Incubator Wiki here: 
>>> https://wiki.apache.org/incubator/June2017
>>>
>>> Mentor, may I request you to please review and sign-off?
>>>
>>> Thanks
>>> hemanth
>>> 
>>> From: Hemanth Yamijala <hyamij...@hortonworks.com>
>>> Sent: Friday, June 02, 2017 9:50 AM
>>> To: dev@atlas.incubator.apache.org
>>> Subject: Re: Incubator report for June 2017 - Draft for review
>>>
>>> Thanks for the review and corrections, Madhan.
>>>
>>> Others - if there are no more corrections, I will update this over the 
>>> weekend on the wiki - so that we can request mentors to sign off.
>>>
>>> Thanks
>>> hemanth
>>> 
>>> From: Madhan Neethiraj <mneethi...@hortonworks.com> on behalf of Madhan 
>>> Neethiraj <mad...@apache.org>
>>> Sent: Wednesday, May 31, 2017 2:11 AM
>>> To: dev@atlas.incubator.apache.org
>>> Subject: Re: Incubator report for June 2017 - Draft for review
>>>
>>> Hemanth,
>>>
>>> Thanks for compiling the report. I updated the report (inline below) for 
>>> the following:
>>>  - included names of new contributors
>>>  - fixed the URL for ‘Resolved JIRAs’ [3]
>>>  - updated the counts for create/resolved JIRAs
>>>
>>> Rest of the contents look good.
>>>
>>> Thanks,
>>> Madhan
>>>
>>>
>>>
>>>
>>> On 5/29/17, 10:03 AM, "Hemanth Yamijala" <hyamij...@hortonworks.com> wrote:
>>>
>>> Atlas community,
>>>
>>> Please find attached the draft of the report to submit to Incubator as 
>>> part of the quarterly reporting process. Please provide feedback on any 
>>> factual errors, missing information etc.
>>>
>>> We need to submit this by June 7th.
>>>
>>> Thanks
>>> hemanth
>>> =
>>>
>>> Atlas
>>>
>>> Apache Atlas is a scalable and extensible set of core foundational 
>>> governance
>>> services that enables enterprises to effectively and efficiently meet 
>>> their
>>> compliance requirements within Hadoop and allows integration with the 
>>> complete
>>> enterprise data ecosystem
>>>
>>> Atlas has been incubating since 2015-05-05.
>>>
>>> Three most important issues to address in the move towards graduation:
>>>
>>> We do not see any issues in moving towards graduation. The dev 
>>> community feel that we are ready for graduation as discussed in this mail 
>>> thread: https://s.apache.org/94xI. We have intimated the IPMC about this 
>>> and are working towards answering some queries raised in the Incubator 
>>> mailing list regarding the same.
>>>
>>>
>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>>> aware of?
>>>
>>> None that we are aware of.
>>>
>>> How has the community developed since the last report?
>>>
>>> 1. Madhan Neethiraj was voted in to the Apache Atlas PPMC.
>>> 2. The following new committers were added:
>>>  - Ayub Khan Pathan
>>>  - Apoorv Naik
>>>  - Kalyani Kashikar
>>>  - N

Re: Incubator report for June 2017 - Draft for review

[Hemanth Yamijala]

Mentors,

May I request you to please sign off on the Incubator report here:
https://wiki.apache.org/incubator/June2017. Tomorrow is the last date
for submission.

Thank you!
Hemanth

On Sun, Jun 4, 2017 at 12:00 PM, Hemanth Yamijala
<hyamij...@hortonworks.com> wrote:
> s/Mentor/Mentors/g - apologies for the typo.
> ____
> From: Hemanth Yamijala <hyamij...@hortonworks.com>
> Sent: Sunday, June 04, 2017 11:58 AM
> To: dev@atlas.incubator.apache.org
> Subject: Re: Incubator report for June 2017 - Draft for review
>
> Atlas community,
>
> The report has been submitted to Incubator Wiki here: 
> https://wiki.apache.org/incubator/June2017
>
> Mentor, may I request you to please review and sign-off?
>
> Thanks
> hemanth
> ____
> From: Hemanth Yamijala <hyamij...@hortonworks.com>
> Sent: Friday, June 02, 2017 9:50 AM
> To: dev@atlas.incubator.apache.org
> Subject: Re: Incubator report for June 2017 - Draft for review
>
> Thanks for the review and corrections, Madhan.
>
> Others - if there are no more corrections, I will update this over the 
> weekend on the wiki - so that we can request mentors to sign off.
>
> Thanks
> hemanth
> 
> From: Madhan Neethiraj <mneethi...@hortonworks.com> on behalf of Madhan 
> Neethiraj <mad...@apache.org>
> Sent: Wednesday, May 31, 2017 2:11 AM
> To: dev@atlas.incubator.apache.org
> Subject: Re: Incubator report for June 2017 - Draft for review
>
> Hemanth,
>
> Thanks for compiling the report. I updated the report (inline below) for the 
> following:
>  - included names of new contributors
>  - fixed the URL for ‘Resolved JIRAs’ [3]
>  - updated the counts for create/resolved JIRAs
>
> Rest of the contents look good.
>
> Thanks,
> Madhan
>
>
>
>
> On 5/29/17, 10:03 AM, "Hemanth Yamijala" <hyamij...@hortonworks.com> wrote:
>
> Atlas community,
>
> Please find attached the draft of the report to submit to Incubator as 
> part of the quarterly reporting process. Please provide feedback on any 
> factual errors, missing information etc.
>
> We need to submit this by June 7th.
>
> Thanks
> hemanth
> =
>
> Atlas
>
> Apache Atlas is a scalable and extensible set of core foundational 
> governance
> services that enables enterprises to effectively and efficiently meet 
> their
> compliance requirements within Hadoop and allows integration with the 
> complete
> enterprise data ecosystem
>
> Atlas has been incubating since 2015-05-05.
>
> Three most important issues to address in the move towards graduation:
>
> We do not see any issues in moving towards graduation. The dev community 
> feel that we are ready for graduation as discussed in this mail thread: 
> https://s.apache.org/94xI. We have intimated the IPMC about this and are 
> working towards answering some queries raised in the Incubator mailing list 
> regarding the same.
>
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> None that we are aware of.
>
> How has the community developed since the last report?
>
> 1. Madhan Neethiraj was voted in to the Apache Atlas PPMC.
> 2. The following new committers were added:
>  - Ayub Khan Pathan
>  - Apoorv Naik
>  - Kalyani Kashikar
>  - Neeru Gupta
>  - Nixon Rodriguez
>  - Sarath Subramanian
> 3. Following contributors have been added to JIRA.
>  - Jan Hentschel
>  - Qinglin Xia
>  - Laxmikanth Malladi
>  - Shi Wang
>  - Christopher Grote
>  - Graham Wallis
>
> How has the project developed since the last report?
>
> 1. Apache Atlas community released version 0.8 of the software on March 
> 31 2017. [1]
> 2. Several new features are in progress or have finished development 
> including enhanced metadata and governance capabilities through typesystem 
> improvements (modeling relationships, glossary), a Virtual Data Connector 
> project, improvements to search capabilities, Export/Import of Atlas graph 
> metadata etc.
> 3. 239 new issues were filed between March 1st 2017 and May 29th [2]. 189 
> issues were resolved in the same time [3]
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>   [ ] Initial setup
>   [ ] Working towards first release
>   [ ] Community building
>   [X] Nearing graduation
>   [ 

Re: Incubator report for June 2017 - Draft for review

[Hemanth Yamijala]

s/Mentor/Mentors/g - apologies for the typo.

From: Hemanth Yamijala <hyamij...@hortonworks.com>
Sent: Sunday, June 04, 2017 11:58 AM
To: dev@atlas.incubator.apache.org
Subject: Re: Incubator report for June 2017 - Draft for review

Atlas community,

The report has been submitted to Incubator Wiki here: 
https://wiki.apache.org/incubator/June2017

Mentor, may I request you to please review and sign-off?

Thanks
hemanth

From: Hemanth Yamijala <hyamij...@hortonworks.com>
Sent: Friday, June 02, 2017 9:50 AM
To: dev@atlas.incubator.apache.org
Subject: Re: Incubator report for June 2017 - Draft for review

Thanks for the review and corrections, Madhan.

Others - if there are no more corrections, I will update this over the weekend 
on the wiki - so that we can request mentors to sign off.

Thanks
hemanth

From: Madhan Neethiraj <mneethi...@hortonworks.com> on behalf of Madhan 
Neethiraj <mad...@apache.org>
Sent: Wednesday, May 31, 2017 2:11 AM
To: dev@atlas.incubator.apache.org
Subject: Re: Incubator report for June 2017 - Draft for review

Hemanth,

Thanks for compiling the report. I updated the report (inline below) for the 
following:
 - included names of new contributors
 - fixed the URL for ‘Resolved JIRAs’ [3]
 - updated the counts for create/resolved JIRAs

Rest of the contents look good.

Thanks,
Madhan




On 5/29/17, 10:03 AM, "Hemanth Yamijala" <hyamij...@hortonworks.com> wrote:

Atlas community,

Please find attached the draft of the report to submit to Incubator as part 
of the quarterly reporting process. Please provide feedback on any factual 
errors, missing information etc.

We need to submit this by June 7th.

Thanks
hemanth
=

Atlas

Apache Atlas is a scalable and extensible set of core foundational 
governance
services that enables enterprises to effectively and efficiently meet their
compliance requirements within Hadoop and allows integration with the 
complete
enterprise data ecosystem

Atlas has been incubating since 2015-05-05.

Three most important issues to address in the move towards graduation:

We do not see any issues in moving towards graduation. The dev community 
feel that we are ready for graduation as discussed in this mail thread: 
https://s.apache.org/94xI. We have intimated the IPMC about this and are 
working towards answering some queries raised in the Incubator mailing list 
regarding the same.


Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

None that we are aware of.

How has the community developed since the last report?

1. Madhan Neethiraj was voted in to the Apache Atlas PPMC.
2. The following new committers were added:
 - Ayub Khan Pathan
 - Apoorv Naik
 - Kalyani Kashikar
 - Neeru Gupta
 - Nixon Rodriguez
 - Sarath Subramanian
3. Following contributors have been added to JIRA.
 - Jan Hentschel
 - Qinglin Xia
 - Laxmikanth Malladi
 - Shi Wang
 - Christopher Grote
 - Graham Wallis

How has the project developed since the last report?

1. Apache Atlas community released version 0.8 of the software on March 31 
2017. [1]
2. Several new features are in progress or have finished development 
including enhanced metadata and governance capabilities through typesystem 
improvements (modeling relationships, glossary), a Virtual Data Connector 
project, improvements to search capabilities, Export/Import of Atlas graph 
metadata etc.
3. 239 new issues were filed between March 1st 2017 and May 29th [2]. 189 
issues were resolved in the same time [3]

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [X] Nearing graduation
  [ ] Other:

Date of last release:

  2017-03-31

When were the last committers or PPMC members elected?

1. PPMC Members - Madhan Neetiraj  (March 5 2017)
2. Committer - Ayub Pathan (March 20 2017)

References:

[1] 
https://lists.apache.org/thread.html/739d520597ea0bf93e9b5649044bc6a92c4660bbc44ffdd94f5bcb21@%3Cdev.atlas.apache.org%3E
[2] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202017-03-01%20AND%20created%20%3C%3D%202017-05-29
[3] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20resolutiondate%20%3E%3D%202017-03-01%20AND%20resolutiondate%20%3C%3D%202017-05-29%20ORDER%20BY%20resolutiondate%2C%20createdDate%20DESC



Signed-off-by:

  [ ](atlas) Arun Murthy
 Comments:
  [ ](atlas) Chris Douglas
 Comments:
  [ ](atlas) Jakob Homan
   

Re: Incubator report for June 2017 - Draft for review

[Hemanth Yamijala]

Atlas community,

The report has been submitted to Incubator Wiki here: 
https://wiki.apache.org/incubator/June2017

Mentor, may I request you to please review and sign-off?

Thanks
hemanth

From: Hemanth Yamijala <hyamij...@hortonworks.com>
Sent: Friday, June 02, 2017 9:50 AM
To: dev@atlas.incubator.apache.org
Subject: Re: Incubator report for June 2017 - Draft for review

Thanks for the review and corrections, Madhan.

Others - if there are no more corrections, I will update this over the weekend 
on the wiki - so that we can request mentors to sign off.

Thanks
hemanth

From: Madhan Neethiraj <mneethi...@hortonworks.com> on behalf of Madhan 
Neethiraj <mad...@apache.org>
Sent: Wednesday, May 31, 2017 2:11 AM
To: dev@atlas.incubator.apache.org
Subject: Re: Incubator report for June 2017 - Draft for review

Hemanth,

Thanks for compiling the report. I updated the report (inline below) for the 
following:
 - included names of new contributors
 - fixed the URL for ‘Resolved JIRAs’ [3]
 - updated the counts for create/resolved JIRAs

Rest of the contents look good.

Thanks,
Madhan




On 5/29/17, 10:03 AM, "Hemanth Yamijala" <hyamij...@hortonworks.com> wrote:

Atlas community,

Please find attached the draft of the report to submit to Incubator as part 
of the quarterly reporting process. Please provide feedback on any factual 
errors, missing information etc.

We need to submit this by June 7th.

Thanks
hemanth
=

Atlas

Apache Atlas is a scalable and extensible set of core foundational 
governance
services that enables enterprises to effectively and efficiently meet their
compliance requirements within Hadoop and allows integration with the 
complete
enterprise data ecosystem

Atlas has been incubating since 2015-05-05.

Three most important issues to address in the move towards graduation:

We do not see any issues in moving towards graduation. The dev community 
feel that we are ready for graduation as discussed in this mail thread: 
https://s.apache.org/94xI. We have intimated the IPMC about this and are 
working towards answering some queries raised in the Incubator mailing list 
regarding the same.


Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

None that we are aware of.

How has the community developed since the last report?

1. Madhan Neethiraj was voted in to the Apache Atlas PPMC.
2. The following new committers were added:
 - Ayub Khan Pathan
 - Apoorv Naik
 - Kalyani Kashikar
 - Neeru Gupta
 - Nixon Rodriguez
 - Sarath Subramanian
3. Following contributors have been added to JIRA.
 - Jan Hentschel
 - Qinglin Xia
 - Laxmikanth Malladi
 - Shi Wang
 - Christopher Grote
 - Graham Wallis

How has the project developed since the last report?

1. Apache Atlas community released version 0.8 of the software on March 31 
2017. [1]
2. Several new features are in progress or have finished development 
including enhanced metadata and governance capabilities through typesystem 
improvements (modeling relationships, glossary), a Virtual Data Connector 
project, improvements to search capabilities, Export/Import of Atlas graph 
metadata etc.
3. 239 new issues were filed between March 1st 2017 and May 29th [2]. 189 
issues were resolved in the same time [3]

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [X] Nearing graduation
  [ ] Other:

Date of last release:

  2017-03-31

When were the last committers or PPMC members elected?

1. PPMC Members - Madhan Neetiraj  (March 5 2017)
2. Committer - Ayub Pathan (March 20 2017)

References:

[1] 
https://lists.apache.org/thread.html/739d520597ea0bf93e9b5649044bc6a92c4660bbc44ffdd94f5bcb21@%3Cdev.atlas.apache.org%3E
[2] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202017-03-01%20AND%20created%20%3C%3D%202017-05-29
[3] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20resolutiondate%20%3E%3D%202017-03-01%20AND%20resolutiondate%20%3C%3D%202017-05-29%20ORDER%20BY%20resolutiondate%2C%20createdDate%20DESC



Signed-off-by:

  [ ](atlas) Arun Murthy
 Comments:
  [ ](atlas) Chris Douglas
 Comments:
  [ ](atlas) Jakob Homan
 Comments:
  [ ](atlas) Vinod Kumar Vavilapalli
 Comments:

IPMC/Shepherd notes:

Re: Incubator report for June 2017 - Draft for review

[Hemanth Yamijala]

Thanks for the review and corrections, Madhan.

Others - if there are no more corrections, I will update this over the weekend 
on the wiki - so that we can request mentors to sign off.

Thanks
hemanth

From: Madhan Neethiraj <mneethi...@hortonworks.com> on behalf of Madhan 
Neethiraj <mad...@apache.org>
Sent: Wednesday, May 31, 2017 2:11 AM
To: dev@atlas.incubator.apache.org
Subject: Re: Incubator report for June 2017 - Draft for review

Hemanth,

Thanks for compiling the report. I updated the report (inline below) for the 
following:
 - included names of new contributors
 - fixed the URL for ‘Resolved JIRAs’ [3]
 - updated the counts for create/resolved JIRAs

Rest of the contents look good.

Thanks,
Madhan




On 5/29/17, 10:03 AM, "Hemanth Yamijala" <hyamij...@hortonworks.com> wrote:

Atlas community,

Please find attached the draft of the report to submit to Incubator as part 
of the quarterly reporting process. Please provide feedback on any factual 
errors, missing information etc.

We need to submit this by June 7th.

Thanks
hemanth
=

Atlas

Apache Atlas is a scalable and extensible set of core foundational 
governance
services that enables enterprises to effectively and efficiently meet their
compliance requirements within Hadoop and allows integration with the 
complete
enterprise data ecosystem

Atlas has been incubating since 2015-05-05.

Three most important issues to address in the move towards graduation:

We do not see any issues in moving towards graduation. The dev community 
feel that we are ready for graduation as discussed in this mail thread: 
https://s.apache.org/94xI. We have intimated the IPMC about this and are 
working towards answering some queries raised in the Incubator mailing list 
regarding the same.


Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

None that we are aware of.

How has the community developed since the last report?

1. Madhan Neethiraj was voted in to the Apache Atlas PPMC.
2. The following new committers were added:
 - Ayub Khan Pathan
 - Apoorv Naik
 - Kalyani Kashikar
 - Neeru Gupta
 - Nixon Rodriguez
 - Sarath Subramanian
3. Following contributors have been added to JIRA.
 - Jan Hentschel
 - Qinglin Xia
 - Laxmikanth Malladi
 - Shi Wang
 - Christopher Grote
 - Graham Wallis

How has the project developed since the last report?

1. Apache Atlas community released version 0.8 of the software on March 31 
2017. [1]
2. Several new features are in progress or have finished development 
including enhanced metadata and governance capabilities through typesystem 
improvements (modeling relationships, glossary), a Virtual Data Connector 
project, improvements to search capabilities, Export/Import of Atlas graph 
metadata etc.
3. 239 new issues were filed between March 1st 2017 and May 29th [2]. 189 
issues were resolved in the same time [3]

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [X] Nearing graduation
  [ ] Other:

Date of last release:

  2017-03-31

When were the last committers or PPMC members elected?

1. PPMC Members - Madhan Neetiraj  (March 5 2017)
2. Committer - Ayub Pathan (March 20 2017)

References:

[1] 
https://lists.apache.org/thread.html/739d520597ea0bf93e9b5649044bc6a92c4660bbc44ffdd94f5bcb21@%3Cdev.atlas.apache.org%3E
[2] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202017-03-01%20AND%20created%20%3C%3D%202017-05-29
[3] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20resolutiondate%20%3E%3D%202017-03-01%20AND%20resolutiondate%20%3C%3D%202017-05-29%20ORDER%20BY%20resolutiondate%2C%20createdDate%20DESC



Signed-off-by:

  [ ](atlas) Arun Murthy
 Comments:
  [ ](atlas) Chris Douglas
 Comments:
  [ ](atlas) Jakob Homan
 Comments:
  [ ](atlas) Vinod Kumar Vavilapalli
 Comments:

IPMC/Shepherd notes:

Incubator report for June 2017 - Draft for review

[Hemanth Yamijala]

Atlas community,

Please find attached the draft of the report to submit to Incubator as part of 
the quarterly reporting process. Please provide feedback on any factual errors, 
missing information etc.

We need to submit this by June 7th.

Thanks
hemanth
=

Atlas

Apache Atlas is a scalable and extensible set of core foundational governance
services that enables enterprises to effectively and efficiently meet their
compliance requirements within Hadoop and allows integration with the complete
enterprise data ecosystem

Atlas has been incubating since 2015-05-05.

Three most important issues to address in the move towards graduation:

We do not see any issues in moving towards graduation. The dev community feel 
that we are ready for graduation as discussed in this mail thread: 
https://s.apache.org/94xI. We have intimated the IPMC about this and are 
working towards answering some queries raised in the Incubator mailing list 
regarding the same.


Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

None that we are aware of.

How has the community developed since the last report?

1. Madhan Neethiraj was voted in to the Apache Atlas PPMC.
2. The following new committers were added:
 - Ayub Khan Pathan
 - Apoorv Naik
 - Kalyani Kashikar
 - Neeru Gupta
 - Nixon Rodriguez
 - Sarath Subramanian
3. At least 5-6 new contributors have been added to JIRA.


How has the project developed since the last report?

1. Apache Atlas community released version 0.8 of the software on March 31 
2017. [1]
2. Several new features are in progress or have finished development including 
enhanced metadata and governance capabilities through typesystem improvements 
(modeling relationships, glossary), a Virtual Data Connector project, 
improvements to search capabilities, Export/Import of Atlas graph metadata etc.
3. 240 new issues were filed between March 1st 2017 and May 29th [2]. 131 
issues were resolved in the same time [3]

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [X] Nearing graduation
  [ ] Other:

Date of last release:

  2017-03-31

When were the last committers or PPMC members elected?

1. PPMC Members - Madhan Neetiraj  (March 5 2017)
2. Committer - Ayub Pathan (March 20 2017)

References:

[1] 
https://lists.apache.org/thread.html/739d520597ea0bf93e9b5649044bc6a92c4660bbc44ffdd94f5bcb21@%3Cdev.atlas.apache.org%3E
[2] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202017-03-01%20AND%20created%20%3C%3D%202017-05-29
[3] 
https://issues.apache.org/jira/browse/ATLAS-1820?jql=project%20%3D%20ATLAS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20created%20%3E%3D%202017-03-01%20AND%20created%20%3C%3D%202017-05-29



Signed-off-by:

  [ ](atlas) Arun Murthy
 Comments:
  [ ](atlas) Chris Douglas
 Comments:
  [ ](atlas) Jakob Homan
 Comments:
  [ ](atlas) Vinod Kumar Vavilapalli
 Comments:

IPMC/Shepherd notes:

Re: [NOTICE] Community Vote for Apache Atlas Graduation to TLP

[Hemanth Yamijala]

Hi John,

I just replied to your email. Given the US holiday, a few of us need some time 
to get back to you and Sam on the responses to your queries.

Thanks
hemanth

From: John D. Ament 
Sent: Monday, May 29, 2017 8:11 PM
To: dev@atlas.incubator.apache.org
Subject: Fwd: [NOTICE] Community Vote for Apache Atlas Graduation to TLP

Atlas Community,

Please see below notes.  There have been no responses on the incubator
lists.

John

-- Forwarded message -
From: Sam Ruby 
Date: Sat, May 27, 2017 at 10:36 PM
Subject: Re: [NOTICE] Community Vote for Apache Atlas Graduation to TLP
To: 


On Thu, May 25, 2017 at 8:45 PM, John D. Ament 
wrote:
> Hi Suma,
>
> Thanks for the heads up.  There is actually no requirement for the podling
> community to vote on graduation, but its a good sign.
>
> I'm a little concerned, can you double check your status file at [1] ?
> Most of the items are marked N/A which is weird, most of these should
> actually have dates.
>
> In addition, can you provide a list of committers you have added since
> starting at Apache?  The podling status report shows none, but it may be
> that your status file is not up to date.
>
> [1]: http://incubator.apache.org/projects/atlas.html

Looking at that page, I note a number of problems with the ids listed there:

bad id   namecorrect id?
===  === =
aahn Andrew Ahn  aa
dkaspar  David Kaspar?
ilasek   Ivo Lasek   ?
chyzer   Chris Hyzer tjbchris
jamesJames Vollmer   ?
adossett Aaron Dossett   dossett
mschussler   Mitch Schussler mitchschussler
VAvasarala   Viswanath Avasarala ?
AVarma   Anil Varma  ?
ssuresh  Suresh Srinivas suresh
vranganathan Venkat Ranganathan  venkatrangan

It would be helpful if one of the mentors went through and updated the PPMC
roster:

https://whimsy.apache.org/roster/ppmc/atlas

One of the things I would like to work on is adding a button to that page
that will draft and post a establish PMC resolution to the board agenda.

- Sam Ruby


> On Thu, May 25, 2017 at 8:33 PM Suma Shivaprasad 
wrote:
>
>> Dear Incubator members,
>>
>> Please note that the community vote for graduating Apache Atlas to TLP
has
>> commenced and has so far received a very positive response from the Atlas
>> community. You can find the vote thread at https://s.apache.org/94xI.
>>
>> Thanks
>> Suma
>>

Re: [VOTE] Graduate Apache Atlas Project from Incubator

[Hemanth Yamijala]

darshanku...@apache.org>
Dave Kantor dkan...@apache.org <mailto:dkan...@apache.org>
David Kaspar dkas...@merck.com <mailto:dkas...@merck.com>
Dennis Fusaro dfus...@aetna.com <mailto:dfus...@aetna.com>
Greg Senia gse...@aetna.com <mailto:gse...@aetna.com>
Harish Butani rhbut...@apache.org <mailto:rhbut...@apache.org>
Hemanth Yamijala yhema...@apache.org <mailto:yhema...@apache.org>
Ivo Lasek ila...@merck.com <mailto:ila...@merck.com>
James Vollmer ja...@target.com <mailto:ja...@target.com>
Jeffrey Hagelberg jnhagelb...@apache.org <mailto:jnhagelb...@apache.org>
Jitendra Pandey jiten...@apache.org <mailto:jiten...@apache.org>
Jon Maron jma...@apache.org <mailto:jma...@apache.org>
Kalyani Kalshikar kalyanikashi...@apache.org <mailto:kalyanikashikar@
apache.org>
Keval Bhatt kbhatt kbh...@apache.org <mailto:kbh...@apache.org>
Madhan Neethiraj mad...@apache.org <mailto:mad...@apache.org>
Mitch Schussler mschuss...@apache.org <mailto:mschuss...@apache.org>
Neeru Gupta guptane...@us.ibm.com <mailto:guptane...@us.ibm.com>
Nixon Rodrigues ni...@apache.org <mailto:ni...@apache.org>
Sarath Subramanian sar...@apache.org <mailto:sar...@apache.org>
Shwetha GS  shweth...@apache.org <mailto:shweth...@apache.org>
Srikanth Sundarrajan srik...@apache.org <mailto:srik...@apache.org>
Suma Shivaprasad suma...@apache.org <mailto:suma...@apache.org>
Suresh Srinivas ssur...@apache.org <mailto:ssur...@apache.org>
Tom Beerbower tbeerbo...@apache.org <mailto:tbeerbo...@apache.org>
Venkat Ranganathan vranganat...@apache.org <mailto:vranganat...@apache.org>
Venkatesh Seetharam venkat...@apache.org <mailto:venkat...@apache.org>
Vimal Sharma svimal2...@apache.org <mailto:svimal2...@apache.org>
Vinod Kumar Vavilapalli vino...@apache.org <mailto:vino...@apache.org>
Viswanath Avasarala vavasar...@slb.com <mailto:vavasar...@slb.com>


NOW, THEREFORE, BE IT FURTHER RESOLVED, that "Madhan Neethiraj" be
appointed to the office of Vice President, Apache Atlas, to serve in
accordance with and
subject to the direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed; and be it further
RESOLVED, that the initial Apache Atlas PMC be and hereby is tasked with
the creation of a set of bylaws intended to encourage open development and
increased participation in the Apache Atlas Project; and be it further

RESOLVED, that the Apache Atlas Project be and hereby is tasked with the
migration of the Apache Incubator Atlas podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
Atlas polling encumbered upon the Apache Incubator Project are hereafter
discharged.

Thanks
Suma

​

Re: Please add me to the contributors list

[Hemanth Yamijala]

Done. Can you please check?

From: Jan Hentschel 
Sent: Friday, May 19, 2017 11:53 PM
To: dev@atlas.incubator.apache.org
Subject: Please add me to the contributors list

Hi,



I currently have some tickets in JIRA, which I would like to assign to myself. 
Could you please add me to the appropriate group in JIRA? My JIRA ID is “Jan 
Hentschel”.



Best, Jan

Re: Please add me to the contributors list

[Hemanth Yamijala]

Hi Qinglin,

Could you please provide Apache IDs for both of you?

I think yours is xiaqinglin, but want to be sure.. I couldn't find your 
colleague's ID without the full name.

Thanks
hemanth

From: qinglin Xia 
Sent: Friday, May 19, 2017 11:32 AM
To: dev@atlas.incubator.apache.org
Subject: Re: Please add me to the contributors list

Hi, All, me and my colleague (luo850589...@foxmail.com) are working on the
hbase and hdfs bridge for some time and already got some progress, we two
would want to make some contribution for the atlas project, is it possible
that you can accpet us two as contributors?

Thanks
Qinglin

On Fri, May 19, 2017 at 4:21 AM, Madhan Neethiraj  wrote:

> Laxmi,
>
> Welcome to Atlas. Thanks for your interest in contributing to Atlas. You
> have been added as a contributor.
>
> Thanks,
> Madhan
>
>
>
> On 5/18/17, 8:53 AM, "Laxmikanth Malladi"  wrote:
>
> Hi All - I have been part of the DL for some time and I would like to
> start
> contributing the project as I'm already using for couple of PoC's.
>
> Thanks,
> Laxmi
>
>
> On Mon, May 15, 2017 at 5:56 PM, Madhan Neethiraj <
> mneethi...@hortonworks.com> wrote:
>
> > Shi,
> >
> > Welcome to Atlas. You have been added as a contributor to Apache
> Atlas.
> >
> > Madhan
> >
> > On 5/15/17, 2:24 PM, "Shi Wang"  wrote:
> >
> > Hi,
> >
> > I would like to contribute to atlas projects, please help add me
> to the
> > contributors list, thanks!
> >
> > Best,
> > Shi
> >
> >
> >
> >
> >
>
>
>
>


--
Regards
Qinglin, Xia
(510)-709-8125

[jira] [Commented] (ATLAS-1818) Performance of Basic Search that Uses indexQuery Takes Long Time to Fetch Results

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-1818:
-

[~ashutoshm], thanks for taking up this really useful improvement!

One question: Regarding your last point - is the intention to provide faceted 
search in searchUsingBasicQuery that might follow a Lucene syntax or some such?

> Performance of Basic Search that Uses indexQuery Takes Long Time to Fetch 
> Results
> -
>
> Key: ATLAS-1818
> URL: https://issues.apache.org/jira/browse/ATLAS-1818
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Affects Versions: trunk, 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
> Fix For: trunk, 0.8-incubating
>
> Attachments: ATLAS-1818.patch
>
>   Original Estimate: 120h
>  Time Spent: 96h
>  Remaining Estimate: 24h
>
> h3. Background
> An environment that is setup with 100K hive_tables each with 84 columns.
> The basic search with query parameter specified is executed. Results take 75 
> secs to appear.
> h3. Analysis & Findings
> Similar test was performed with smaller data set (200 hive_tables each with 
> 81 columns) resulted in less than ideal performance.
> Atlas Basic Search API uses _graph.indexQuery_ for performing search. This 
> uses _Solr_ for doing the search.
> There are 2 aspects that affect performance:
> * Solr's default for returning max query set when no limit is specified is 
> 100K. In the test scenario, this is returning entire result set.
> * Once result set is returned, _EntityDiscoveryService.searchUsingBasicQuery_ 
> does a sequential scan to weed out pertinent data. This operation is 
> proportional to size of the result set. 
> h3. Solution
> Following changes will improve performance:
> * Solr's max result set property is governed by 
> _atlas.graph.index.search.max-result-set-size_. It will make sense to set 
> this to a lower number.
> * Modify Solr's configuration _solrconfig.xml_ to use _FastLRUCache_.
> * Modify _EntityDiscoveryService.searchUsingBasicQuery_ to form a query that 
> takes additional paramters.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Hi

[Hemanth Yamijala]

Hi,

Could you please elaborate your requirement with an example or a couple, 
ideally. What kind of rules are you looking at?

Thanks
Hemanth

From: kant kodali 
Sent: Monday, May 01, 2017 3:51 AM
To: dev@atlas.incubator.apache.org
Subject: Hi

Hi All,

Is there any way I can specify a rule so I can see all the Lineages that
satisfy that rule In Apache Atlas?

Thanks!

Re: Access as JIRA and Confluence contributor

[Hemanth Yamijala]

Added to JIRA. Please check.

From: Christopher Grote 
Sent: Friday, April 28, 2017 8:35 PM
To: dev@atlas.incubator.apache.org
Subject: Access as JIRA and Confluence contributor

Dear all,

Would it be possible to please add me as a JIRA and Confluence contributor
for Atlas?

I'd like to be able to assign myself work (JIRA), as well as contribute
some documentation to the Confluence wiki.

My userid for both is "cmgrote".

Many thanks!

Cheers,
Chris

---
Christopher Grote - Executive IT Architect for Banking & Financial Markets
- Member, IBM Academy of Technology - christopher.gr...@uk.ibm.com
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [DISCUSS] Ready to graduate?

[Hemanth Yamijala]

+1 from me as well.

It has been a pleasure  being involved with Atlas and see the product and 
community grow.

Thanks, Chris, for starting this thread.

Hemanth

From: Jakob Homan 
Sent: Thursday, April 27, 2017 4:27 AM
To: dev@atlas.incubator.apache.org
Subject: Re: [DISCUSS] Ready to graduate?

+1.

I've not been very involved with the day-to-day bits of the project as
Mentor, so when the new PMC is constituted, there's no need to include
me.  But I'll stay a fan of Atlas after graduation.

-Jakob

On 26 April 2017 at 15:29, Suma Shivaprasad
 wrote:
> +1. Agreed
>
> The community is really vibrant/active with many companies involved in
> shaping the roadmap and features.
>  It has also grown a lot from past year with a lot of interest from users
> and this is a great time to propose for graduation
>
> I volunteer to start working on the graduation and take this forward if no
> one else has any objections.
>
> Thanks
> Suma
>
>
>
>
>
> On Wed, Apr 26, 2017 at 2:03 AM, Nigel L Jones  wrote:
>
>>
>>
>> +1 from me.
>>
>> The Atlas community is vibrant, we have engagement from multiple companies,
>> and the industry interest around governance is immense, as witnessed at
>> recent conferences. It's exciting to see it evolve and getting it into a
>> TLP will be another tick in the box as seen by potential users.
>>
>> Let's go for it!
>>
>> -Original Message-
>> From: Mandy Chessell [mailto:mandy_chess...@uk.ibm.com]
>> Sent: 26 April 2017 07:30
>> To: dev@atlas.incubator.apache.org
>> Subject: Re: [DISCUSS] Ready to graduate?
>>
>> Hello Chris,
>> No concerns at all ... we have a vibrant, multi-company community that is
>> working together to expand Atlas's capability to be THE open metadata and
>> governance platform for data and analytics.  Many other
>> people/organizations are eager to consume the results.   Moving the
>> project out of incubation sends a strong message to our stakeholders and
>> users that Atlas is here to stay and through that we can strengthen the
>> community further.
>>
>> All the best
>> Mandy
>> ___
>> Mandy Chessell CBE FREng CEng FBCS
>> IBM Distinguished Engineer
>>
>> Master Inventor
>> Member of the IBM Academy of Technology
>> Visiting Professor, Department of Computer Science, University of Sheffield
>>
>> Email: mandy_chess...@uk.ibm.com
>> LinkedIn: http://www.linkedin.com/pub/mandy-chessell/22/897/a49
>>
>> Assistant: Janet Brooks - jsbrook...@uk.ibm.com
>>
>>
>>
>> From:   Chris Douglas 
>> To: dev@atlas.incubator.apache.org
>> Date:   26/04/2017 01:45
>> Subject:[DISCUSS] Ready to graduate?
>>
>>
>>
>> Hey Atlas folk-
>>
>> The name search JIRA is filled in [1] (thanks Madhan!), pending approval
>> from VP trademarks. Independent of its resolution, does the community feel
>> it is ready to graduate?
>>
>> As far as I've observed, the project is more than ready to be a top-level
>> project. Are there any concerns we should discuss before we proceed?
>>
>> The process, roughly:
>> 1. Community discussion of graduation
>> 2. [VOTE] to graduate (PPMC votes binding) 3. Cite thread in
>> general@incubator for discussion/vote (IPMC votes
>> binding)
>> 4. Add a resolution to the board agenda establishing Atlas as a top-level
>> project 5. ASF board approves the resolution at its next meeting, Atlas
>> becomes a TLP
>>
>> The project will also need to pick a chair for the new PMC. We can discuss
>> that when we post the resolution. -C
>>
>> [1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-118
>>
>>
>> Unless stated otherwise above:
>> IBM United Kingdom Limited - Registered in England and Wales with number
>> 741598.
>> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>>
>>

Re: Access as JIRA contributor

[Hemanth Yamijala]

Done. Please check and let us know if you're not able to access still as a 
contributor.

Thanks
hemanth

From: Mandy Chessell 
Sent: Monday, April 24, 2017 4:34 PM
To: dev@atlas.incubator.apache.org
Subject: Access as JIRA contributor

Dear All,
Would it be possible to add me to the JIRA contributor access for Atlas?

My JIRA userid is "mandy_chessell"

All the best
Mandy
___
Mandy Chessell CBE FREng CEng FBCS
IBM Distinguished Engineer

Master Inventor
Member of the IBM Academy of Technology
Visiting Professor, Department of Computer Science, University of
Sheffield

Email: mandy_chess...@uk.ibm.com
LinkedIn: http://www.linkedin.com/pub/mandy-chessell/22/897/a49

Assistant: Janet Brooks - jsbrook...@uk.ibm.com

[jira] [Commented] (ATLAS-1707) Atlas WUI on continues loading behind FireWall

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-1707:
-

Looks good to me. +1.

Thanks

> Atlas WUI on continues loading behind FireWall
> --
>
> Key: ATLAS-1707
> URL: https://issues.apache.org/jira/browse/ATLAS-1707
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.7-incubating
> Environment: Atlas: Version":"0.7.0.2.5.3
> JDK 1.8
> Linux
>Reporter: Ernani Pereira de Mattos Junior
>Assignee: Nixon Rodrigues
>  Labels: patch, test
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1707.2.patch, ATLAS-1707.patch, index.html, 
> index.html.original
>
>
> Atlas is behind a FW in which does return a response. We Identify index.html 
> was loading googleapis css does not have a timeout and proceed with the WUI;
> ref:http://tinyurl.com/lan4by9 
> By removing the bellow line from the html file, there were no problem. 
>  href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,400italic,600,600italic,700,700italic;
>  rel="stylesheet" type="text/css">
> 1. Shouldn't be applications self-contain in case of such situation?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1707) Atlas WUI on continues loading behind FireWall

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-1707:
-

[~ashutoshm], I believe we might need something slightly different. 

Firstly, the specific fonts we are using are licensed under Open Font License. 
Please see https://fonts.google.com/specimen/Source+Sans+Pro. This is the font 
we use, AFAIK. The general process is to copy the license text of the actual 
license into a file (as you've done) under the 3rdparty licenses folder.

Next, we must reference this from the LICENSE file in the top folder of the 
Atlas project. For e.g. like in this line:

This product bundles bootstrap-datepicker 4.14.30, which is available under
MIT License.  For details, see 3party-licenses/bootstrap-datepicker-LICENSE

> Atlas WUI on continues loading behind FireWall
> --
>
> Key: ATLAS-1707
> URL: https://issues.apache.org/jira/browse/ATLAS-1707
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.7-incubating
> Environment: Atlas: Version":"0.7.0.2.5.3
> JDK 1.8
> Linux
>Reporter: Ernani Pereira de Mattos Junior
>Assignee: Nixon Rodrigues
>  Labels: patch, test
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1707.1.patch, ATLAS-1707.patch, index.html, 
> index.html.original
>
>
> Atlas is behind a FW in which does return a response. We Identify index.html 
> was loading googleapis css does not have a timeout and proceed with the WUI;
> ref:http://tinyurl.com/lan4by9 
> By removing the bellow line from the html file, there were no problem. 
>  href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,400italic,600,600italic,700,700italic;
>  rel="stylesheet" type="text/css">
> 1. Shouldn't be applications self-contain in case of such situation?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ATLAS-1707) Atlas WUI on continues loading behind FireWall

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-1707:
-

We may need to make sure that the Open Font License is included in the License 
file we have. Please verify this. Can be done in another JIRA if required.

> Atlas WUI on continues loading behind FireWall
> --
>
> Key: ATLAS-1707
> URL: https://issues.apache.org/jira/browse/ATLAS-1707
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.7-incubating
> Environment: Atlas: Version":"0.7.0.2.5.3
> JDK 1.8
> Linux
>Reporter: Ernani Pereira de Mattos Junior
>Assignee: Nixon Rodrigues
>  Labels: patch, test
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-1707.patch, index.html, index.html.original
>
>
> Atlas is behind a FW in which does return a response. We Identify index.html 
> was loading googleapis css does not have a timeout and proceed with the WUI;
> ref:http://tinyurl.com/lan4by9 
> By removing the bellow line from the html file, there were no problem. 
>  href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,400italic,600,600italic,700,700italic;
>  rel="stylesheet" type="text/css">
> 1. Shouldn't be applications self-contain in case of such situation?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

New committer to Apache Atlas: Ayub Pathan

[Hemanth Yamijala]

Atlas dev community,

The Podling Project Management Committee (PPMC) for Apache Atlas
has invited Ayub Pathan to become a committer and we are pleased
to announce that he has accepted.

Congratulations, Ayub! Thanks for your many efforts in ensuring the
quality of the Atlas project.

thanks,
Hemanth

[jira] [Commented] (ATLAS-1704) amend Atlas simple security to add glossary

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-1704:
-

Is this different from ATLAS-1703? Seems to be a duplicate.

> amend Atlas simple security to add glossary  
> -
>
> Key: ATLAS-1704
> URL: https://issues.apache.org/jira/browse/ATLAS-1704
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: David Radley
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

New committer to Apache Atlas: Apoorv Naik

[Hemanth Yamijala]

Atlas dev community,

The Project Management Committee (PMC) for Apache Atlas
has invited Apoorv Naik to become a committer and we are pleased
to announce that he has accepted.

Congratulations, Apoorv!

thanks,
Hemanth

Re: [VOTE] Release Apache Atlas 0.8 (incubating) - release candidate 0 (dev group vote)

[Hemanth Yamijala]

Folks - David / Venkat,

The latest release candidate is RC1. There is a separate thread on this where 
there are a lots of votes. Could you please transfer your votes there so there 
is no confusion.

Madhan, I guess it will be better to [CLOSE] this vote as cancelled.

Thanks
Hemanth

From: Venkat Ranganathan 
Sent: Friday, March 10, 2017 7:16 PM
To: dev@atlas.incubator.apache.org
Subject: Re: [VOTE] Release Apache Atlas 0.8 (incubating) - release candidate 0 
(dev group vote)

+1

Built and Ran tests


Venkat

From: David Radley 
Sent: Friday, March 10, 2017 1:42 AM
To: dev@atlas.incubator.apache.org
Subject: Re: [VOTE] Release Apache Atlas 0.8 (incubating) - release candidate 0 
(dev group vote)

+1 from me.



From:   Madhan Neethiraj 
To: "dev@atlas.incubator.apache.org" 
Date:   07/03/2017 09:54
Subject:[VOTE] Release Apache Atlas 0.8 (incubating) - release
candidate 0 (dev group vote)



Atlas team,



Apache Atlas 0.8 (incubating) release candidate #0 is now available for a
vote within dev community. Links to the release artifacts are given below.
Can you please review and vote?



The vote will be open for at least 72 hours or until necessary votes are
reached.

[ ] +1  approve

[ ] +0  no opinion

[ ] -1  disapprove (and reason why)



Here is my +1



Thanks,

Madhan





List of improvements and issues addressed in this release:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20Atlas%20AND%20status%20%3D%20Resolved%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.8-incubating%20ORDER%20BY%20key%20DESC




Git tag for the release:
https://github.com/apache/incubator-atlas/tree/release-0.8-rc0



Sources for the release:
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.8-incubating-rc0/apache-atlas-0.8-incubating-sources.tar.gz




Source release verification:

  PGP Signature:
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.8-incubating-rc0/apache-atlas-0.8-incubating-sources.tar.gz.asc


  MD5 Hash:
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.8-incubating-rc0/apache-atlas-0.8-incubating-sources.tar.gz.md5




Keys to verify the signature of the release artifacts are available at:
https://dist.apache.org/repos/dist/dev/incubator/atlas/KEYS












Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [VOTE] Release Apache Atlas 0.8 (incubating) - release candidate 1 (dev group vote)

[Hemanth Yamijala]

Hi Vimal,

Your vote should be binding.

Thanks
Hemanth

From: Vimal Sharma 
Sent: Thursday, March 09, 2017 1:26 PM
To: dev@atlas.incubator.apache.org
Subject: Re: [VOTE] Release Apache Atlas 0.8 (incubating) - release candidate 1 
(dev group vote)

+1(non binding) for the release

- Verified checksum and signature
- Build successful and all tests are passing (One IT in webapp failed but 
succeeded in rerun)
- Built with external Hbase and Solr
- Verified basic functionality using QuickStart


Thanks
Vimal




On 3/9/17, 11:53 AM, "Sarath Kumar Subramanian"  
wrote:

>   - Verified md5 checksum and signature.
>   - No binaries in source
>   - Build successful with embedded hbase-solr
>   - Verified Quickstart, lineage, tags and search
>   - Basic Sanity test
>
>+1 (non-binding) for the release.
>
>
>Thanks,
>Sarath Subramanian
>
>
>On Wed, Mar 8, 2017 at 9:10 PM, Ayub Khan Pathan 
>wrote:
>
>>   +1 (non-binding vote) for the release.
>>
>> - Verified “incubating” tag existence
>> - Verified for successful build
>> - Sanity tests are successful.
>>
>> Thanks
>> Ayub Khan
>>
>> On 3/8/17, 1:30 PM, "Madhan Neethiraj"  wrote:
>>
>> Atlas team,
>>
>>
>>
>> Apache Atlas 0.8 (incubating) release candidate #1 is now available
>> for a vote within dev community. Links to the release artifacts are given
>> below. Can you please review and vote?
>>
>>
>>
>> This update includes fix for the following JIRAS: ATLAS-1648,
>> ATLAS-1655, ATLAS-1656, ATLAS-1657, ATLAS-1658
>>
>>
>>
>> The vote will be open for at least 72 hours or until necessary votes
>> are reached.
>>
>> [ ] +1  approve
>>
>> [ ] +0  no opinion
>>
>> [ ] -1  disapprove (and reason why)
>>
>>
>>
>> Here is my +1
>>
>>
>>
>> Thanks,
>>
>> Madhan
>>
>>
>>
>>
>>
>> List of improvements and issues addressed in this release:
>> https://issues.apache.org/jira/issues/?jql=project%20%
>> 3D%20Atlas%20AND%20status%20%3D%20Resolved%20AND%
>> 20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.
>> 8-incubating%20ORDER%20BY%20key%20DESC
>>
>>
>>
>> Git tag for the release: https://github.com/apache/
>> incubator-atlas/tree/release-0.8-rc1
>>
>>
>>
>> Sources for the release: https://dist.apache.org/repos/
>> dist/dev/incubator/atlas/0.8-incubating-rc1/apache-atlas-0.
>> 8-incubating-sources.tar.gz
>>
>>
>>
>> Source release verification:
>>
>>   PGP Signature:  https://dist.apache.org/repos/
>> dist/dev/incubator/atlas/0.8-incubating-rc1/apache-atlas-0.
>> 8-incubating-sources.tar.gz.asc
>>
>>   MD5 Hash:   https://dist.apache.org/repos/
>> dist/dev/incubator/atlas/0.8-incubating-rc1/apache-atlas-0.
>> 8-incubating-sources.tar.gz.md5
>>
>>
>>
>> Keys to verify the signature of the release artifacts are available
>> at: https://dist.apache.org/repos/dist/dev/incubator/atlas/KEYS
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>

Re: [VOTE] Release Apache Atlas 0.8 (incubating) - release candidate 1 (dev group vote)

[Hemanth Yamijala]

Verified the following:

- No binaries in source distro.
- MD5 checksum matches
- Tag exists and pointing to right source.
- Builds fine. There was a test failure in atlas-webapp module - which
is documented in the README already.
- Setup an Atlas instance pointing to HBase and Solr. Server came up fine.
- Ran quickstart and verified the UI is showing up types, lineage,
tags, search correctly.
- NOTICE, DISCLAIMER, LICENSE files exist.
- Licenses for all modules in external JS folder are referenced in LICENSE file.

+1 for the release based on the above tests.

Thanks
Hemanth


On Wed, Mar 8, 2017 at 1:30 PM, Madhan Neethiraj  wrote:
> Atlas team,
>
>
>
> Apache Atlas 0.8 (incubating) release candidate #1 is now available for a 
> vote within dev community. Links to the release artifacts are given below. 
> Can you please review and vote?
>
>
>
> This update includes fix for the following JIRAS: ATLAS-1648, ATLAS-1655, 
> ATLAS-1656, ATLAS-1657, ATLAS-1658
>
>
>
> The vote will be open for at least 72 hours or until necessary votes are 
> reached.
>
> [ ] +1  approve
>
> [ ] +0  no opinion
>
> [ ] -1  disapprove (and reason why)
>
>
>
> Here is my +1
>
>
>
> Thanks,
>
> Madhan
>
>
>
>
>
> List of improvements and issues addressed in this release: 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20Atlas%20AND%20status%20%3D%20Resolved%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.8-incubating%20ORDER%20BY%20key%20DESC
>
>
>
> Git tag for the release: 
> https://github.com/apache/incubator-atlas/tree/release-0.8-rc1
>
>
>
> Sources for the release: 
> https://dist.apache.org/repos/dist/dev/incubator/atlas/0.8-incubating-rc1/apache-atlas-0.8-incubating-sources.tar.gz
>
>
>
> Source release verification:
>
>   PGP Signature:  
> https://dist.apache.org/repos/dist/dev/incubator/atlas/0.8-incubating-rc1/apache-atlas-0.8-incubating-sources.tar.gz.asc
>
>   MD5 Hash:   
> https://dist.apache.org/repos/dist/dev/incubator/atlas/0.8-incubating-rc1/apache-atlas-0.8-incubating-sources.tar.gz.md5
>
>
>
> Keys to verify the signature of the release artifacts are available at: 
> https://dist.apache.org/repos/dist/dev/incubator/atlas/KEYS
>
>
>
>
>
>
>
>
>

Re: Atlas incubator report

[Hemanth Yamijala]

All,

I have added the contents of the report to 
https://wiki.apache.org/incubator/March2017

Thanks
Hemanth

From: Hemanth Yamijala <yhema...@gmail.com>
Sent: Monday, March 06, 2017 10:55 AM
To: dev@atlas.incubator.apache.org
Subject: Re: Atlas incubator report

Hi Madhan,

I verified your links and they look fine to me. Will use them in the
Incubator Wiki.

Thanks for the review.

Hemanth

On Mon, Mar 6, 2017 at 10:22 AM, Madhan Neethiraj <mad...@apache.org> wrote:
> Hemanth,
>
> Thanks for compiling the report. Can you please review the links [4] and [5]? 
> They open JIRAs ATLAS-1600 and ATLAS-1599 respectively. Perhaps you meant the 
> following URLs?
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202016-12-01%20AND%20created%20%3C%3D%202017-02-28
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20resolved%20%3E%3D%202016-12-01%20AND%20resolved%20%3C%3D%202017-02-28
>
> Rest of the contents look good.
>
> +1 from me.
>
> Thanks,
> Madhan
>
>
> On 3/5/17, 7:17 AM, "Hemanth Yamijala" <yhema...@gmail.com> wrote:
>
> Hi,
>
> There was a typo in the last email (reported 1508 issues as resolved
> instead of 158. This is fixed now.) Apologies for so many emails.
>
> ==
> Atlas
> Apache Atlas is a scalable and extensible set of core foundational
> governance services that enables enterprises to effectively and
> efficiently meet their compliance requirements within Hadoop and
> allows integration with the complete enterprise data ecosystem.
>
> Atlas has been incubating since 2015-05-05.
>
> Three most important issues to address in the move towards graduation:
> 1. Podling name search is pending. PODLINGNAMESEARCH-118 [1] was
> opened to track this.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be 
> aware of?
> No specific issues at this time to report.
>
> How has the community developed since the last report?
> 1. No new committers or PPMC additions since last time. About 4 new
> contributors have been added since the last report. The current number
> of contributors is around 74.
>
> 2. The activity on the atlas-dev mailing list stands at an average of
> around 800 messages per month between December and February [2]
>
> How has the project developed since the last report?
> 1. 0.7.1 (incubating) release of Apache Atlas was made on 30th January
> 2017 [3]. In addition, a 0.8 release is being planned and community is
> focussed on this.
>
> 2. New features such as an improved API layer, more performance
> improvements, UI enhancements to create new entities etc are being
> planned in the 0.8 release. In addition, there are proposals to bring
> a new Business Glossary feature.
>
> 3. A total of 253 issues were reported between Dec 1st 2016 and Feb
> 28th 2017. 158 issues have been resolved in the same time [4][5]
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>   [ ] Initial setup
>   [ ] Working towards first release
>   [ ] Community building
>   [X] Nearing graduation
>   [ ] Other:
>
>
> Date of last release:
> 2017-01-30: 0.7.1-incubating [3]
>
> When were the last committers or PMC members elected?
> 1. The PPMC voted and elected 3 new members as committers to the
> project on 2016-10-20: Madhan Neethiraj, Jeffrey Hagelberg and Vimal
> Sharma.
>
> Links
> [1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-118
>
> [2] 
> http://markmail.org/search/?q=atlas#query:atlas%20list%3Aorg.apache.atlas.dev+page:1+state:facets
>
> [3] 
> https://lists.apache.org/thread.html/a63701573703d464c963e1cad9b93c0038c1826f841982b50d08c515@%3Cdev.atlas.apache.org%3E
>
> [4] 
> https://issues.apache.org/jira/browse/ATLAS-1600?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202016-12-01%20AND%20created%20%3C%3D%202017-02-28
>
> [5] 
> https://issues.apache.org/jira/browse/ATLAS-1599?jql=project%20%3D%20ATLAS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20resolved%20%3E%3D%202016-12-01%20AND%20resolved%20%3C%3D%202017-02-28
> ==
>
>
> On Sun, Mar 5, 2017 at 8:45 PM, Hemanth Yamijala <yhema...@gmail.com> 
> wrote:
> > Thanks, John, for pointing out about the change in format.
> >
> > Atlas community, please find the modified report. The main diff I see
> > is in the additional question "How

Re: Atlas incubator report

[Hemanth Yamijala]

Hi Madhan,

I verified your links and they look fine to me. Will use them in the
Incubator Wiki.

Thanks for the review.

Hemanth

On Mon, Mar 6, 2017 at 10:22 AM, Madhan Neethiraj <mad...@apache.org> wrote:
> Hemanth,
>
> Thanks for compiling the report. Can you please review the links [4] and [5]? 
> They open JIRAs ATLAS-1600 and ATLAS-1599 respectively. Perhaps you meant the 
> following URLs?
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202016-12-01%20AND%20created%20%3C%3D%202017-02-28
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20resolved%20%3E%3D%202016-12-01%20AND%20resolved%20%3C%3D%202017-02-28
>
> Rest of the contents look good.
>
> +1 from me.
>
> Thanks,
> Madhan
>
>
> On 3/5/17, 7:17 AM, "Hemanth Yamijala" <yhema...@gmail.com> wrote:
>
> Hi,
>
> There was a typo in the last email (reported 1508 issues as resolved
> instead of 158. This is fixed now.) Apologies for so many emails.
>
> ==
> Atlas
> Apache Atlas is a scalable and extensible set of core foundational
> governance services that enables enterprises to effectively and
> efficiently meet their compliance requirements within Hadoop and
> allows integration with the complete enterprise data ecosystem.
>
> Atlas has been incubating since 2015-05-05.
>
> Three most important issues to address in the move towards graduation:
> 1. Podling name search is pending. PODLINGNAMESEARCH-118 [1] was
> opened to track this.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be 
> aware of?
> No specific issues at this time to report.
>
> How has the community developed since the last report?
> 1. No new committers or PPMC additions since last time. About 4 new
> contributors have been added since the last report. The current number
> of contributors is around 74.
>
> 2. The activity on the atlas-dev mailing list stands at an average of
> around 800 messages per month between December and February [2]
>
> How has the project developed since the last report?
> 1. 0.7.1 (incubating) release of Apache Atlas was made on 30th January
> 2017 [3]. In addition, a 0.8 release is being planned and community is
> focussed on this.
>
> 2. New features such as an improved API layer, more performance
> improvements, UI enhancements to create new entities etc are being
> planned in the 0.8 release. In addition, there are proposals to bring
> a new Business Glossary feature.
>
> 3. A total of 253 issues were reported between Dec 1st 2016 and Feb
> 28th 2017. 158 issues have been resolved in the same time [4][5]
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>   [ ] Initial setup
>   [ ] Working towards first release
>   [ ] Community building
>   [X] Nearing graduation
>   [ ] Other:
>
>
> Date of last release:
> 2017-01-30: 0.7.1-incubating [3]
>
> When were the last committers or PMC members elected?
> 1. The PPMC voted and elected 3 new members as committers to the
> project on 2016-10-20: Madhan Neethiraj, Jeffrey Hagelberg and Vimal
> Sharma.
>
> Links
> [1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-118
>
> [2] 
> http://markmail.org/search/?q=atlas#query:atlas%20list%3Aorg.apache.atlas.dev+page:1+state:facets
>
> [3] 
> https://lists.apache.org/thread.html/a63701573703d464c963e1cad9b93c0038c1826f841982b50d08c515@%3Cdev.atlas.apache.org%3E
>
> [4] 
> https://issues.apache.org/jira/browse/ATLAS-1600?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202016-12-01%20AND%20created%20%3C%3D%202017-02-28
>
> [5] 
> https://issues.apache.org/jira/browse/ATLAS-1599?jql=project%20%3D%20ATLAS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20resolved%20%3E%3D%202016-12-01%20AND%20resolved%20%3C%3D%202017-02-28
> ==
>
>
> On Sun, Mar 5, 2017 at 8:45 PM, Hemanth Yamijala <yhema...@gmail.com> 
> wrote:
> > Thanks, John, for pointing out about the change in format.
> >
> > Atlas community, please find the modified report. The main diff I see
> > is in the additional question "How would you assess the podling's
> > maturity?"
> >
> > Thanks,
> > hemanth
> >
> > ===
> > Atlas
> > Apache Atlas is a scalable and extensible set of core foundational
> > governance services that enables ent

Re: Atlas incubator report

[Hemanth Yamijala]

Hi,

There was a typo in the last email (reported 1508 issues as resolved
instead of 158. This is fixed now.) Apologies for so many emails.

==
Atlas
Apache Atlas is a scalable and extensible set of core foundational
governance services that enables enterprises to effectively and
efficiently meet their compliance requirements within Hadoop and
allows integration with the complete enterprise data ecosystem.

Atlas has been incubating since 2015-05-05.

Three most important issues to address in the move towards graduation:
1. Podling name search is pending. PODLINGNAMESEARCH-118 [1] was
opened to track this.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No specific issues at this time to report.

How has the community developed since the last report?
1. No new committers or PPMC additions since last time. About 4 new
contributors have been added since the last report. The current number
of contributors is around 74.

2. The activity on the atlas-dev mailing list stands at an average of
around 800 messages per month between December and February [2]

How has the project developed since the last report?
1. 0.7.1 (incubating) release of Apache Atlas was made on 30th January
2017 [3]. In addition, a 0.8 release is being planned and community is
focussed on this.

2. New features such as an improved API layer, more performance
improvements, UI enhancements to create new entities etc are being
planned in the 0.8 release. In addition, there are proposals to bring
a new Business Glossary feature.

3. A total of 253 issues were reported between Dec 1st 2016 and Feb
28th 2017. 158 issues have been resolved in the same time [4][5]

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [X] Nearing graduation
  [ ] Other:


Date of last release:
2017-01-30: 0.7.1-incubating [3]

When were the last committers or PMC members elected?
1. The PPMC voted and elected 3 new members as committers to the
project on 2016-10-20: Madhan Neethiraj, Jeffrey Hagelberg and Vimal
Sharma.

Links
[1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-118

[2] 
http://markmail.org/search/?q=atlas#query:atlas%20list%3Aorg.apache.atlas.dev+page:1+state:facets

[3] 
https://lists.apache.org/thread.html/a63701573703d464c963e1cad9b93c0038c1826f841982b50d08c515@%3Cdev.atlas.apache.org%3E

[4] 
https://issues.apache.org/jira/browse/ATLAS-1600?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202016-12-01%20AND%20created%20%3C%3D%202017-02-28

[5] 
https://issues.apache.org/jira/browse/ATLAS-1599?jql=project%20%3D%20ATLAS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20resolved%20%3E%3D%202016-12-01%20AND%20resolved%20%3C%3D%202017-02-28
==


On Sun, Mar 5, 2017 at 8:45 PM, Hemanth Yamijala <yhema...@gmail.com> wrote:
> Thanks, John, for pointing out about the change in format.
>
> Atlas community, please find the modified report. The main diff I see
> is in the additional question "How would you assess the podling's
> maturity?"
>
> Thanks,
> hemanth
>
> ===
> Atlas
> Apache Atlas is a scalable and extensible set of core foundational
> governance services that enables enterprises to effectively and
> efficiently meet their compliance requirements within Hadoop and
> allows integration with the complete enterprise data ecosystem.
>
> Atlas has been incubating since 2015-05-05.
>
> Three most important issues to address in the move towards graduation:
> 1. Podling name search is pending. PODLINGNAMESEARCH-118 [1] was
> opened to track this.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware 
> of?
> No specific issues at this time to report.
>
> How has the community developed since the last report?
> 1. No new committers or PPMC additions since last time. About 4 new
> contributors have been added since the last report. The current number
> of contributors is around 74.
>
> 2. The activity on the atlas-dev mailing list stands at an average of
> around 800 messages per month between December and February [2]
>
> How has the project developed since the last report?
> 1. 0.7.1 (incubating) release of Apache Atlas was made on 30th January
> 2017 [3]. In addition, a 0.8 release is being planned and community is
> focussed on this.
>
> 2. New features such as an improved API layer, more performance
> improvements, UI enhancements to create new entities etc are being
> planned in the 0.8 release. In addition, there are proposals to bring
> a new Business Glossary feature.
>
> 3. A total of 253 issues were reported between Dec 1st 2016 and Feb
> 28th 2017. 1508issues have been resolved in the same time [4][5]
>
> How would you assess the podling's maturity?
> Please feel free to add your ow

Re: Atlas incubator report

[Hemanth Yamijala]

Thanks, John, for pointing out about the change in format.

Atlas community, please find the modified report. The main diff I see
is in the additional question "How would you assess the podling's
maturity?"

Thanks,
hemanth

===
Atlas
Apache Atlas is a scalable and extensible set of core foundational
governance services that enables enterprises to effectively and
efficiently meet their compliance requirements within Hadoop and
allows integration with the complete enterprise data ecosystem.

Atlas has been incubating since 2015-05-05.

Three most important issues to address in the move towards graduation:
1. Podling name search is pending. PODLINGNAMESEARCH-118 [1] was
opened to track this.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No specific issues at this time to report.

How has the community developed since the last report?
1. No new committers or PPMC additions since last time. About 4 new
contributors have been added since the last report. The current number
of contributors is around 74.

2. The activity on the atlas-dev mailing list stands at an average of
around 800 messages per month between December and February [2]

How has the project developed since the last report?
1. 0.7.1 (incubating) release of Apache Atlas was made on 30th January
2017 [3]. In addition, a 0.8 release is being planned and community is
focussed on this.

2. New features such as an improved API layer, more performance
improvements, UI enhancements to create new entities etc are being
planned in the 0.8 release. In addition, there are proposals to bring
a new Business Glossary feature.

3. A total of 253 issues were reported between Dec 1st 2016 and Feb
28th 2017. 1508issues have been resolved in the same time [4][5]

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [X] Nearing graduation
  [ ] Other:


Date of last release:
2017-01-30: 0.7.1-incubating [3]

When were the last committers or PMC members elected?
1. The PPMC voted and elected 3 new members as committers to the
project on 2016-10-20: Madhan Neethiraj, Jeffrey Hagelberg and Vimal
Sharma.

Links
[1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-118

[2] 
http://markmail.org/search/?q=atlas#query:atlas%20list%3Aorg.apache.atlas.dev+page:1+state:facets

[3] 
https://lists.apache.org/thread.html/a63701573703d464c963e1cad9b93c0038c1826f841982b50d08c515@%3Cdev.atlas.apache.org%3E

[4] 
https://issues.apache.org/jira/browse/ATLAS-1600?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202016-12-01%20AND%20created%20%3C%3D%202017-02-28

[5] 
https://issues.apache.org/jira/browse/ATLAS-1599?jql=project%20%3D%20ATLAS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20resolved%20%3E%3D%202016-12-01%20AND%20resolved%20%3C%3D%202017-02-28




On Sun, Mar 5, 2017 at 7:19 PM, John D. Ament <johndam...@apache.org> wrote:
> Please don't forget that the format has changed:
>
> Atlas
>
> Apache Atlas is a scalable and extensible set of core foundational governance
> services that enables enterprises to effectively and efficiently meet their
> compliance requirements within Hadoop and allows integration with the complete
> enterprise data ecosystem
>
> Atlas has been incubating since 2015-05-05.
>
> Three most important issues to address in the move towards graduation:
>
>   1.
>   2.
>   3.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>
>
> How has the community developed since the last report?
>
>
>
> How has the project developed since the last report?
>
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>   [ ] Initial setup
>   [ ] Working towards first release
>   [ ] Community building
>   [ ] Nearing graduation
>   [ ] Other:
>
> Date of last release:
>
>   -XX-XX
>
> When were the last committers or PPMC members elected?
>
>
>
> Signed-off-by:
>
>   [ ](atlas) Arun Murthy
>  Comments:
>   [ ](atlas) Chris Douglas
>  Comments:
>   [ ](atlas) Jakob Homan
>  Comments:
>   [ ](atlas) Vinod Kumar Vavilapalli
>  Comments:
>
> IPMC/Shepherd notes:
>
>
> On 2017-03-05 00:39 (-0500), Hemanth Yamijala <yhema...@gmail.com> wrote:
>> Hi,
>>
>> We need to submit an incubator report and have missed the first
>> deadline for submission. Please review the text below and let me know
>> if there are any errors to be corrected. I will wait until Tuesday
>> morning 9 AM IST to hear back from folks.
>>
>> Thanks
>> Hemanth
>> 
>> Atlas
>> Apache Atlas is a scalable and extensible set of core foundational
>>

Re: Podling Report Reminder - March 2017

[Hemanth Yamijala]

Hi John,

Apologies for the delay. I've created a draft and sent it out for
review on the dev mailing list. Will give it until Monday evening PST
for any review comments and add to the wiki.

Thanks
Hemanth

On Sat, Mar 4, 2017 at 6:48 AM, John D. Ament  wrote:
> All,
>
> There's been no response to this.  Can someone look at creating a report?
>
> John
>
> On 2017-03-01 22:07 (-0500), johndam...@apache.org wrote:
>> 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 March 2017, 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, March 01).
>>
>> 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.
>> *   How does the podling rate their own maturity.
>>
>> This should be appended to the Incubator Wiki page at:
>>
>> https://wiki.apache.org/incubator/March2017
>>
>> 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
>>

Atlas incubator report

[Hemanth Yamijala]

Hi,

We need to submit an incubator report and have missed the first
deadline for submission. Please review the text below and let me know
if there are any errors to be corrected. I will wait until Tuesday
morning 9 AM IST to hear back from folks.

Thanks
Hemanth

Atlas
Apache Atlas is a scalable and extensible set of core foundational
governance services that enables enterprises to effectively and
efficiently meet their compliance requirements within Hadoop and
allows integration with the complete enterprise data ecosystem.

Atlas has been incubating since 2015-05-05.

Three most important issues to address in the move towards graduation:
1. Podling name search is pending. PODLINGNAMESEARCH-118 [1] was
opened to track this.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No specific issues at this time to report.

How has the community developed since the last report?
1. No new committers or PPMC additions since last time. About 4 new
contributors have been added since the last report. The current number
of contributors is around 74.

2. The activity on the atlas-dev mailing list stands at an average of
around 800 messages per month between December and February [2]

How has the project developed since the last report?
1. 0.7.1 (incubating) release of Apache Atlas was made on 30th January
2017 [3]. In addition, a 0.8 release is being planned and community is
focussed on this.

2. New features such as an improved API layer, more performance
improvements, UI enhancements to create new entities etc are being
planned in the 0.8 release. In addition, there are proposals to bring
a new Business Glossary feature.

3. A total of 253 issues were reported between Dec 1st 2016 and Feb
28th 2017. 158 issues have been resolved in the same time [4][5]

Date of last release:
2017-01-30: 0.7.1-incubating [3]

When were the last committers or PMC members elected?
1. The PPMC voted and elected 3 new members as committers to the
project on 2016-10-20: Madhan Neethiraj, Jeffrey Hagelberg and Vimal
Sharma.

Links
[1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-118

[2] 
http://markmail.org/search/?q=atlas#query:atlas%20list%3Aorg.apache.atlas.dev+page:1+state:facets

[3] 
https://lists.apache.org/thread.html/a63701573703d464c963e1cad9b93c0038c1826f841982b50d08c515@%3Cdev.atlas.apache.org%3E

[4] 
https://issues.apache.org/jira/browse/ATLAS-1600?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202016-12-01%20AND%20created%20%3C%3D%202017-02-28

[5] 
https://issues.apache.org/jira/browse/ATLAS-1599?jql=project%20%3D%20ATLAS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20resolved%20%3E%3D%202016-12-01%20AND%20resolved%20%3C%3D%202017-02-28

Re: .7.1 rc3 - change in requirements at Run Time ?

[Hemanth Yamijala]

Hi Russell,


I am unable to see the exact error that you are facing - in case you attached 
an image or message.


AFAIK, there is no change in requirement for 0.7.1 from 0.7.0. Specifically, 
BerkeleyDB jars are not bundled with Atlas due to Apache licensing 
restrictions. The default profile (when we build with -Pdist) expects a setup 
of external HBase and Solr, which is the preferred deployment mode. If you need 
to build with BerkeleyDB and ElasticSearch, you should use a specific profile 
and also manually get the dependent jars copied to the deployment. This is 
documented in the 0.7 documentation here: 
http://atlas.incubator.apache.org/0.7.0-incubating/InstallationSteps.html?. 
Please lookup for the profile "berkeley-elasticsearch" and let us know if that 
gives you information required.


Thanks

Hemanth


From: Russell Anderson 
Sent: Tuesday, January 24, 2017 6:48 AM
To: dev@atlas.incubator.apache.org
Cc: Apoorv Naik; Madhan Neethiraj; Ashutosh Mestry; Sarath Subramanian; David 
Radley; Vimal Sharma; Russell Anderson; Barry Rosen
Subject: .7.1 rc3 - change in requirements at Run Time ?


[cid:1__=8FBB0A21DF9506DF8f9e8a93df938690918c8FB@]

Can someone please tell me if there is a new run time required library for 
Atlas .7.1 rc3 versus .7.0 rc2 ?

Atlas will not start up without this class - this appears to be a specific 
Berkeley DB java class. What version of the JDK is required ?

Regards,

Russ.


[Inactive hide details for Sarath Subramanian ---01/23/2017 07:56:19 
PM-]Sarath Subramanian 
---01/23/2017 07:56:19 
PM-- This is an 
automatically generated e-mai

From: Sarath Subramanian 
To: Apoorv Naik , Madhan Neethiraj , 
Ashutosh Mestry 
Cc: Sarath Subramanian , atlas 
, David Radley , Vimal 
Sharma 
Date: 01/23/2017 07:56 PM
Subject: Re: Review Request 55358: [ATLAS-1312] Update QuickStart to use the 
new APIs for type and entities creation
Sent by: Sarath Subramanian 






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

(Updated Jan. 23, 2017, 4:55 p.m.)


Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, and 
Suma Shivaprasad.


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


Repository: atlas


Description
---

The quick start currently uses old APIs to create types and entities. This 
needs to be updated to use the v2 APIs for types and entities.


Diffs (updated)
-

 client/src/main/java/org/apache/atlas/AtlasBaseClient.java d055b78
 client/src/main/java/org/apache/atlas/AtlasLineageClientV2.java PRE-CREATION
 distro/src/bin/quick_start.py 14c8464
 distro/src/bin/quick_start_v1.py PRE-CREATION
 intg/src/main/java/org/apache/atlas/type/AtlasTypeUtil.java c866946
 webapp/src/main/java/org/apache/atlas/examples/QuickStart.java 8322bc6
 webapp/src/main/java/org/apache/atlas/examples/QuickStartV2.java PRE-CREATION
 webapp/src/test/java/org/apache/atlas/examples/QuickStartV2IT.java PRE-CREATION
 webapp/src/test/java/org/apache/atlas/web/resources/BaseResourceIT.java 51be64c

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


Testing
---

Tested using POstman REST Client and new ITs added


Thanks,

Sarath Subramanian

Re: [VOTE] Release Apache Atlas 0.7.1 (incubating) - release candidate 3 (dev group vote)

[Hemanth Yamijala]

Repeated these tests from last RC check:

* SHA / MD5 checksums fine
* Tag exists and looks OK
* No binaries in source
* Built fine (minus tests)
* Single node instance with HBase and Solr came up
* Quickstart ran fine and UI looks good.

+1 (binding).

Thanks
Hemanth

From: Madhan Neethiraj <mad...@apache.org>
Sent: Thursday, January 19, 2017 10:15 PM
To: dev@atlas.incubator.apache.org
Subject: [VOTE] Release Apache Atlas 0.7.1 (incubating) - release candidate 3 
(dev group vote)

Atlas team,



Apache Atlas 0.7.1 (incubating) release candidate #3 is now available for a 
vote within dev community. Links to the release artifacts are given below. Can 
you please review and vote?



I apologize for yet another release-candidate. Only change in “release 
candidate 3” is the update to build instructions in README.txt. There are no 
other changes.



We currently have 7 binding votes and 7 non-binding votes for the earlier 
release candidates. Thank you everyone for validating the release candidates, 
your feedback and vote.

  +1 (binding):  7 votes

 - Shwetha Shivalingamurthy

 - Venkat Ranganathan

 - Keval Bhatt

 - Vimal Sharma

 - Suma Shivaprasad

 - Hemanth Yamijala

 - Madhan Neethiraj



  +1 (non-binding): 7 votes

 - David Radley

 - Sarath Kumar Subramanian

 - Ismaël Mejía

 - Jean-Baptiste Onofré

 - Ayub Khan Pathan

 - Nixon Rodrigues

 - Apoorv Naik





Changes since last release-candidate:

  - updated the build instructions in README.txt (ATLAS-1000)



The vote will be open for at least 72 hours or until necessary votes are 
reached.

[ ] +1  approve

[ ] +0  no opinion

[ ] -1  disapprove (and reason why)



Thanks,

Madhan





List of issues addressed in this release: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20Atlas%20AND%20fixVersion%20%3D%200.7.1-incubating%20ORDER%20BY%20key%20DESC



Git tag for the release: 
https://github.com/apache/incubator-atlas/tree/release-0.7.1-rc3



Sources for the release: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc3/apache-atlas-0.7.1-incubating-sources.tar.gz



Source release verification:

  PGP Signature: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc3/apache-atlas-0.7.1-incubating-sources.tar.gz.asc

  MD5 Hash: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc3/apache-atlas-0.7.1-incubating-sources.tar.gz.mds

  Keys to verify the signature of the release artifacts are available at: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/KEYS

Re: [VOTE] Release Apache Atlas 0.7.1 (incubating) - release candidate 2 (dev group vote)

[Hemanth Yamijala]

Hi folks,

My 2 cents.

IMHO, the git clone step in the README is a bit of a red herring. 
For most cases, the fact that someone is reading the README already means that 
they have gotten a version of Atlas to build. How or why did they choose that 
specific version.. depends - maybe  cloning the repo, or from the release email 
(http://markmail.org/thread/gljgiumhggixcoyq), or by visiting the release links 
on http://atlas.incubator.apache.org/ and so on.. 

So removing the git clone step from the README is as good as fix as any. 

I agree the version could be more prominently documented. But for situations 
where the source code was already obtained deliberately selecting a version - 
it may not be that critical an issue?

Thanks
hemanth

From: David Radley 
Sent: Thursday, January 19, 2017 2:54 PM
To: dev@atlas.incubator.apache.org
Subject: Re: [VOTE] Release Apache Atlas 0.7.1 (incubating) - release candidate 
2 (dev group vote)

Hi Madhan,
Sorry - that was my mistake on the clone command. I think we could defer
some of my other suggestions to a later release. I feel the points below
are important as they have the potential to cause confusion.

I think it is confusing that we say
for 0.8 use:
git clone https://git-wip-us.apache.org/repos/asf/incubator-atlas.git
atlas
for 0.7.1
git clone https://github.com/apache/incubator-atlas.git

Ideally we should have a consistent git url naming convention, I think the
minimum is that we should include 0.7.1 or 7 somewhere in the new git url.
At the moment the 0.7.1 git url could easily be mistaken for the latest
code.

I cloned the source and see that the README now does not contain the clone
instructions. I looked in the documentation for the installation
instructions and see that the it clone specified is for 0.8.
I think we should document the correct git clone syntax for 0.7.1
somewhere.

Maybe I am missing something, but I cannot see the version number 0.7.1
mentioned anywhere (I see 0.7.1 mentioned in files under .git folder and
0.7 mentioned in Jira  in the release notes) . So I am unsure how I could
know what version of Atlas I am on; from the source tree or a built Atlas.


Here is my +1, if we can create a more representative git url and document
it somewhere and have a way of finding out what release we are.

Thanks David.



From:   Madhan Neethiraj 
To: "dev@atlas.incubator.apache.org" 
Date:   18/01/2017 16:37
Subject:Re: [VOTE] Release Apache Atlas 0.7.1 (incubating) -
release candidate 2 (dev group vote)
Sent by:Madhan Neethiraj 



David,

Thanks for validating the release candidate and your comments.
Please see my response below:

>> "git clone https://github.com/apache/incubator-atlas.git;
>> This is the wrong git command - as this will put the code into git –
not
>>  clone it from the repository into a local folder.
This command gets the repository to local folder “incubator-atlas”, which
Is consistent with the following build instructions in the README.

>> 2) I think that the readme should explicitly mention the version
number
>>0.7.1 and also point to the latest code 0.8 and explicitly talk
about the
>>need for 0.7.1, rather than using 0.8, which I assume is primarily
the
>>java level. I think all the urls should default to the latest code
(0.8).
>>
>>3) I suggest that the readme includes the versions of any libraries
that
>>need to be on a machine to be able to build. I would mention the
required
>>levels of Java, Maven, Git and Python. I have not installed as I was
not
>>sure of the levels I need of these prereqs.

Can these be addressed this in the next release? One approach would be to
create multiple READM.txt, one for each release. Another approach would
be to create multiple sections in README.txt - one for each release.

Thanks,
Madhan


On 1/18/17, 3:18 AM, "David Radley"  wrote:

Atlas team,
I am not sure if the resdme updates have gone in; from the link below
the
readme seems not to be correct.


I have downloaded the tar.gz file.


Readme feedback
1) I notice the readme starts by saying to get the code using "git
clone
https://github.com/apache/incubator-atlas.git;
This is the wrong git command - as this will put the code into git -
not
clone it from the repository into a local folder.

I look on http://atlas.incubator.apache.org/InstallationSteps.html. It

says to use "git clone
https://git-wip-us.apache.org/repos/asf/incubator-atlas.git atlas"
We need to document a 0.7.1 equivalent for the clone in the readme.

2) I think that the readme should explicitly mention the version
number
0.7.1 and also point to the latest code 0.8 and explicitly talk about
the
need for 0.7.1, rather than using 0.8, which I assume is primarily the

java level. I 

JanusGraph - fork of Titan?

[Hemanth Yamijala]

Found this from an announcement today on the Titan mailing list:


http://janusgraph.org/

Re: [VOTE] Release Apache Atlas 0.7.1 (incubating) - release candidate 2 (dev group vote)

[Hemanth Yamijala]

Hi,

* SHA / MD5 checksums fine
* Tag exists and looks OK
* No binaries in source
* Built fine (minus the minor test failures)
* Single node instance with HBase and Solr came up
* Quickstart ran fine and UI looks good.
* License of 3rd party CSS, JS look OK from what I can see

+1 (binding) from my end, based on the above verification.

Thanks
hemanth

From: Madhan Neethiraj 
Sent: Wednesday, January 18, 2017 1:51 PM
To: dev@atlas.incubator.apache.org
Subject: [VOTE] Release Apache Atlas 0.7.1 (incubating) - release candidate 2 
(dev group vote)

Atlas team,

Apache Atlas 0.7.1 (incubating) release candidate #2 is now available for a 
vote within dev community. This update addresses the issues reported by Hemanth 
and Shwetha (thanks!).

Changes since last release-candidate:
- updated README.txt with build instructions (ATLAS-1000)

Links to the release artifacts are given below. Can you please review and vote?

The vote will be open for at least 72 hours or until necessary votes are 
reached.
[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Here is my +1

Thanks,
Madhan


List of issues addressed in this release: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20Atlas%20AND%20fixVersion%20%3D%200.7.1-incubating%20ORDER%20BY%20key%20DESC

Git tag for the release: 
https://github.com/apache/incubator-atlas/tree/release-0.7.1-rc2

Sources for the release: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc2/apache-atlas-0.7.1-incubating-sources.tar.gz

Source release verification:
  PGP Signature: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc2/apache-atlas-0.7.1-incubating-sources.tar.gz.asc
  MD5 Hash: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc2/apache-atlas-0.7.1-incubating-sources.tar.gz.mds

  Keys to verify the signature of the release artifacts are available at: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/KEYS

Re: [VOTE] Release Apache Atlas 0.7.1 (incubating) - release candidate 1 (dev group vote)

[Hemanth Yamijala]

Thanks Madhan for looking into the README fix. Appreciate your patience with 
seeing this through.

I understand fixing the tests is a continuous affair. I am fine covering these 
later, especially, as I can see the base functionality is fine.

Thanks
Hemanth

From: Madhan Neethiraj <mneethi...@hortonworks.com> on behalf of Madhan 
Neethiraj <mad...@apache.org>
Sent: Wednesday, January 18, 2017 12:37 PM
To: dev@atlas.incubator.apache.org
Subject: Re: [VOTE] Release Apache Atlas 0.7.1 (incubating) - release candidate 
1 (dev group vote)

Hemanth,

I will add build instructions in README.txt and create another release 
candidate shortly. You are right about inconsistent test failures due to timing 
issues; community is looking into fixing these tests and these will be 
addressed in subsequent releases.

Thanks,
Madhan



On 1/17/17, 10:21 PM, "Hemanth Yamijala" <hyamij...@hortonworks.com> wrote:

Madhan,

I verified the following:

* SHA/MD5 checksums
* incubating in release name
* no binaries in release
* 3rd party licenses for the JS / CSS files I could identify
* build from source - a few minor points which I have pointed below. Build 
compile and package passed fine.
* single node Atlas instance with HBase and Solr - came up fine.
* Ran quickstart, browsed the UI - looks fine.

Couple of minor issues:

* The following tests failed: 
EntityJerseyResourceIT.testDeleteExistentTraitNonExistentForEntity, 
HiveHookIT.testCreateExternalTable, HiveHookIT.testInsertIntoTempTable. I know 
the community is working on some timing oriented test failures, and this seems 
a continuous effort. Given the basic functionality is fine, I think these are 
red herrings and will ignore them. Rest of the build was fine (including tests)

* For the 0.7.0 release, there was feedback from IPMC to make the build 
instructions more explicit in the README itself, as opposed to having them only 
the website. We had filed ATLAS-1000 for this. Although this JIRA is marked for 
0.8 release, since we are doing this anyway - maybe better to address it now. 
(Apologies for not pointing it out earlier - slipped my mind).

Please let me know if you think ATLAS-1000 is worth covering now.

Thanks
Hemanth

From: Madhan Neethiraj <mad...@apache.org>
Sent: Tuesday, January 17, 2017 11:57 PM
To: dev@atlas.incubator.apache.org
Subject: [VOTE] Release Apache Atlas 0.7.1 (incubating) - release candidate 
1 (dev group vote)

Atlas team,



Apache Atlas 0.7.1 (incubating) release candidate #1 is now available for a 
vote within dev community.



Changes since last release-candidate:

-  files/directories that were inadvertently included in the last 
release candidate were removed. Thanks Hemanth for finding this issue



Links to the release artifacts are given below. Can you please review and 
vote?



The vote will be open for at least 72 hours or until necessary votes are 
reached.

 [ ] +1  approve

 [ ] +0  no opinion

 [ ] -1  disapprove (and reason why)



Here is my +1



Thanks,

Madhan





List of issues addressed in this release: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20Atlas%20AND%20fixVersion%20%3D%200.7.1-incubating%20ORDER%20BY%20key%20DESC



Git tag for the release: 
https://github.com/apache/incubator-atlas/tree/release-0.7.1-rc1



Sources for the release: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc1/apache-atlas-0.7.1-incubating-sources.tar.gz



Source release verification:

  PGP Signature: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc1/apache-atlas-0.7.1-incubating-sources.tar.gz.asc

  MD5 Hash: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc1/apache-atlas-0.7.1-incubating-sources.tar.gz.mds



  Keys to verify the signature of the release artifacts are available 
at: https://dist.apache.org/repos/dist/dev/incubator/atlas/KEYS

Re: [VOTE] Release Apache Atlas 0.7.1 (incubating) - release candidate 1 (dev group vote)

[Hemanth Yamijala]

Madhan,

I verified the following:

* SHA/MD5 checksums 
* incubating in release name
* no binaries in release
* 3rd party licenses for the JS / CSS files I could identify
* build from source - a few minor points which I have pointed below. Build 
compile and package passed fine.
* single node Atlas instance with HBase and Solr - came up fine.
* Ran quickstart, browsed the UI - looks fine.

Couple of minor issues:

* The following tests failed: 
EntityJerseyResourceIT.testDeleteExistentTraitNonExistentForEntity, 
HiveHookIT.testCreateExternalTable, HiveHookIT.testInsertIntoTempTable. I know 
the community is working on some timing oriented test failures, and this seems 
a continuous effort. Given the basic functionality is fine, I think these are 
red herrings and will ignore them. Rest of the build was fine (including tests)

* For the 0.7.0 release, there was feedback from IPMC to make the build 
instructions more explicit in the README itself, as opposed to having them only 
the website. We had filed ATLAS-1000 for this. Although this JIRA is marked for 
0.8 release, since we are doing this anyway - maybe better to address it now. 
(Apologies for not pointing it out earlier - slipped my mind).

Please let me know if you think ATLAS-1000 is worth covering now.

Thanks
Hemanth

From: Madhan Neethiraj 
Sent: Tuesday, January 17, 2017 11:57 PM
To: dev@atlas.incubator.apache.org
Subject: [VOTE] Release Apache Atlas 0.7.1 (incubating) - release candidate 1 
(dev group vote)

Atlas team,



Apache Atlas 0.7.1 (incubating) release candidate #1 is now available for a 
vote within dev community.



Changes since last release-candidate:

-  files/directories that were inadvertently included in the last 
release candidate were removed. Thanks Hemanth for finding this issue



Links to the release artifacts are given below. Can you please review and vote?



The vote will be open for at least 72 hours or until necessary votes are 
reached.

 [ ] +1  approve

 [ ] +0  no opinion

 [ ] -1  disapprove (and reason why)



Here is my +1



Thanks,

Madhan





List of issues addressed in this release: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20Atlas%20AND%20fixVersion%20%3D%200.7.1-incubating%20ORDER%20BY%20key%20DESC



Git tag for the release: 
https://github.com/apache/incubator-atlas/tree/release-0.7.1-rc1



Sources for the release: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc1/apache-atlas-0.7.1-incubating-sources.tar.gz



Source release verification:

  PGP Signature: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc1/apache-atlas-0.7.1-incubating-sources.tar.gz.asc

  MD5 Hash: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc1/apache-atlas-0.7.1-incubating-sources.tar.gz.mds



  Keys to verify the signature of the release artifacts are available at: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/KEYS

Re: [VOTE] Release Apache Atlas 0.7.1 (incubating) - release candidate 0 (dev group vote)

[Hemanth Yamijala]

Hello Madhan,

Thank you for putting out the release.

I started to look at it, but soon found that we seem to have included some 
binaries in the source package at graphdb/titan0/target, 
shaded/hbase-server-shaded/target, shaded/hbase-client-shaded/target - which is 
accounting for a large portion of the size of the source package. The size is 
161 MB, which seems unusual for a source package.

Assuming this is a source only release (which is what we have normally done) - 
these probably are all to be removed, and just remnants of an earlier build?

Also, I did see some files that seemed extraneous, such as:

* apache-atlas-0.7.1-incubating/webapp/test-output/
* apache-atlas-0.7.1-incubating/.idea

and so on.

Thanks
Hemanth

From: Madhan Neethiraj 
Sent: Tuesday, January 17, 2017 2:09 AM
To: dev@atlas.incubator.apache.org
Subject: [VOTE] Release Apache Atlas 0.7.1 (incubating) - release candidate 0 
(dev group vote)

Atlas team,

Apache Atlas 0.7.1 (incubating) release candidate #0 is now available for a 
vote within dev community. Links to the release artifacts are given below. Can 
you please review and vote?

The vote will be open for at least 72 hours or until necessary votes are 
reached.
[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Here is my +1

Thanks,
Madhan


List of issues addressed in this release: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20Atlas%20AND%20fixVersion%20%3D%200.7.1-incubating%20ORDER%20BY%20key%20DESC

Git tag for the release: 
https://github.com/apache/incubator-atlas/tree/release-0.7.1-rc0

Sources for the release: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc0/apache-atlas-0.7.1-incubating-sources.tar.gz

Source release verification:
  PGP Signature: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc0/apache-atlas-0.7.1-incubating-sources.tar.gz.asc
  MD5 Hash: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc0/apache-atlas-0.7.1-incubating-sources.tar.gz.mds

Keys to verify the signature of the release artifacts are available at: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/KEYS

Re: Hook for Non Supported Data stores

[Hemanth Yamijala]

Hi,

It is possible to write Hooks for new data stores, as long as there is a 
mechanism in the data store (in your case, Impala) to invoke a class / method 
when there is a change to metadata. For all hooks that currently exist (Hive, 
Storm, Falcon, Sqoop) we have leveraged such plugin mechanisms exposed by the 
hosting systems.

I am not familiar with Impala to answer if such a plugin mechanism exists. 
Perhaps you could check with the Impala integration APIs and see. If not, there 
are other alternatives we can discuss on how you can integrate with Atlas, 
still.

Thanks
hemanth

From: Karthik K 
Sent: Tuesday, January 03, 2017 3:45 PM
To: dev@atlas.incubator.apache.org
Subject: Hook for Non Supported Data stores

Team,

Is there we could write or extend Hook for non supported data store like
Impala.

Hive, HDFS, Kafka, Storm are supported now but would like to know if i have
Impala table and will it be possible to create hook for the same.

Thanks & Regards,
K.Karthikeyan

[jira] [Commented] (ATLAS-1416) UI: It would be nice to sort the properties in the details page of an entity by name

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-1416:
-

[~davidrad], I was thinking of the sort functionality in the UI. I was however 
imagining they would be pre-sorted, but maybe having an explicit sort would 
work too. To be clear, the JIRA is only about the UX, and nothing to do with 
the API.

> UI: It would be nice to sort the properties in the details page of an entity 
> by name
> 
>
> Key: ATLAS-1416
> URL: https://issues.apache.org/jira/browse/ATLAS-1416
> Project: Atlas
>  Issue Type: Improvement
>    Reporter: Hemanth Yamijala
>
> The Atlas UI has a Details page for every entity. In the "Properties" tab of 
> this pane, it currently enumerates all properties of the entity. Currently 
> the order seems random and hence is not very easy to grok. It would be nice 
> to have these sorted by property name to make location of required details 
> easier.



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

Re: searching for entities with tags by name

[Hemanth Yamijala]

Hi,

I suspect the tag you searched for is a business term under a taxonomy, and not 
a regular tag. If yes, this behavior can be explained.

It is a by-product of how business terms are implemented today. AFAIK, they are 
implemented as traits. For regular traits (or tags), new instances are created 
whenever they are associated with an entity. However, terms are 'singleton' 
traits, i.e only one instance is created and this is looked up and associated 
with entities whenever the term association happens. The singleton instance is 
attached to the 'Taxonomy' instance by the Business Taxonomy implementation as 
a way of easily looking it up when required for association.

The side effect of this, is that when we search for a business term - because 
it is a tag, the search API gets both objects (the actual association and the 
implicit Taxonomy object association) in the results.

You must not see this behavior for regular tags.

Thanks
Hemanth

From: Avi Levi 
Sent: Wednesday, December 28, 2016 5:45 PM
To: dev@atlas.incubator.apache.org
Subject: searching for entities with tags by name

Hi

According to the documentation, searching for entities that are
associated to tags is done using the search/dsl api:

http:/// api/atlas/
discovery/search/dsl?query= %60tag-name%60

in the documentation the response contains one instance in the
results, but when I execute the api call, I get two instances in the
results, one of them
is the actual entity that I've tagged, and the other one is an object
of type Taxonomy.

can anyone explain this behavior ?

thanks

Re: Hive Hook - what is missing ?

[Hemanth Yamijala]

Hi,

A few questions to help debug:

1) Are you using Hive CLI or Beeline? Best results would be to
configure these hooks with HiveServer2 and use Beeline.

2) Could you please check hive logs and look for AtlasHook related messages?

Thanks
Hemanth

On Mon, Dec 26, 2016 at 8:59 PM, Russell Anderson  wrote:
>
>
> Hi dev list,
>
> I have built the Atlas7rc2 - have working the Hive Import, the Dashboard,
> and generally things appear to be working as expected.
>
> However, I have followed the instruction below but cannot seem to get the
> Hive Hook to detect table hive creations to be added to the metadata /
> lineage.
>
> Can anyone suggest how to debug what could be missing regardless of
> following the instructions below ? Any and all help appreciated !!!
>
> Regards,
>
> Russ.
>
> =
>
> Hive Hook
>
>
> Hive supports listeners on hive command execution using hive hooks. This is
> used to add/update/remove entities in Atlas using the model defined in
> org.apache.atlas.hive.model.HiveDataModelGenerator. The hook submits the
> request to a thread pool executor to avoid blocking the command execution.
> The thread submits the entities as message to the notification server and
> atlas server reads these messages and registers the entities. Follow these
> instructions in your hive set-up to add hive hook for Atlas:
>   Set-up atlas hook in hive-site.xml of your hive configuration:
> 
>   hive.exec.post.hooks
>   org.apache.atlas.hive.hook.HiveHook
> 
>
>
> 
>   atlas.cluster.name
>   primary
> 
>
>
>   Add 'export HIVE_AUX_JARS_PATH=/hook/hive' in
>   hive-env.sh of your hive configuration
>   Copy /atlas-application.properties to the hive conf
>   directory.
>
>
> The following properties in /atlas-application.properties
> control the thread pool and notification details:
>   atlas.hook.hive.synchronous - boolean, true to run the hook
>   synchronously. default false. Recommended to be set to false to avoid
>   delays in hive query completion.
>   atlas.hook.hive.numRetries - number of retries for notification
>   failure. default 3
>   atlas.hook.hive.minThreads - core number of threads. default 5
>   atlas.hook.hive.maxThreads - maximum number of threads. default 5
>   atlas.hook.hive.keepAliveTime - keep alive time in msecs. default 10
>   atlas.hook.hive.queueSize - queue size for the threadpool. default
>   1

[jira] [Created] (ATLAS-1416) UI: It would be nice to sort the properties in the details page of an entity by name

[Hemanth Yamijala (JIRA)]

Hemanth Yamijala created ATLAS-1416:
---

 Summary: UI: It would be nice to sort the properties in the 
details page of an entity by name
 Key: ATLAS-1416
 URL: https://issues.apache.org/jira/browse/ATLAS-1416
 Project: Atlas
  Issue Type: Improvement
Reporter: Hemanth Yamijala


The Atlas UI has a Details page for every entity. In the "Properties" tab of 
this pane, it currently enumerates all properties of the entity. Currently the 
order seems random and hence is not very easy to grok. It would be nice to have 
these sorted by property name to make location of required details easier.



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

Re: [jira] [Updated] (ATLAS-1298) UI never finishes loading

[Hemanth Yamijala]

FWIW, I have found clearing the browser caches helps in this case -
assuming you have not tried this already.

On Wed, Dec 21, 2016 at 4:16 AM, Russell Anderson  wrote:

> Hi,
>
> I made the code changes identified in the work around from ATLAS-1298.patch
>
> However, I started with atlas7 rc2 as the code base.
>
> My build was run with 'mvn clean package -Pdist,berkeley-elasticsearch
> -DskipTests -DskipCheck=true'
>
> All completed successfully - however - the same behavior results -
> infinite circle - never ends
>
> The import-hive.sh works fine, and the REST API returns lineage and works
> as expected.
>
> Regards,
>
> Russ.
>
>
> [image: Inactive hide details for "Keval Bhatt (JIRA)" ---12/20/2016
> 12:38:40 AM--- [ https://issues.apache.org/jira/browse/ATLAS-1]"Keval
> Bhatt (JIRA)" ---12/20/2016 12:38:40 AM--- [ https://issues.apache.org/
> jira/browse/ATLAS-1298?page=com.atlassian.jira.plugin.system.issuet
>
> From: "Keval Bhatt (JIRA)" 
> To: dev@atlas.incubator.apache.org
> Date: 12/20/2016 12:38 AM
> Subject: [jira] [Updated] (ATLAS-1298) UI never finishes loading
> --
>
>
>
>
> [ https://issues.apache.org/jira/browse/ATLAS-1298?page=
> com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Keval Bhatt updated ATLAS-1298:
> ---
>Fix Version/s: 0.7.1-incubating
>
> > UI never finishes loading
> > -
> >
> > Key: ATLAS-1298
> > URL: https://issues.apache.org/jira/browse/ATLAS-1298
> > Project: Atlas
> >  Issue Type: Bug
> >Affects Versions: 0.7-incubating
> > Environment: Atlas 0.7 - Profile Berkeley/ElasticSearch
> >Reporter: PJ Van Aeken
> >Assignee: Keval Bhatt
> > Fix For: 0.7.1-incubating
> >
> > Attachments: ATLAS-1298.patch, graycol.gif
> >
> >
> > The REST API  works fine, and I can see the data from the quickstart
> script but when I go to the UI, I only get the login screen, followed by
> the two-tone background and a "loading circle" which never completes
> loading. There are no errors in application.log.
> > Note: I am running inside a docker container but port 21000 is exposed
> to the host. I am querying the API from my browser on the host machine, so
> not from inside the docker container. It works with both localhost and the
> internal docker ip.
> > Any help debugging/fixing this would be greatly appreciated.
> > *EDIT:* Running the master branch outside of docker,
> "mylaptopname:21000" works just fine but "localhost:21000" suffers from the
> same issue.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>
>
>
>
>

[jira] [Commented] (ATLAS-1408) Creating an attribute definition of array type, where the elements have a dot in the typename causes issues

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-1408:
-

[~madhan.neethiraj] pointed me to the '.' being the problem. Irrespective of 
the solutions to this specific problem, it would be nice to not get the server 
into an unrecoverable state.

> Creating an attribute definition of array type, where the elements have a dot 
> in the typename causes issues
> ---
>
> Key: ATLAS-1408
> URL: https://issues.apache.org/jira/browse/ATLAS-1408
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Hemanth Yamijala
>Priority: Critical
>
> I created a type File.v1 and then another type FileSet.v1 which contains an 
> array of File.v1 type instances. The creation was using the 
> {{AtlasClient.createType(TypeDef)}} API. This returned back successfully. 
> However, post this Atlas server went into a funny state where simple DSL 
> queries like {{hive_table}} started failing. Looking the application logs, 
> noticed this error post the registration of the FileSet.v1 type:
> {code}
> 2016-12-20 13:46:53,960 INFO  - [pool-2-thread-4 - 
> 8eaf688d-9cd4-46dc-92da-d84991512e9b:] ~ TypeSystem reset invoked by 
> TypeRegistry changes (DefaultMetadataService:749)
>  Many types restored and then 
> 2016-12-20 13:46:54,266 ERROR - [pool-2-thread-4 - 
> 8eaf688d-9cd4-46dc-92da-d84991512e9b:] ~ Failed to restore type-system after 
> TypeRegistry changes (DefaultMetadataService:759)
> org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown 
> datatype: array
> at 
> org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)
> at 
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.getDataType(TypeSystem.java:669)
> at 
> org.apache.atlas.typesystem.types.AttributeInfo.(AttributeInfo.java:46)
> at 
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.constructAttributeInfo(TypeSystem.java:496)
> at 
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.constructHierarchicalType(TypeSystem.java:540)
> at 
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.orderAndConstructTypes(TypeSystem.java:583)
> at 
> org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.verifyTypes(TypeSystem.java:709)
> at 
> org.apache.atlas.typesystem.types.TypeSystem.createTransientTypeSystem(TypeSystem.java:346)
> at 
> org.apache.atlas.services.DefaultMetadataService.onChange(DefaultMetadataService.java:753)
> at 
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$TypeRegistryUpdateHook.notifyListeners(AtlasTypeDefGraphStore.java:940)
> at 
> org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$TypeRegistryUpdateHook.onComplete(AtlasTypeDefGraphStore.java:924)
> {code}
> DSL failures post this error had this trace:
> {code}
> 2016-12-20 13:49:55,398 ERROR - [pool-2-thread-8 - 
> 3d671edf-9dce-4656-a5e3-04e3d3bd3ade:] ~ Unable to get entity list for 
> dslQuery hive_table (MetadataDiscoveryResource:141)
> org.apache.atlas.discovery.DiscoveryException: Invalid expression : hive_table
> at 
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:139)
> at 
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.searchByDSL(GraphBackedDiscoveryService.java:124)
> at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:51)
> at 
> org.apache.atlas.web.resources.MetadataDiscoveryResource.searchUsingQueryDSL(MetadataDiscoveryResource.java:135)
> at sun.reflect.GeneratedMethodAccessor41.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> {code}
> Restarting the server caused more issues because the types restoration failed 
> as in the error in the first stack trace, which caused failures in 
> initializations and so, effectively, the server did not come up. The 
> workaround was the delete the HBase titan table and start over again.



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

[jira] [Created] (ATLAS-1408) Creating an attribute definition of array type, where the elements have a dot in the typename causes issues

[Hemanth Yamijala (JIRA)]

Hemanth Yamijala created ATLAS-1408:
---

 Summary: Creating an attribute definition of array type, where the 
elements have a dot in the typename causes issues
 Key: ATLAS-1408
 URL: https://issues.apache.org/jira/browse/ATLAS-1408
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.8-incubating
Reporter: Hemanth Yamijala
Priority: Critical


I created a type File.v1 and then another type FileSet.v1 which contains an 
array of File.v1 type instances. The creation was using the 
{{AtlasClient.createType(TypeDef)}} API. This returned back successfully. 
However, post this Atlas server went into a funny state where simple DSL 
queries like {{hive_table}} started failing. Looking the application logs, 
noticed this error post the registration of the FileSet.v1 type:

{code}
2016-12-20 13:46:53,960 INFO  - [pool-2-thread-4 - 
8eaf688d-9cd4-46dc-92da-d84991512e9b:] ~ TypeSystem reset invoked by 
TypeRegistry changes (DefaultMetadataService:749)
 Many types restored and then 
2016-12-20 13:46:54,266 ERROR - [pool-2-thread-4 - 
8eaf688d-9cd4-46dc-92da-d84991512e9b:] ~ Failed to restore type-system after 
TypeRegistry changes (DefaultMetadataService:759)
org.apache.atlas.typesystem.exception.TypeNotFoundException: Unknown datatype: 
array
at org.apache.atlas.typesystem.types.TypeSystem.getDataType(TypeSystem.java:192)
at 
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.getDataType(TypeSystem.java:669)
at org.apache.atlas.typesystem.types.AttributeInfo.(AttributeInfo.java:46)
at 
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.constructAttributeInfo(TypeSystem.java:496)
at 
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.constructHierarchicalType(TypeSystem.java:540)
at 
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.orderAndConstructTypes(TypeSystem.java:583)
at 
org.apache.atlas.typesystem.types.TypeSystem$TransientTypeSystem.verifyTypes(TypeSystem.java:709)
at 
org.apache.atlas.typesystem.types.TypeSystem.createTransientTypeSystem(TypeSystem.java:346)
at 
org.apache.atlas.services.DefaultMetadataService.onChange(DefaultMetadataService.java:753)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$TypeRegistryUpdateHook.notifyListeners(AtlasTypeDefGraphStore.java:940)
at 
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$TypeRegistryUpdateHook.onComplete(AtlasTypeDefGraphStore.java:924)
{code}

DSL failures post this error had this trace:

{code}
2016-12-20 13:49:55,398 ERROR - [pool-2-thread-8 - 
3d671edf-9dce-4656-a5e3-04e3d3bd3ade:] ~ Unable to get entity list for dslQuery 
hive_table (MetadataDiscoveryResource:141)
org.apache.atlas.discovery.DiscoveryException: Invalid expression : hive_table
at 
org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:139)
at 
org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.searchByDSL(GraphBackedDiscoveryService.java:124)
at 
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:51)
at 
org.apache.atlas.web.resources.MetadataDiscoveryResource.searchUsingQueryDSL(MetadataDiscoveryResource.java:135)
at sun.reflect.GeneratedMethodAccessor41.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
{code}

Restarting the server caused more issues because the types restoration failed 
as in the error in the first stack trace, which caused failures in 
initializations and so, effectively, the server did not come up. The workaround 
was the delete the HBase titan table and start over again.



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

Re: Request for Atlas wiki or blog we can put Eclipse setup instructions on?

[Hemanth Yamijala]

David,


I am including back dev@atlas. I think you are proposing a change to making the 
edits simpler from the current process, hence would be nice if other people can 
chime in with their opinion.​


I guess we get some advantages in doing it the current way:


* We can follow all current processes for patch review & commit for docs as for 
source. Indeed, it would be nice to update documentation whenever sources are 
updated in the same patch. I know some Apache projects did insist on this 
practice a while back.

* Versioning comes for free and in well defined manners (although, I believe 
all Wiki systems provide versioning as well - so may not be a big issue)

* Docs can be distributed with the source package of Atlas and built and 
deployed independently. (again may not be a big advantage)


In your proposal, I am not still clear on the workflow for a doc update - in 
particular, how the review / commit would work. So would be nice to understand 
that a bit more in detail.


I am not sure if the choice of doing documentation this way was a deliberate 
one given the above or similar advantages. Maybe someone more in the know-how 
can elaborate.


Thanks

hemanth



From: David Radley <david_rad...@uk.ibm.com>
Sent: Monday, December 19, 2016 11:11 PM
To: Hemanth Yamijala
Subject: Re: Request for Atlas wiki or blog we can put Eclipse setup 
instructions on?

Hi Hemanth,
Ok thanks.

I have registered in twiki.org , made my changes in Microsoft Word, pasted them 
into twiki sandbox and then switched views to cut and paste the raw format out. 
This seems to work, though I need to manually change the size of the titles to 
fit what you have already done.

If I read this correctly, I assume the way we should be running this, is to the 
download and install Twiki on the web server running the Atlas site and then we 
could expose the rich text Wiki editor on the web site.  Maybe only allow 
committers create and update access for the wiki. The wiki would be the master 
then not Git.

all the best, David.







From:    Hemanth Yamijala <hyamij...@hortonworks.com>
To:David Radley/UK/IBM@IBMGB
Cc:"dev@atlas.incubator.apache.org" <dev@atlas.incubator.apache.org>
Date:19/12/2016 15:59
Subject:Re: Request for Atlas wiki or blog we can put Eclipse setup 
instructions on?




David,

I have indeed edited files directly.. There are only a handful of syntax 
elements we need to know and the help for these is available in many online 
sources (e.g. 
http://twiki.org/cgi-bin/view/TWiki/TextFormattingRules)<http://twiki.org/cgi-bin/view/TWiki/TextFormattingRules>.

Atlas docs can be built by running mvn docs (or something similar) and the 
files can be checked online. I don't know if there are twiki editors that make 
this easier to manage. Maybe others know?

Thanks
hemanth



From: David Radley <david_rad...@uk.ibm.com>
Sent: Monday, December 19, 2016 9:11 PM
To: Hemanth Yamijala
Cc: dev@atlas.incubator.apache.org
Subject: Fw: Request for Atlas wiki or blog we can put Eclipse setup 
instructions on?

Hi Hemanth,
I have not worked with Twiki files before - I assume people do not work 
directly with the raw format I get from Git (Eclipse shows me the wiki in a 
preview panel but does not give me a wiki rich text editor). I wondered what 
development software / process you and community use to create Twiki files.
   many thanks, David.



- Forwarded by David Radley/UK/IBM on 19/12/2016 14:55 -

From:David Radley/UK/IBM
To:dev@atlas.incubator.apache.org
Date:19/12/2016 10:33
Subject:Re: Request for Atlas wiki or blog we can put Eclipse setup 
instructions on?



Hi Hemanth,
That makes sense. I have raised ATLAS 1401 for this,  many thanks , David.




From:Hemanth Yamijala <hyamij...@hortonworks.com>
To:"dev@atlas.incubator.apache.org" <dev@atlas.incubator.apache.org>
Date:19/12/2016 04:26
Subject:Re: Request for Atlas wiki or blog we can put Eclipse setup 
instructions on?




Hi David,

I recommend these instructions be added to the source code under the 
documentation section. These will be in the Twiki style. Specifically here: 
https://github.com/apache/incubator-atlas/tree/master/docs/src/site/twiki. We 
could create a 'developer' section somewhere and start adding things like these 
in. Indeed, even the technical guide can be under this section, IMO.

We can then publish these docs to the website: 
http://atlas.incubator.apache.org/.

Advantage: Precisely for the reason you state, we can keep changing this as the 
instructions get stale and tag them to a specific release as required.

If you think this makes sense, please do open a JIRA ticket and contribute a 
patch, as usual (mo

Re: Request for Atlas wiki or blog we can put Eclipse setup instructions on?

[Hemanth Yamijala]

David,


I have indeed edited files directly.. There are only a handful of syntax 
elements we need to know and the help for these is available in many online 
sources (e.g. 
http://twiki.org/cgi-bin/view/TWiki/TextFormattingRules)<http://twiki.org/cgi-bin/view/TWiki/TextFormattingRules>.


Atlas docs can be built by running mvn docs (or something similar) and the 
files can be checked online. I don't know if there are twiki editors that make 
this easier to manage. Maybe others know?


Thanks

hemanth


From: David Radley <david_rad...@uk.ibm.com>
Sent: Monday, December 19, 2016 9:11 PM
To: Hemanth Yamijala
Cc: dev@atlas.incubator.apache.org
Subject: Fw: Request for Atlas wiki or blog we can put Eclipse setup 
instructions on?

Hi Hemanth,
I have not worked with Twiki files before - I assume people do not work 
directly with the raw format I get from Git (Eclipse shows me the wiki in a 
preview panel but does not give me a wiki rich text editor). I wondered what 
development software / process you and community use to create Twiki files.
many thanks, David.



- Forwarded by David Radley/UK/IBM on 19/12/2016 14:55 -

From:David Radley/UK/IBM
To:dev@atlas.incubator.apache.org
Date:19/12/2016 10:33
Subject:Re: Request for Atlas wiki or blog we can put Eclipse setup 
instructions on?



Hi Hemanth,
That makes sense. I have raised ATLAS 1401 for this,  many thanks , David.




From:    Hemanth Yamijala <hyamij...@hortonworks.com>
To:"dev@atlas.incubator.apache.org" <dev@atlas.incubator.apache.org>
Date:19/12/2016 04:26
Subject:Re: Request for Atlas wiki or blog we can put Eclipse setup 
instructions on?




Hi David,

I recommend these instructions be added to the source code under the 
documentation section. These will be in the Twiki style. Specifically here: 
https://github.com/apache/incubator-atlas/tree/master/docs/src/site/twiki. We 
could create a 'developer' section somewhere and start adding things like these 
in. Indeed, even the technical guide can be under this section, IMO.

We can then publish these docs to the website: 
http://atlas.incubator.apache.org/.

Advantage: Precisely for the reason you state, we can keep changing this as the 
instructions get stale and tag them to a specific release as required.

If you think this makes sense, please do open a JIRA ticket and contribute a 
patch, as usual (modifying or adding files under the docs/src/ folder and 
committers can take it forward.

Hope this makes sense.

Thanks
Hemanth

From: David Radley <david_rad...@uk.ibm.com>
Sent: Sunday, December 18, 2016 4:01 PM
To: dev@atlas.incubator.apache.org
Subject: Request for Atlas wiki or blog we can put Eclipse setup instructions 
on?

Hi ,
I have been asked to share the details on how I set up Eclipse of Atlas. I
followed detailed instructions prepared by Dave Kantor, which I have
slightly embellished. I think it would make sense to put these
instructions in the open so more people can benefit from them. Is there a
relevant wiki/blog that we can get access to, to put this sort of
information on? As the build dependancies change, the instructions will
get stale from time to time - so we will need to be able to easily keep
them up to date.  I suspect other people in the community may have
equivalent instructions IntellJ ,  many thanks , David.
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU




Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: Request for Atlas wiki or blog we can put Eclipse setup instructions on?

[Hemanth Yamijala]

Hi David,

I recommend these instructions be added to the source code under the 
documentation section. These will be in the Twiki style. Specifically here: 
https://github.com/apache/incubator-atlas/tree/master/docs/src/site/twiki. We 
could create a 'developer' section somewhere and start adding things like these 
in. Indeed, even the technical guide can be under this section, IMO.

We can then publish these docs to the website: 
http://atlas.incubator.apache.org/.

Advantage: Precisely for the reason you state, we can keep changing this as the 
instructions get stale and tag them to a specific release as required.

If you think this makes sense, please do open a JIRA ticket and contribute a 
patch, as usual (modifying or adding files under the docs/src/ folder and 
committers can take it forward.

Hope this makes sense.

Thanks
Hemanth

From: David Radley 
Sent: Sunday, December 18, 2016 4:01 PM
To: dev@atlas.incubator.apache.org
Subject: Request for Atlas wiki or blog we can put Eclipse setup instructions 
on?

Hi ,
I have been asked to share the details on how I set up Eclipse of Atlas. I
followed detailed instructions prepared by Dave Kantor, which I have
slightly embellished. I think it would make sense to put these
instructions in the open so more people can benefit from them. Is there a
relevant wiki/blog that we can get access to, to put this sort of
information on? As the build dependancies change, the instructions will
get stale from time to time - so we will need to be able to easily keep
them up to date.  I suspect other people in the community may have
equivalent instructions IntellJ ,  many thanks , David.
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

[jira] [Commented] (ATLAS-1389) Ping REST API entrypoint

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-1389:
-

Would the {{admin/status}} API not be sufficient for this? Is the intention to 
just check reachability, or have a more detailed notion of what a healthy Atlas 
server means? Even if the latter, could the {{admin/status}} endpoint be 
enhanced to return additional information?

> Ping REST API entrypoint
> 
>
> Key: ATLAS-1389
> URL: https://issues.apache.org/jira/browse/ATLAS-1389
> Project: Atlas
>  Issue Type: New Feature
>Reporter: David Kantor
>Assignee: Jeffrey Hagelberg
>
> Provide a lightweight ping API to allow clients to check status of Atlas 
> server.



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

Re: Improvement suggestion: change terms to be implemented as entities

[Hemanth Yamijala]

David,

I hope folks who are more plugged into Atlas on a day-to-day basis will provide 
relevant feedback. I have a very few comments below.

Regarding point 10: AFAIK, the most significant constraint of implementing 
terms as entities was that entity to entity relationships needed to be 
predefined, while tags / traits could be associated to any entity without this 
prior definition.

Regarding point 7: Tags and traits are indeed interchangeable. In the Atlas UI 
specifically, we always refer to trait types as tags (which is confusing IMO, 
but well, that's where we are)

Thanks
hemanth

From: David Radley 
Sent: Monday, December 12, 2016 11:27 PM
To: dev@atlas.incubator.apache.org
Subject: Improvement suggestion: change terms to be implemented as entities

Hi,
I have raised Atlas Jiras 1254 an 1245. I would like your feedback on
changing the implementation of business/glossary terms to be entities,
rather than trait types and trait instances. This would mean:

1) A Term would have a guid for ATLAS-1245
2) TermResourceDefinition could be changed to add relationship
projections, to support ATLAS-1254. I suggest we have "has a" , homonymns
and antonyms as the relationships.
- has-a relationships would allow us to associate a Hive table
with one term and its columns with other column related terms. So we could
then work with the  the business glossary terms and it would be aware of
the conceptual has-a relationship; rather than needing to interrogate the
asset. Of course glossary terms could be associated using has-a
relationships without being mapped to entities.
- homonyms and antonyms are commonly used with business glossaries

3) We would not have a new trait type that would be created for every term
- that cannot be deleted. Instead we would have 1 system type for term
that all terms entities would be associated with.
4) We would need to ensure we could still support for available_as_tag for
terms - this means we expose the term by name as a tag
5) I suggest we tolerate gets on the term using the the guid in the URI as
well as the fully qualified name. Creation of new terms should create
hrefs with the guid.
6) Term to term relationships would be simple in the code as we would use
an entity to entity relationship.
7) I notice in the the Atlas technical user guide (page 60), talks of
traits and tags terminology as being interchangable. In the code (apart
from in the supplied trait types),  it seems that traits are only used to
implement terms, I guess because terms are often known by their name. Tags
are somewhat different as they are used to interact with Ranger for tag
based policies.
8) The Atlas technical user guide talks of 2 ways of categorizing entities
, the business taxonomy and tags / traits. This change would be in line
with the separation.
9) Having a guid for terms would allow us to rename the term without
changing its identifier. I assume we should allow multiple terms of the
same name in different taxonomies.
10) I think the reason that terms were implemented as trait instances as
traits are identified by name so do not need guids and if a trait was an
entity, a user could define a relationship to a term entity, which would
be confusing. My suggestion is that if the user chooses to create a type
with a relationship to a term, then we reject the creation of the type .
At the moment they presumably could create a relationship to a taxonomy
which we should also reject.
11) As part of these changes, I suggest that entities also contain a
response field of terms. So it is more obvious to a REST client what the
associated terms are with an entity.

Please let me know if I have missed/misunderstood/misrepresented anything.
I appreciate your feedback, as I hope to address these Jiras soon,

many thanks , David.
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: Apache Atlas newbie alert -- atlas-dev & documentation

[Hemanth Yamijala]

Stephanie,

Thank you for the email. This question can most certainly be asked on
the dev mailing list, and hence I took the liberty of including that
here. Let's continue discussion here.

If I understand correctly, you would like to post a design document
for ATLAS-1095 to discuss in depth. It would be extremely useful to do
that. There are a couple of options:

* For fairly large enhancements, you could write a design document and
attach it to the JIRA and solicit feedback from the community on that.
Part of the feedback discussion usually occurs on the JIRA comments.
And revisions to the document can be reposted once there is
significant change. This would be a preferred way, IMHO. You can see
how this worked out in ATLAS-511 as an example.
* The other option is the Atlas Wiki:
https://cwiki.apache.org/confluence/display/ATLAS/Atlas+Home - but I
have rarely seen it being used, and while I have read access, I don't
know see to add pages etc. Maybe someone on the admin list can help
with that.

Please let me know if this answers your questions.

Thanks
Hemanth

On Fri, Dec 9, 2016 at 5:51 AM, Stephanie Hazlewood
 wrote:
> Hemanth,
>
> My apologies for not posting directly to the atlas-dev list. I noticed on
> the mail list that you typically answered questions around documentation -
> but being new - not sure if this is a good question to ask on the dev list
> itself as it is not really applicable to a current feature being
> implemented.
>
> Is it possible to post to the website architecture/design/terminology
> material for the purpose of collaboration/discussion?   I have a fair amount
> of material supporting a Jira (ATLAS-1095) opened last summer for a
> framework that IBM would like to propose and contribute to Apache Atlas.
>
> Best regards,
> Stephanie
>
>
> Stephanie Hazlewood
> STSM, Strategic Initiatives
> IBM Analytics
> e: stepha...@ca.ibm.com
> p: 905-413-5292
> m: 416-529-9987

Re: Podling Report Draft for December 2016

[Hemanth Yamijala]

Actually, one thing I forgot to mention was to include search related 
enhancements being worked on for 0.8-incubating.

Thanks
Hemanth

From: Hemanth Yamijala <hyamij...@hortonworks.com>
Sent: Monday, December 05, 2016 1:49 PM
To: dev@atlas.incubator.apache.org
Subject: Re: Podling Report Draft for December 2016

Hi Vimal,

Thank you for taking this up.

The report looks good to me.

Thanks
Hemanth

From: Vimal Sharma <visha...@hortonworks.com>
Sent: Monday, December 05, 2016 12:35 PM
To: dev@atlas.incubator.apache.org
Subject: Podling Report Draft for December 2016

Hi everyone,

All incubator projects are expected to submit a Podling report in every quarter.

The link below contains the last report we submitted for reference:
https://wiki.apache.org/incubator/September2016

We need to submit the report for the last quarter on the wiki by December 7th. 
Please review the content below and provide your feedback/suggestions.

// Report Beginning 
///

Atlas
Apache Atlas is a scalable and extensible set of core foundational governance 
services that enables enterprises to effectively and efficiently meet their 
compliance requirements within Hadoop and allows integration with the complete 
enterprise data ecosystem.

Atlas has been incubating since 2015-05-05.

Three most important issues to address in the move towards graduation:
1. Podling name search is pending.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No specific issues at this time to report.

How has the community developed since the last report?
1. We have added 3 new committers since the last report from different 
organizations. About 10 new contributors have been added since the last report. 
The current number of contributors is around 70.

2. The activity on the atlas-dev mailing list stands at around 610 messages per 
month between September and November [1]

3. People across various organizations are interested in exploring Atlas. We 
have received comments and suggestions from people who are evaluating Atlas for 
their governance requirements.

How has the project developed since the last report?
1. We are working towards a 0.8-incubating release in the next couple of 
months. This upcoming release would include major features like structured high 
level REST APIs, column level lineage for Hive CTAS queries, entity 
creation/updation from Atlas UI, Atlas Hook support for Hive2, Knox SSO support 
for Atlas, addition of user defined and system attributes to entities, Business 
Catalog GA

2. An abstraction layer has been added to make Atlas agnostic to the underlying 
graph database version

3. A total of 186 issues were reported between Sep 1st 2016 and Nov 30th 2016. 
122 issues have been resolved in the same time [2][3]

Date of last release:
2016-07-09: 07-incubating [4]

When were the last committers or PMC members elected?
1. The PPMC voted and elected 3 new members as committers to the project on 
2016-10-20: Madhan Neethiraj, Jeffrey Hagelberg and Vimal Sharma.

Links
[1] http://mail-archives.apache.org/mod_mbox/incubator-atlas-dev/

[2] 
https://issues.apache.org/jira/browse/ATLAS-1341?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%20%272016-09-01%27%20and%20created%20%3C%3D%20%272016-11-30%27

[3] 
https://issues.apache.org/jira/browse/ATLAS-1335?jql=project%20%3D%20ATLAS%20AND%20resolved%20%3E%3D%20%272016-09-01%27%20and%20resolved%20%3C%3D%20%272016-11-30%27

[4] 
https://mail-archives.apache.org/mod_mbox/www-announce/201607.mbox/%3ccaabv78fuzcv51e4pn8fg7nwkjyouqo9z2wnhsiz2estbtvj...@mail.gmail.com%3E

// Report End 
///


Thanks
Vimal

Re: Podling Report Draft for December 2016

[Hemanth Yamijala]

Hi Vimal,

Thank you for taking this up.

The report looks good to me.

Thanks
Hemanth

From: Vimal Sharma 
Sent: Monday, December 05, 2016 12:35 PM
To: dev@atlas.incubator.apache.org
Subject: Podling Report Draft for December 2016

Hi everyone,

All incubator projects are expected to submit a Podling report in every quarter.

The link below contains the last report we submitted for reference:
https://wiki.apache.org/incubator/September2016

We need to submit the report for the last quarter on the wiki by December 7th. 
Please review the content below and provide your feedback/suggestions.

// Report Beginning 
///

Atlas
Apache Atlas is a scalable and extensible set of core foundational governance 
services that enables enterprises to effectively and efficiently meet their 
compliance requirements within Hadoop and allows integration with the complete 
enterprise data ecosystem.

Atlas has been incubating since 2015-05-05.

Three most important issues to address in the move towards graduation:
1. Podling name search is pending.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No specific issues at this time to report.

How has the community developed since the last report?
1. We have added 3 new committers since the last report from different 
organizations. About 10 new contributors have been added since the last report. 
The current number of contributors is around 70.

2. The activity on the atlas-dev mailing list stands at around 610 messages per 
month between September and November [1]

3. People across various organizations are interested in exploring Atlas. We 
have received comments and suggestions from people who are evaluating Atlas for 
their governance requirements.

How has the project developed since the last report?
1. We are working towards a 0.8-incubating release in the next couple of 
months. This upcoming release would include major features like structured high 
level REST APIs, column level lineage for Hive CTAS queries, entity 
creation/updation from Atlas UI, Atlas Hook support for Hive2, Knox SSO support 
for Atlas, addition of user defined and system attributes to entities, Business 
Catalog GA

2. An abstraction layer has been added to make Atlas agnostic to the underlying 
graph database version

3. A total of 186 issues were reported between Sep 1st 2016 and Nov 30th 2016. 
122 issues have been resolved in the same time [2][3]

Date of last release:
2016-07-09: 07-incubating [4]

When were the last committers or PMC members elected?
1. The PPMC voted and elected 3 new members as committers to the project on 
2016-10-20: Madhan Neethiraj, Jeffrey Hagelberg and Vimal Sharma.

Links
[1] http://mail-archives.apache.org/mod_mbox/incubator-atlas-dev/

[2] 
https://issues.apache.org/jira/browse/ATLAS-1341?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%20%272016-09-01%27%20and%20created%20%3C%3D%20%272016-11-30%27

[3] 
https://issues.apache.org/jira/browse/ATLAS-1335?jql=project%20%3D%20ATLAS%20AND%20resolved%20%3E%3D%20%272016-09-01%27%20and%20resolved%20%3C%3D%20%272016-11-30%27

[4] 
https://mail-archives.apache.org/mod_mbox/www-announce/201607.mbox/%3ccaabv78fuzcv51e4pn8fg7nwkjyouqo9z2wnhsiz2estbtvj...@mail.gmail.com%3E

// Report End 
///


Thanks
Vimal

Re: Interest in Apache Atlas

[Hemanth Yamijala]

Hi Sandeep,

Responses inline. Hoping others can pitch in with more recent information, as 
mine might be a little dated.

Thanks
hemanth

From: Sandeep Nayak 
Sent: Sunday, December 04, 2016 12:00 AM
To: dev@atlas.incubator.apache.org
Cc: Venkatesh Seetharam
Subject: Re: Interest in Apache Atlas

Hi all,

Sending a reminder, I am looking for answers to the questions below. Can
someone help?

Thanks in advance for your attention.

- Sandeep

On Thu, Dec 1, 2016 at 12:13 AM, Sandeep Nayak 
wrote:

> Hi all,
>
> I had asked a couple questions to Venkatesh earlier please see email
> below. He recommended that I move the questions to the dev mailing list and
> thus this mail.
>
> To follow up on the questions asked below to my queries
>
> (a) Multi-tenancy: If I were to bring in data-sets from different
> customers then I need to record, annotate or tag and provide access to
> data-sets only to the relevant owners. Is it possible for me to record and
> manage data-sets for different customers in a single Atlas instance? Does
> Atlas provide me with the necessary constructs to separate recording of
> data-sets by tenant and tracking metadata etc by tenant?

It is possible to build a solution on top of Atlas to satisfy your 
requirements. It appears you need a namespacing facility of sorts. While there 
is no native construct like that in Atlas today (please see ATLAS-51, which is 
still open), I guess you could rely on the extensibility of the type system to 
let your objects extend from a base type that defines a tenant attribute. Then 
use wrapper APIs that filter out objects according to the tenant in question. 
Of course, one could use the lower level APIs to get around this, and hence it 
is cooperative in nature.

>
> (c) Performance Numbers: I understand it is built to scale given the use
> of HBase but any performance numbers that can be shared will be helpful.
> E.g. Is there a limit to the number of data-sets I can record on Atlas? Are
> there performance numbers on the number of queries?
>

This is dated information (at least couple of months). If someone has updated 
numbers, we should hear from them. At that time, we tested importing 50K Hive 
tables and dependent objects (columns etc) with a total of about < 10M 
vertices. 

>From what I remember, I think we could import these in about 20 minutes or so. 
>However, this does make some assumptions about the dependencies on the data 
>sets and hence we could bump up parallelism for import. We tested reads with 
>queries from 30 users in parallel. Times vary based on type of queries - 
>simple lookups take seconds, but more complex queries like lineage take longer.

This is a constant source of improvement in the project and there are several 
JIRAs talking about performance changes including some that are still open. 
E.g. ATLAS-711.

> (d) Are there companies using Atlas in production at this stage?
>
> Thanks in advance for your responses.
>
> - Sandeep
>
>
>
>
> On Fri, Nov 18, 2016 at 9:10 AM, Venkatesh Seetharam  > wrote:
>
>> Sandeep - please use the dev mailing list for atlas for a prompt response.
>>
>> (a) How can one achieve multi-tenancy on Apache Atlas?
>> Can you pls elaborate? You can always have a package structure for your
>> data sets.
>>
>> (b) Is Atlas ready for production usage?
>> It depends, I think it is but needs some scripting around BCP, etc.
>>
>> (c) Are there published numbers on the volume of data-sets Atlas can
>> manage?
>> Its built to scale, uses Titan & Hbase as a backend store which is known
>> to scale.
>>
>> On Fri, Nov 4, 2016 at 12:02 PM Sandeep Nayak 
>> wrote:
>>
>>> Hi Venkatesh,
>>>
>>> I apologize for the direct email, if there is a better channel to
>>> surface my questions I will be happy to go there. I am subscribed to
>>> dev@atlas but thought that may not be the right forum for questions
>>> potential Atlas users may have.
>>>
>>> I am looking for Data Catalog solutions and in early evaluation and from
>>> what I read so far it appears Apache Atlas provides most of the
>>> capabilities I am looking for. Namely data-set registration, lineage
>>> tracking, access control (via Ranger), auditing to name a few.
>>>
>>> I do have a couple questions which will help me in my evaluation
>>>
>>> (a) How can one achieve multi-tenancy on Apache Atlas?
>>> (b) Is Atlas ready for production usage?
>>> (c) Are there published numbers on the volume of data-sets Atlas can
>>> manage? One of the requirements I pointed out above is data lineage and if
>>> I am ingesting streaming and batch data sets the typical volumes could be
>>> very high.
>>>
>>> Hoping you will point me in the right direction to get answers.
>>>
>>> Thanks for your time and help.
>>>
>>> Regards,
>>>
>>> Sandeep
>>>
>>
>

[jira] [Commented] (ATLAS-1346) Search APIs should return empty list instead of throwing exception

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-1346:
-

A long while back, on ATLAS-805, we discovered that Titan's read only 
operations also could end up mutating some underlying indexes. Without proper 
transaction boundaries, this seemed to cause some failures for operations run 
after the read queries - please look at this comment in particular: 
https://issues.apache.org/jira/browse/ATLAS-805?focusedCommentId=15289274=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15289274

So, could you please double-check if removing transactionality is still OK?

> Search APIs should return empty list instead of throwing exception
> --
>
> Key: ATLAS-1346
> URL: https://issues.apache.org/jira/browse/ATLAS-1346
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
> Fix For: 0.8-incubating
>
>
> Currently the APIs return a 404 when there's no result found in the 
> repository which causes the graph transaction to rollback, instead the search 
> API should return an empty list and the rest layer should translate it to a 
> 404 or the read-only APIs should be excluded from the GraphTransaction 
> interceptor.



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

Re: JSON License and Apache Projects

[Hemanth Yamijala]

Hi Madhan,

I think this is the problem:
https://github.com/apache/incubator-atlas/blob/master/addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java#L55

This is referring to JSONObject from org.json package.

Thanks
Hemanth

On Sat, Nov 26, 2016 at 1:01 PM, Madhan Neethiraj <mad...@apache.org> wrote:
> Hemanth, David,
>
>
>
> Atlas uses JOSN libraries from org.json4s, while the licensing issue seems to 
> be about the code/libraries from ‘https://github.com/stleary/JSON-java’. Are 
> both referring to the same?
>
> Thanks,
> Madhan
>
> On 11/25/16, 2:00 AM, "David Radley" <david_rad...@uk.ibm.com> wrote:
>
> Hi ,
> It does seem like we should move away from using this json library. Of the
> options, I suggest we use Jackson,
>all the best,  David.
>
>
>
> From:   Hemanth Yamijala <yhema...@gmail.com>
> To: dev@atlas.incubator.apache.org
> Date:   25/11/2016 09:13
> Subject:Fwd: JSON License and Apache Projects
>
>
>
> Atlas-dev,
>
> Is this something to worry about? I see references to
> o.json.JSONObject in HiveHook. And we seem to be pulling it in via
> Hive dependencies.
>
> Thanks
> hemanth
>
>
> -- Forwarded message --
> From: Ted Dunning <ted.dunn...@gmail.com>
> Date: Thu, Nov 24, 2016 at 6:40 AM
> Subject: Fwd: JSON License and Apache Projects
> To: "gene...@incubator.apache.org" <gene...@incubator.apache.org>
>
>
> The VP Legal for Apache has determined that the JSON processing library
> from json.org <https://github.com/stleary/JSON-java> is not usable as a
> dependency by Apache projects. This is because the license includes a line
> that places a field of use condition on downstream users in a way that is
> not compatible with Apache's license.
>
> This decision is, unfortunately, a change from the previous situation.
> While the current decision is correct, it would have been nice if we had
> had this decision originally.
>
> As such, some existing projects may be impacted because they assumed that
> the json.org dependency was OK to use.
>
> Incubator projects that are currently using the json.org library have
> several courses of action:
>
> 1) just drop it. Some projects like Storm have demos that use twitter4j
> which incorporates the problematic code. These demos aren't core and could
> just be dropped for a time.
>
> 2) help dependencies move away from problem code. I have sent a pull
> request to twitter4 <https://github.com/yusuke/twitter4j/pull/254>j, for
> example, that eliminates the problem. If they accept the pull, then all
> would be good for the projects that use twitter4j (and thus json.org)
>
> 3) replace the json.org artifact with a compatible one that is open
> source.
> I have created and published an artifact based on clean-room Android code
> <https://github.com/tdunning/open-json> that replicates the most important
> parts of the json.org code. This code is compatible, but lacks some
> coverage. It also could lead to jar hell if used unjudiciously because it
> uses the org.json package. Shading and exclusion in a pom might help. Or
> not. Go with caution here.
>
> 4) switch to safer alternatives such as Jackson. This requires code
> changes, but is probably a good thing to do. This option is the one that
> is
> best in the long-term but is also the most expensive.
>
>
> -- Forwarded message --
> From: Jim Jagielski <j...@apache.org>
> Date: Wed, Nov 23, 2016 at 6:10 AM
> Subject: JSON License and Apache Projects
> To: ASF Board <bo...@apache.org>
>
>
> (forwarded from legal-discuss@)
>
> As some of you may know, recently the JSON License has been
> moved to Category X (https://www.apache.org/legal/resolved#category-x).
>
> I understand that this has impacted some projects, especially
> those in the midst of doing a release. I also understand that
> up until now, really, there has been no real "outcry" over our
> usage of it, especially from end-users and other consumers of
> our projects which use it.
>
> As compelling as that is, the fact is that the JSON license
> itself is not OSI approved and is therefore not, by definition,
> an "Open Source license" and, as such, cannot be considered as
> one which is acceptable as related to categories.
>
> Therefore, w/ my VP Legal hat on, I am making the following

Fwd: JSON License and Apache Projects

[Hemanth Yamijala]

Atlas-dev,

Is this something to worry about? I see references to
o.json.JSONObject in HiveHook. And we seem to be pulling it in via
Hive dependencies.

Thanks
hemanth


-- Forwarded message --
From: Ted Dunning 
Date: Thu, Nov 24, 2016 at 6:40 AM
Subject: Fwd: JSON License and Apache Projects
To: "gene...@incubator.apache.org" 


The VP Legal for Apache has determined that the JSON processing library
from json.org  is not usable as a
dependency by Apache projects. This is because the license includes a line
that places a field of use condition on downstream users in a way that is
not compatible with Apache's license.

This decision is, unfortunately, a change from the previous situation.
While the current decision is correct, it would have been nice if we had
had this decision originally.

As such, some existing projects may be impacted because they assumed that
the json.org dependency was OK to use.

Incubator projects that are currently using the json.org library have
several courses of action:

1) just drop it. Some projects like Storm have demos that use twitter4j
which incorporates the problematic code. These demos aren't core and could
just be dropped for a time.

2) help dependencies move away from problem code. I have sent a pull
request to twitter4 j, for
example, that eliminates the problem. If they accept the pull, then all
would be good for the projects that use twitter4j (and thus json.org)

3) replace the json.org artifact with a compatible one that is open source.
I have created and published an artifact based on clean-room Android code
 that replicates the most important
parts of the json.org code. This code is compatible, but lacks some
coverage. It also could lead to jar hell if used unjudiciously because it
uses the org.json package. Shading and exclusion in a pom might help. Or
not. Go with caution here.

4) switch to safer alternatives such as Jackson. This requires code
changes, but is probably a good thing to do. This option is the one that is
best in the long-term but is also the most expensive.


-- Forwarded message --
From: Jim Jagielski 
Date: Wed, Nov 23, 2016 at 6:10 AM
Subject: JSON License and Apache Projects
To: ASF Board 


(forwarded from legal-discuss@)

As some of you may know, recently the JSON License has been
moved to Category X (https://www.apache.org/legal/resolved#category-x).

I understand that this has impacted some projects, especially
those in the midst of doing a release. I also understand that
up until now, really, there has been no real "outcry" over our
usage of it, especially from end-users and other consumers of
our projects which use it.

As compelling as that is, the fact is that the JSON license
itself is not OSI approved and is therefore not, by definition,
an "Open Source license" and, as such, cannot be considered as
one which is acceptable as related to categories.

Therefore, w/ my VP Legal hat on, I am making the following
statements:

 o No new project, sub-project or codebase, which has not
   used JSON licensed jars (or similar), are allowed to use
   them. In other words, if you haven't been using them, you
   aren't allowed to start. It is Cat-X.

 o If you have been using it, and have done so in a *release*,
   AND there has been NO pushback from your community/eco-system,
   you have a temporary exclusion from the Cat-X classification thru
   April 30, 2017. At that point in time, ANY and ALL usage
   of these JSON licensed artifacts are DISALLOWED. You must
   either find a suitably licensed replacement, or do without.
   There will be NO exceptions.

 o Any situation not covered by the above is an implicit
   DISALLOWAL of usage.

Also please note that in the 2nd situation (where a temporary
exclusion has been granted), you MUST ensure that NOTICE explicitly
notifies the end-user that a JSON licensed artifact exists. They
may not be aware of it up to now, and that MUST be addressed.

If there are any questions, please ask on the legal-discuss@a.o
list.

--
Jim Jagielski
VP Legal Affairs

Re: Titan Backend

[Hemanth Yamijala]

Hi,

FWIW, In addition to this, the Atlas community (in particular Jeffrey 
Hagelberg), is working on creating an abstraction layer between Atlas and 
Titan, so that it will be easier to plugin other implementations. You can track 
this work on the JIRA: https://issues.apache.org/jira/browse/ATLAS-610 and its 
subtasks.

Thanks
Hemanth

From: Vimal Sharma 
Sent: Saturday, November 19, 2016 11:28 PM
To: dev@atlas.incubator.apache.org; Ellis, Thomas
Subject: Re: Titan Backend

Hi Thomas,
Sorry for the delay in response.

We haven’t evaluated any alternatives to Titan and so there are no immediate 
plans of migrating to any other graph backend. Having said that, we will keep 
track of Titan licensing and if it moves out of Apache, we will discuss our 
plans in Atlas
mailing list.

Thanks
Vimal

From: "Ellis, Thomas" >
Reply-To: 
"dev@atlas.incubator.apache.org" 
>
Date: Saturday, November 19, 2016 at 2:32 AM
To: "dev@atlas.incubator.apache.org" 
>
Subject: Re: Titan Backend


Hi - is someone able to get back to me on this?


From: Ellis, Thomas
Sent: 11 November 2016 17:39:13
To: dev@atlas.incubator.apache.org
Subject: Titan Backend


Hi Atlas,


It doesn't look like Datastax, after their acquisition of Aurelius, are that 
keen to take on open source support of Titan or let it get submitted to Apache 
- 
https://lists.apache.org/thread.html/e4f2c1403bfb4fe75fce9bd6f3182b9a95b9830ad9893944bac01ed9@%3Cgeneral.incubator.apache.org%3E
 - what are Atlas' plans for the future graph backend in Atlas?

Tom Ellis
Principal Consultant - Technical Consulting

EXCELIAN LTD
44 Featherstone Street / London / EC1Y 8RN / UK
T: +44 (0)207 336 9504
www.excelian.com
[1463577696533_PastedImage]



The information contained in this email and any attached files is confidential 
and intended solely for the addressee(s). The email may be legally privileged 
or prohibited from disclosure and unauthorised use. If you are not the named 
addressee you may not use, copy, or disclose this information to any other 
person. If you received this message in error please notify the sender 
immediately and delete it from your system.



Any opinion or views contained in this email message are those of the sender, 
and do not represent those of the Company in any way and reliance should not be 
placed upon its contents. Unless otherwise stated, this email message is not 
intended to be contractually binding. Where an Agreement exists between our 
respective companies and there is conflict between the contents of this email 
message and the Agreement then the terms of that Agreement shall prevail.




Excelian Limited / 44 Featherstone Street London / EC1Y 8RN / United Kingdom


T +44 (0)207 336 9595 / www.excelian.com

[jira] [Closed] (ATLAS-1271) dadad

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala closed ATLAS-1271.
---

> dadad
> -
>
> Key: ATLAS-1271
> URL: https://issues.apache.org/jira/browse/ATLAS-1271
> Project: Atlas
>  Issue Type: Bug
>Reporter: dreal hakim
>




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

Re: (ERROR) apache.rat:apache-rat/plugin:too many unapproved licenses

[Hemanth Yamijala]

Hi,

We've seen test failures on and off - due to some timing issues with
the tests. If you are OK with it, you could try building with
-DskipTests to avoid the test failures.

Thanks
Hemanth

On Tue, Nov 1, 2016 at 7:26 PM, Bilal Arshad <b.ars...@derby.ac.uk> wrote:
> Thank you so much for the prompt replies.
>
> I tried cleaning any extra files that could have been created temporarily.
>
> And then I tried running the following command:
>
> export MAVEN_OPTS="-Xmx2536m -XX:MaxPermSize=512m" && mvn clean install
>
> I got this error:
>
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify (verify) on 
> project atlas-webapp: There are test failures.
>
> Would you be kind enough to suggest what else to try?
>
> Thanking you in anticipation.
>
> Kind Regards
> Bilal
>
> -Original Message-
> From: Apoorv Naik [mailto:an...@hortonworks.com]
> Sent: 01 November 2016 04:40
> To: dev@atlas.incubator.apache.org; Bilal Arshad <b.ars...@derby.ac.uk>
> Subject: Re: (ERROR) apache.rat:apache-rat/plugin:too many unapproved licenses
>
> I’ve run into rat issues a lot of times, I simply had to clean any extra 
> files that I created temporarily.
>
> Usually I use git clean -fd and git clean -fX to remove any unwanted 
> untracked files.
>
>
>
> On 10/31/16, 9:36 PM, "Hemanth Yamijala" <yhema...@gmail.com> wrote:
>
>>Hi Bilal,
>>
>>I see you opened a JIRA for this. That's one way to get answers. The
>>other is to send an email to dev@atlas.incubator.apache.org -
>>especially if you're not sure there is a bug, or an issue with your
>>environment. I've copied the email ID now in this response, so we could
>>take the conversation further there.
>>
>>I haven't run the rat check myself, but could be please check
>>$ATLAS_HOME/atlas/target/rat.txt and see if the files that are failing
>>the license checks are identified there?
>>
>>Thanks
>>Hemanth
>>
>>On Tue, Nov 1, 2016 at 12:51 AM, Bilal Arshad <b.ars...@derby.ac.uk> wrote:
>>> Apologies in advance if you are not the appropriate person to contact.
>>>
>>> Hey There,
>>>
>>> I was installing Apache-Atlas framework on Ubuntu 14.04. after git
>>> clone https://git-wip-us.apache.org/repos/asf/incubator-atlas.git
>>> atlas i was trying to export and install Maven through export
>>> MAVEN_OPTS="-Xmx1536m -XX:MaxPermSize=512m" && mvn clean install but
>>> it was giving following
>>> errors:
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.rat:apache-rat-plugin:0.7:check
>>> (rat-check) on project apache-atlas: Too many unapproved licenses: 1
>>> -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the
>>> errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using
>>> the -X switch to enable full debug logging. [ERROR] [ERROR] For more
>>> information about the errors and possible solutions, please read the
>>> following articles: [ERROR] [Help 1]
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>>
>>> i also tried some skip options like:
>>>
>>> -DskipTests
>>>
>>> -DskipTests -Drat.skip=true
>>>
>>> mvn clean validate -Pcheck-licenses
>>>
>>> but error was the same.
>>>
>>> your kind and urgent help in this regard will be highly appreciated.
>>>
>>> Cheers,
>>>
>>> Kind Regards
>>>
>>> Bilal Arshad
>>>
>>> Postgraduate Researcher
>>>
>>> University of Derby
>>>
>>> Ph: +44-1332-593732
>>>
>>>
>>>
>>>
>>>
>>> The University of Derby has a published policy regarding email and
>>> reserves the right to monitor email traffic.
>>> If you believe this was sent to you in error, please reply to the
>>> sender and let them know.
>>>
>>> Key University contacts: http://www.derby.ac.uk/its/contacts/
>>
>
>
> The University of Derby has a published policy regarding email and reserves 
> the right to monitor email traffic.
> If you believe this was sent to you in error, please reply to the sender and 
> let them know.
>
> Key University contacts: http://www.derby.ac.uk/its/contacts/

Re: (ERROR) apache.rat:apache-rat/plugin:too many unapproved licenses

[Hemanth Yamijala]

Hi Bilal,

I see you opened a JIRA for this. That's one way to get answers. The
other is to send an email to dev@atlas.incubator.apache.org -
especially if you're not sure there is a bug, or an issue with your
environment. I've copied the email ID now in this response, so we
could take the conversation further there.

I haven't run the rat check myself, but could be please check
$ATLAS_HOME/atlas/target/rat.txt and see if the files that are failing
the license checks are identified there?

Thanks
Hemanth

On Tue, Nov 1, 2016 at 12:51 AM, Bilal Arshad  wrote:
> Apologies in advance if you are not the appropriate person to contact.
>
> Hey There,
>
> I was installing Apache-Atlas framework on Ubuntu 14.04. after git clone
> https://git-wip-us.apache.org/repos/asf/incubator-atlas.git atlas i was
> trying to export and install Maven through export MAVEN_OPTS="-Xmx1536m
> -XX:MaxPermSize=512m" && mvn clean install but it was giving following
> errors:
>
> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.7:check
> (rat-check) on project apache-atlas: Too many unapproved licenses: 1 ->
> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run
> Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable
> full debug logging. [ERROR] [ERROR] For more information about the errors
> and possible solutions, please read the following articles: [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
> i also tried some skip options like:
>
> -DskipTests
>
> -DskipTests -Drat.skip=true
>
> mvn clean validate -Pcheck-licenses
>
> but error was the same.
>
> your kind and urgent help in this regard will be highly appreciated.
>
> Cheers,
>
> Kind Regards
>
> Bilal Arshad
>
> Postgraduate Researcher
>
> University of Derby
>
> Ph: +44-1332-593732
>
>
>
>
>
> The University of Derby has a published policy regarding email and reserves
> the right to monitor email traffic.
> If you believe this was sent to you in error, please reply to the sender and
> let them know.
>
> Key University contacts: http://www.derby.ac.uk/its/contacts/

Congratulations to the new committers

[Hemanth Yamijala]

Jeff, Madhan & Vimal,


Congratulations on the committership and best wishes to all of you in the role!


Thanks

Hemanth

Re: How can use external kafka

[Hemanth Yamijala]

The links below provide more information:

http://atlas.incubator.apache.org/Architecture.html - Please refer to 
"Integration" for an overview
http://atlas.incubator.apache.org/Configuration.html - Please refer to 
"Notification Configs" for a full list of all Configs. By setting the property 
atlas.notification.embedded = false, we will use external Kafka. The remaining 
properties like atlas.kafka.zookeeper.connect and atlas.kafka.bootstrap.servers 
should be configured to point to external brokers.

http://atlas.incubator.apache.org/AtlasTechnicalUserGuide.pdf  - Here, you can 
see the section "Messaging Integration with Atlas" - this lists all the formats 
of messages, topics and other details to write applications that integrate with 
Atlas using Kafka.

We are using Kafka 0.10.x. That would be suitable.

Hope that helps.

Thanks
Hemanth


From: zhao.hong...@zte.com.cn 
Sent: Thursday, October 20, 2016 7:53 AM
To: dev@atlas.incubator.apache.org
Subject: How can use  external kafka

Hi,

I want to know about how we can use our Atlas with external kafka ,if have
any document can share with us ,

and what kafaka version is suitable;

Regards,






Randy  Zhao
赵洪涛
TEL :15062208803

[jira] [Resolved] (ATLAS-1201) using progaurd in android for cordova plugin

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala resolved ATLAS-1201.
-
Resolution: Invalid

This is unlikely to be an Apache Atlas project issue. Could you please open 
this against the right project?

> using progaurd in android for cordova plugin
> 
>
> Key: ATLAS-1201
> URL: https://issues.apache.org/jira/browse/ATLAS-1201
> Project: Atlas
>  Issue Type: Bug
>Reporter: lokesh
>




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

Re: Rename trait to classification

[Hemanth Yamijala]

Hi David,

Reg. the point I made about sharing traits - I don't want to give an
impression that this as an agreed upon point. Apologize if I conveyed
that sense.

It is a fact that Atlas today has two concepts that are slightly
related: Traits (aka Tags) and Business Terms. The latter was new in
0.7. IMO, it is important that the Atlas community tries to converge
on an unambiguous definition of these concepts as the product would be
driven around these.

With respect to this thread, I am trying to fit in whether
"classification" is a new concept. Or it overlaps with one of the two
existing ones (which we are trying to rename).

I am certainly not a domain expert on this in any sense :-) - so
hoping that others who are would provide guidance (@aahn - ping?).

Thanks
hemanth

On Mon, Sep 26, 2016 at 2:59 PM, David Radley <david_rad...@uk.ibm.com> wrote:
> Hi Hermanth and Mandy ,
> Thanks for your feedback.
>
> It does seem like these are de-facto industry terms in the governance
> industry; the reason I say this is that looking around the web I see quite
> a few uses of the words governance classification in different domains
> (including in the Atlas documentation!).
>
> I was not aware of the idea that traits and terms would be authored by
> different roles - thanks for your explanation. What is coming up for me is
> :
>
> I think business users should be able to add new business terms (maybe
> going through a workflow and a governance curator then sorting out
> inconsistencies), as they are the most expert as the language they use.
> Classifications could be authored by different teams, for example levels
> of confidentiality (in Mandy's example) would be dictated by the
> governance team. Governance rules would run on these classifications.
>
> You say "So, it is hard to use traits in a shared sense or expect to have
> conventional usage" . I notice the Atlas tutorial did not give me this
> impression, as the example of a trait/tag is PII.
> Your description of traits implies they are more like free form labels .
> If this is the intent for traits, then it does not make sense to rename
> them to classification. Maybe traits should be called labels; so their
> name is more in line with their expected usage. Though we should change
> the tutorial!
>
> A business term is a type of classification -a semantic classification. We
> could add in the concept of classification which Business term and
> Business category  (Jira 1186 ) inherit from. This would allow us to add
> in confidential classifications and classifications schemes to organize.
>
> I look forwards to your thoughts,
>   all the best, David.
>
>
>
>
> From:   Hemanth Yamijala <hyamij...@hortonworks.com>
> To: David Radley <dev@atlas.incubator.apache.org>
> Date:   26/09/2016 05:33
> Subject:Re: Rename trait to classification
>
>
>
> Hi,
>
> Are these de-facto industry terms in the governance industry? If yes,
> would they make more sense to explore as part of the Business Taxonomy
> feature that's currently in alpha in 0.7, rather than the trait system?
>
> One differentiation we've been trying to express is that traits (also
> referred to as tags in some places in Atlas) are free form and left to the
> user using them. So, it is hard to use traits in a shared sense or expect
> to have conventional usage. So, traits would probably be a tool for a data
> scientist to quickly annotate something for their own discovery usage
> later.
>
> Business taxonomy, on the other hand, is something we are thinking as used
> to express standard classification, even if only within an organization,
> but maybe even across industry domains etc. They would likely be created
> by data stewards with knowledge of the domain and their usage would follow
> established practices (authorization controlling who can do what).
>
> Not sure if what we're referring to as "classification" here fits the
> "traits" or "business taxonomy" side more - trying to understand...
>
> Thanks
> hemanth
> 
> From: Mandy Chessell <mandy_chess...@uk.ibm.com>
> Sent: Sunday, September 25, 2016 9:56 PM
> To: David Radley
> Cc: dev@atlas.incubator.apache.org
> Subject: Re: Rename trait to classification
>
> Hello David,
> I also like the idea of using the term classification.
> Typically classifications in governance are ordered sets of values grouped
> into a classification scheme.  Is the notion of the classification scheme
> also part of the change you are thinking of?
>
> For example, the classification scheme and "unclassified" value which is
> the default classification for any data element that h

Re: Rename trait to classification

[Hemanth Yamijala]

Hi,

Are these de-facto industry terms in the governance industry? If yes, would 
they make more sense to explore as part of the Business Taxonomy feature that's 
currently in alpha in 0.7, rather than the trait system? 

One differentiation we've been trying to express is that traits (also referred 
to as tags in some places in Atlas) are free form and left to the user using 
them. So, it is hard to use traits in a shared sense or expect to have 
conventional usage. So, traits would probably be a tool for a data scientist to 
quickly annotate something for their own discovery usage later.

Business taxonomy, on the other hand, is something we are thinking as used to 
express standard classification, even if only within an organization, but maybe 
even across industry domains etc. They would likely be created by data stewards 
with knowledge of the domain and their usage would follow established practices 
(authorization controlling who can do what).

Not sure if what we're referring to as "classification" here fits the "traits" 
or "business taxonomy" side more - trying to understand...

Thanks
hemanth

From: Mandy Chessell 
Sent: Sunday, September 25, 2016 9:56 PM
To: David Radley
Cc: dev@atlas.incubator.apache.org
Subject: Re: Rename trait to classification

Hello David,
I also like the idea of using the term classification.
Typically classifications in governance are ordered sets of values grouped
into a classification scheme.  Is the notion of the classification scheme
also part of the change you are thinking of?

For example, the classification scheme and "unclassified" value which is
the default classification for any data element that has no classification
from this scheme associated with it.  The other values are defined in
increasing levels of sensitivity.  There are also sub-classifications.  So
for example, confidential has sub-classifications of Business
Confidential, Partner Confidential and Personal Confidential.  If a rule
is defined for "confidential", it applies to all three of the
sub-classifications.

§Confidentiality Classification Scheme
§Confidentiality is used to classify the impact of disclosing information
to unauthorized individuals
•Unclassified
•Internal Use
•Confidential
•Business Confidential.
•Partner Confidential.
•Personal Information.
•Sensitive
•Sensitive Personal
•Sensitive Financial
•Sensitive Operational
•Restricted
•Restricted Financial
•Restricted Operational
•Trade Secret


The classification schemes create a graduated view of how sensitive data
is.  We would also expect to see classification schemes for other aspects
of governance such as retention, confidence (quality) and criticality.


All the best
Mandy
___
Mandy Chessell CBE FREng CEng FBCS
IBM Distinguished Engineer
IBM Analytics Group CTO Office

Master Inventor
Member of the IBM Academy of Technology
Visiting Professor, Department of Computer Science, University of
Sheffield

Email: mandy_chess...@uk.ibm.com
LinkedIn: http://www.linkedin.com/pub/mandy-chessell/22/897/a49

Assistant: Janet Brooks - jsbrook...@uk.ibm.com



From:   David Radley/UK/IBM@IBMGB
To: dev@atlas.incubator.apache.org
Date:   23/09/2016 17:05
Subject:Re: Rename trait to classification



Hi Madhan,
That would be great :-)  thanks, David.



From:   Madhan Neethiraj 
To: "dev@atlas.incubator.apache.org" 
Date:   23/09/2016 16:48
Subject:Re: Rename trait to classification
Sent by:Madhan Neethiraj 



David,

I agree on replacing ‘trait’ with ‘Classification’. I guess the name
‘triat’ might have been influenced by Scala (and not from Ranger, which
doesn’t have ‘triat’ in its vocab..).

Instead of renaming in the existing APIs, how about we go with the new
name in the API introduced in ATLAS-1171?

Thanks,
Madhan



On 9/23/16, 1:35 AM, "David Radley"  wrote:

Hi,
I have raised Jira ATLAS-1187. This is to rename trait to
Classification.
I know that this would effect the API, so am keen to understand how we


agree to version the API maybe including other changes. I feel trait
is
not very descriptive and I assume comes from Ranger terminology. I
think
using classification instead brings us into using terminology better
representing the Atlas capability and its role in governance use
cases. I
am keen to get your feedback. I do not feel that I should just submit
a
fix like this - I think we need more agreement to account for the
impact
on current users. At the same time, we are still in incubation we
should
be able to make changes like this to polish the API.

I am looking forward to your thoughts,   David Radley
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with
number
741598.
Registered 

[jira] [Resolved] (ATLAS-1189) Server Signature validation on client failed while using only CA in the client truststore

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala resolved ATLAS-1189.
-
Resolution: Invalid

I am suspecting this is not an Apache Atlas project issue, but maybe some other 
project. Could you please confirm? If yes, please file a JIRA against the right 
component. If it is related to Atlas, please reopen the issue and provide some 
more information in the report. Thanks!

> Server Signature validation on client failed while using only CA in the 
> client truststore
> -
>
> Key: ATLAS-1189
> URL: https://issues.apache.org/jira/browse/ATLAS-1189
> Project: Atlas
>  Issue Type: Bug
>Reporter: Libois Claude
>




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

[jira] [Commented] (ATLAS-1145) Storm hook with kafka topic and hive bolt picks wrong hive table name

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-1145:
-

[~sarath.ku...@gmail.com], Some time back I had a working version of Kafka to 
Hive storm topology capturing lineage into Atlas etc. Code is here: 
https://github.com/yhemanth/storm-samples/blob/master/src/main/java/com/dsinpractice/storm/samples/WordCountTopology.java
 However, we shifted focus from Hive to HDFS for later testing.

The main issue AFAIK is to setup Hive for streaming accurately. It took some 
time for me to figure that out.  Wish I had documented the steps more clearly 
:-(

These are properties I have in my hive-site which *I think* were used to get 
these to work. Please use these in case they are of help.

{code}

hive.support.concurrency
true


hive.enforce.bucketing
true


hive.exec.dynamic.partition.mode
nonstrict


hive.compactor.initiator.on
true


hive.txn.manager
org.apache.hadoop.hive.ql.lockmgr.DbTxnManager


hive.compactor.initiator.on
true 


hive.compactor.worker.threads
1 

{code}

> Storm hook with kafka topic and hive bolt picks wrong hive table name 
> --
>
> Key: ATLAS-1145
> URL: https://issues.apache.org/jira/browse/ATLAS-1145
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Sarath Subramanian
>
> Storm hook with kafka topic and hive bolt picks kafka topic name as hive 
> table name



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

[jira] [Resolved] (ATLAS-1176) MultipartStream need readBodyDataStream

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala resolved ATLAS-1176.
-
Resolution: Invalid

The issue does not seem to be a part of Atlas project. Please assign against 
right project.

> MultipartStream need readBodyDataStream
> ---
>
> Key: ATLAS-1176
> URL: https://issues.apache.org/jira/browse/ATLAS-1176
> Project: Atlas
>  Issue Type: Improvement
>Reporter: shuaib hasan khwaja
>
> Currently MultipartStream has support for "readBodyData", which basically 
> read the body data and write in out stream. It work great, if plan to have 
> body in memory or write in disk. But not work when you want to upstream some 
> where else.
> Its a good idea to get the InputStream for part body and use it for upload to 
> upstream. Some thing like...
> public InputStream readBodyDataStream(OutputStream output) IOException {
> return newInputStream();
> }



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

Re: Thoughts on the first step to understand the Atlas data model internals

[Hemanth Yamijala]

David,

This might not directly address all the points you mention below, but regarding 
learning about Atlas from a core understanding perspective, you may want to go 
through the document here: 
http://atlas.incubator.apache.org/AtlasTechnicalUserGuide.pdf. This is 
something we created just after the 0.7 release timeframe and feel it 
represents core concepts to a reasonable extent. 

There are several improvements that it needs: 
Likely, it is not complete and missing pieces. 
Further, being in PDF form makes it hard to edit, so moving it to a more 
editable format and specifically adding it to source code itself should be a 
goal.

Etc...

But if it forms a starting point, then it would be great to base further 
improvements on top of it.

Thanks
Hemanth

From: David Radley 
Sent: Thursday, September 15, 2016 6:26 PM
To: atlas
Subject: Thoughts on the first step to understand the Atlas data model internals

Hi,
I am looking to understand the important pieces in the Atlas architecture
and the order that is useful to think about them. I wanted to check my
understanding and questions around the top level data model concept as
someone relatively new to the project. then update the docs. I am
interested in feedback / thoughts / things I may have misunderstood. I
think the next areas for a person looking to understand the internals to
understand is the type system and providers and maybe then tracking how
the code flows from the web to the graph.

It seems that the data model of Atlas is the where to start; the
fundamental interface is interface ResourceDefinition and the base object
is BaseResourceDefinition. As the top level data object, I think this
needs to be simple and intuitive and have a defined purpose.
I would expect top level metadata objects should have the ability to have
relationships and attributes, which it seems to have and a way to identify
them (names and guid - which I do not see in this object)

I do not think the validate*** request call methods should live in this
interface. I would separate out request logic from the core data model
object; as they are different concerns.

The baseResourceDefinition has :
 protected static final TypeSystem typeSystem = TypeSystem.getInstance
();

protected final Set instanceProperties = new HashSet<>();
protected final Set collectionProperties = new HashSet<>();
protected Map propertyDefs = new
HashMap<>();
protected Map properties = new HashMap<>();

protected final Map projections = new HashMap<>();
protected final Map relations = new HashMap<>();

protected final PropertyMapper propertyMapper;
protected final Map
propertyValueFormatters = new HashMap<>();


There is an implied concept of  Property here in the naming of these
fields. If this is important then I suggest we have a Property class /
Interface defining what we mean by it.
I see there are projections and relationships. do we need both of these
concepts in the top level object as the only implementation of a
Projection is a RelationshipProjection.
I see AttributeDefintion in the list, this class does not subclass
ResourceDefintion - I am left thinking that in some way these are both
Definitions which I would expect to be a super class / interface.   Also
given that this is in a systemtypes package it should be a system type.
I see AttributeInfo and a not sure how this related to
AttributeDefintions. It would be great to be able to add in javadoc to
help here.
EntityResourceDefinition implements ResourceDefinition but says typename
is not meaningful for it. This is confusing. We should have an interface
without a gettypename to be clean or at least an explanation.
In UML, we often view relationships to other objects as attributes. I
wonder how we think of attributes and relationships here - can you define
an attribute with typeA and have a relationship to TypeA. Can I assume
that attributes are contained compositions with the same lifeycle as the
container. Relationships could be bidirectional ,directional or
aggregation containment relationships with an independent  lifecycle to
the resourcedfintion
PropertyValueFormatter I wonder why these are in the top level object. Do
we expect different formatters for a given type? What is the use case here
- I wonder if we are exposing a plug point, so that other code could
provide custom formatters. If this is the intent how would this work?
PropertyMapper I find this name misleading. It seems to be translating for
fully formatted name to a clean name. I suggest using a more descriptive
name like PropertyNameCleanser.  Do we expect different Mappers for a
given type? What is the use case here - I wonder if we are exposing a plug
point, so that other code could provide custom mappers. If this is the
intent how would this work?

I 

[jira] [Assigned] (ATLAS-1173) Doc: Minor editorial bug in the example given for property atlas.server.ha.zookeeper.auth

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala reassigned ATLAS-1173:
---

Assignee: Hemanth Yamijala

> Doc: Minor editorial bug in the example given for property 
> atlas.server.ha.zookeeper.auth
> -
>
> Key: ATLAS-1173
> URL: https://issues.apache.org/jira/browse/ATLAS-1173
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>    Assignee: Hemanth Yamijala
>Priority: Minor
> Attachments: ATLAS-1173.patch
>
>
> In {{Configuration.twiki}}, we have specified the example for Zookeeper 
> security configs as follows (under the High Availability Properties).
> {code}
> atlas.server.ha.zookeeper.acl=auth:sasl:cli...@comany.com
> {code}
> The auth: prefix in the value is incorrect and should be removed.



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

[jira] [Updated] (ATLAS-1173) Doc: Minor editorial bug in the example given for property atlas.server.ha.zookeeper.auth

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala updated ATLAS-1173:

Attachment: ATLAS-1173.patch

Very trivial patch fixing the issue.

> Doc: Minor editorial bug in the example given for property 
> atlas.server.ha.zookeeper.auth
> -
>
> Key: ATLAS-1173
> URL: https://issues.apache.org/jira/browse/ATLAS-1173
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Priority: Minor
> Attachments: ATLAS-1173.patch
>
>
> In {{Configuration.twiki}}, we have specified the example for Zookeeper 
> security configs as follows (under the High Availability Properties).
> {code}
> atlas.server.ha.zookeeper.acl=auth:sasl:cli...@comany.com
> {code}
> The auth: prefix in the value is incorrect and should be removed.



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

[jira] [Updated] (ATLAS-1173) Doc: Minor editorial bug in the example given for property atlas.server.ha.zookeeper.auth

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala updated ATLAS-1173:

Affects Version/s: 0.7-incubating

> Doc: Minor editorial bug in the example given for property 
> atlas.server.ha.zookeeper.auth
> -
>
> Key: ATLAS-1173
> URL: https://issues.apache.org/jira/browse/ATLAS-1173
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>    Assignee: Hemanth Yamijala
>Priority: Minor
> Attachments: ATLAS-1173.patch
>
>
> In {{Configuration.twiki}}, we have specified the example for Zookeeper 
> security configs as follows (under the High Availability Properties).
> {code}
> atlas.server.ha.zookeeper.acl=auth:sasl:cli...@comany.com
> {code}
> The auth: prefix in the value is incorrect and should be removed.



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

[jira] [Created] (ATLAS-1173) Doc: Minor editorial bug in the example given for property atlas.server.ha.zookeeper.auth

[Hemanth Yamijala (JIRA)]

Hemanth Yamijala created ATLAS-1173:
---

 Summary: Doc: Minor editorial bug in the example given for 
property atlas.server.ha.zookeeper.auth
 Key: ATLAS-1173
 URL: https://issues.apache.org/jira/browse/ATLAS-1173
 Project: Atlas
  Issue Type: Bug
Reporter: Hemanth Yamijala
Priority: Minor


In {{Configuration.twiki}}, we have specified the example for Zookeeper 
security configs as follows (under the High Availability Properties).

{code}
atlas.server.ha.zookeeper.acl=auth:sasl:cli...@comany.com
{code}

The auth: prefix in the value is incorrect and should be removed.




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

Re: Podling report September 2016 for review

[Hemanth Yamijala]

Thanks to everyone who reviewed and replied.

I've added the content at https://wiki.apache.org/incubator/September2016.

Thanks
Hemanth

From: Hemanth Yamijala <yhema...@gmail.com>
Sent: Wednesday, September 07, 2016 11:27 AM
To: dev@atlas.incubator.apache.org
Subject: Re: Podling report September 2016 for review

Thanks, Ayub. Will modify this to "Versioned Kafka messages" and move
"Support for rolling upgrade" to the 2nd point in 0.8-incubating.

On Wed, Sep 7, 2016 at 11:23 AM, Ayub Khan Pathan
<apat...@hortonworks.com> wrote:
> +1.
> A small change: “Support for rolling upgrade” might send a broader message, 
> we might want to exclude it for now.
>
> Thanks
> Ayub Khan
>
>
> On 9/6/16, 11:05 PM, "Hemanth Yamijala" <yhema...@gmail.com> wrote:
>
> Hi Jakob,
>
> That is a typo. Will remove them before submitting on the wiki. Thank
> you for catching that.
>
> Thanks
> Hemanth
>
> On Tue, Sep 6, 2016 at 11:01 PM, Jakob Homan <jgho...@gmail.com> wrote:
> > +1.  What's the question for the triple question mark (on comm
> > development).  Are the numbers still unsure?
> >
> > On 5 September 2016 at 23:36, Vimal Sharma <visha...@hortonworks.com> 
> wrote:
>     >> +1 for the report.
> >>
> >> Thanks
> >> Vimal
> >>
> >>
> >>
> >>
> >> On 9/5/16, 8:10 PM, "Hemanth Yamijala" <hyamij...@hortonworks.com> 
> wrote:
> >>
> >>>Hi all,
> >>>
> >>>
> >>>All incubator projects are expected to submit a podling report once a 
> quarter.
> >>>
> >>>Here's the last report we submitted for reference: 
> http://wiki.apache.org/incubator/June2016
> >>>
> >>>
> >>>We need to update the current report on the wiki by September 7th.
> >>>
> >>>Please review the content below and let me know if there's any 
> feedback on the same.
> >>>
> >>>
> >>>Thanks
> >>>
> >>>Hemanth
> >>>
> >>>
> >>>
> >>>Atlas
> >>>
> >>>Apache Atlas is a scalable and extensible set of core foundational 
> governance
> >>>services that enables enterprises to effectively and efficiently meet 
> their
> >>>compliance requirements within Hadoop and allows integration with the 
> complete
> >>>enterprise data ecosystem
> >>>
> >>>Atlas has been incubating since 2015-05-05.
> >>>
> >>>Three most important issues to address in the move towards graduation:
> >>>
> >>>  1. Podling name search is pending.?
> >>>
> >>>Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> >>>aware of?
> >>>
> >>>  No specific issues at this time to report.
> >>>
> >>>How has the community developed since the last report?
> >>>
> >>>  1. ???We have added 4 new committers since the last report from 
> different
> >>>  organizations. Around 15 new contributors were added since the 
> last report.
> >>>  The current number of contributors is around 60.
> >>>  2. The activity on the atlas-dev mailing list stands at around 900 
> messages
> >>>   per month between June and August. [1]
> >>>
> >>>How has the project developed since the last report?
> >>>
> >>>  1. A major release, 0.7-incubating, was made in the month of July.
> >>> This release added several new features to make Atlas enterprise
> >>> ready including: Authentication and authorization support, High
> >>> availability, deeper integrations with other Hadoop components
> >>> including Hive, HDFS, Falcon etc., Entity versioning, support for
> >>> rolling upgrade, support for creating business taxonomies, 
> enhanced
> >>> user interface, better performance etc.
> >>>  2. Work is proceeding in 0.8-incubating to stabilize many of these
> >>>  features and also add several strategic improvements including
> >>>  abstr

Re: Podling report September 2016 for review

[Hemanth Yamijala]

Thanks, Ayub. Will modify this to "Versioned Kafka messages" and move
"Support for rolling upgrade" to the 2nd point in 0.8-incubating.

On Wed, Sep 7, 2016 at 11:23 AM, Ayub Khan Pathan
<apat...@hortonworks.com> wrote:
> +1.
> A small change: “Support for rolling upgrade” might send a broader message, 
> we might want to exclude it for now.
>
> Thanks
> Ayub Khan
>
>
> On 9/6/16, 11:05 PM, "Hemanth Yamijala" <yhema...@gmail.com> wrote:
>
> Hi Jakob,
>
> That is a typo. Will remove them before submitting on the wiki. Thank
> you for catching that.
>
> Thanks
> Hemanth
>
> On Tue, Sep 6, 2016 at 11:01 PM, Jakob Homan <jgho...@gmail.com> wrote:
> > +1.  What's the question for the triple question mark (on comm
> > development).  Are the numbers still unsure?
> >
> > On 5 September 2016 at 23:36, Vimal Sharma <visha...@hortonworks.com> 
> wrote:
> >> +1 for the report.
> >>
> >> Thanks
> >> Vimal
> >>
> >>
> >>
> >>
> >> On 9/5/16, 8:10 PM, "Hemanth Yamijala" <hyamij...@hortonworks.com> 
> wrote:
> >>
> >>>Hi all,
> >>>
> >>>
> >>>All incubator projects are expected to submit a podling report once a 
> quarter.
> >>>
> >>>Here's the last report we submitted for reference: 
> http://wiki.apache.org/incubator/June2016
> >>>
> >>>
> >>>We need to update the current report on the wiki by September 7th.
> >>>
> >>>Please review the content below and let me know if there's any 
> feedback on the same.
> >>>
> >>>
> >>>Thanks
> >>>
> >>>Hemanth
> >>>
> >>>
> >>>
> >>>Atlas
> >>>
> >>>Apache Atlas is a scalable and extensible set of core foundational 
> governance
> >>>services that enables enterprises to effectively and efficiently meet 
> their
> >>>compliance requirements within Hadoop and allows integration with the 
> complete
> >>>enterprise data ecosystem
> >>>
> >>>Atlas has been incubating since 2015-05-05.
> >>>
> >>>Three most important issues to address in the move towards graduation:
> >>>
> >>>  1. Podling name search is pending.?
> >>>
> >>>Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> >>>aware of?
> >>>
> >>>  No specific issues at this time to report.
> >>>
> >>>How has the community developed since the last report?
> >>>
> >>>  1. ???We have added 4 new committers since the last report from 
> different
> >>>  organizations. Around 15 new contributors were added since the 
> last report.
> >>>  The current number of contributors is around 60.
> >>>  2. The activity on the atlas-dev mailing list stands at around 900 
> messages
> >>>   per month between June and August. [1]
> >>>
> >>>How has the project developed since the last report?
> >>>
> >>>  1. A major release, 0.7-incubating, was made in the month of July.
> >>> This release added several new features to make Atlas enterprise
> >>> ready including: Authentication and authorization support, High
> >>> availability, deeper integrations with other Hadoop components
> >>> including Hive, HDFS, Falcon etc., Entity versioning, support for
> >>> rolling upgrade, support for creating business taxonomies, 
> enhanced
> >>> user interface, better performance etc.
> >>>  2. Work is proceeding in 0.8-incubating to stabilize many of these
> >>>  features and also add several strategic improvements including
> >>>  abstractions to the underlying graph database to make it easier
> >>>  to move to later versions, etc.
> >>>  3. A total of 302 issues were reported between June 1st 2016 and 
> August 31st
> >>> 2016. 266 issues were resolved in the same time frame [2],[3]
> >>>
> >>>
> >>>Date of last release:
> >>>
> >>>2016-07-09: 07-incubating [4]
> >>>
> >>>When were the last committers or PMC members elected?
> >>>
> >>>  1. The PPMC voted and elected 4 new members as committers to
> >>>   the project on 2016-07-05: Tom Beerbower, Keval Bhatt,  David
> >>>   Kantor and Darshan Kumar.
> >>>
> >>>[1] http://mail-archives.apache.org/mod_mbox/incubator-atlas-dev/
> >>>[2] 
> https://issues.apache.org/jira/browse/ATLAS-1149?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202016-06-01%20AND%20created%20%3C%3D%202016-08-31
> >>>[3] 
> https://issues.apache.org/jira/browse/ATLAS-775?jql=project%20%3D%20ATLAS%20AND%20resolved%20%3E%3D%202016-06-01%20AND%20resolved%20%3C%3D%202016-08-31
> >>>[4]
> 
> >>>https://mail-archives.apache.org/mod_mbox/www-announce/201607.mbox/%3ccaabv78fuzcv51e4pn8fg7nwkjyouqo9z2wnhsiz2estbtvj...@mail.gmail.com%3E
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
>
>
>
>

Re: Podling report September 2016 for review

[Hemanth Yamijala]

Hi Jakob,

That is a typo. Will remove them before submitting on the wiki. Thank
you for catching that.

Thanks
Hemanth

On Tue, Sep 6, 2016 at 11:01 PM, Jakob Homan <jgho...@gmail.com> wrote:
> +1.  What's the question for the triple question mark (on comm
> development).  Are the numbers still unsure?
>
> On 5 September 2016 at 23:36, Vimal Sharma <visha...@hortonworks.com> wrote:
>> +1 for the report.
>>
>> Thanks
>> Vimal
>>
>>
>>
>>
>> On 9/5/16, 8:10 PM, "Hemanth Yamijala" <hyamij...@hortonworks.com> wrote:
>>
>>>Hi all,
>>>
>>>
>>>All incubator projects are expected to submit a podling report once a 
>>>quarter.
>>>
>>>Here's the last report we submitted for reference: 
>>>http://wiki.apache.org/incubator/June2016
>>>
>>>
>>>We need to update the current report on the wiki by September 7th.
>>>
>>>Please review the content below and let me know if there's any feedback on 
>>>the same.
>>>
>>>
>>>Thanks
>>>
>>>Hemanth
>>>
>>>
>>>
>>>Atlas
>>>
>>>Apache Atlas is a scalable and extensible set of core foundational governance
>>>services that enables enterprises to effectively and efficiently meet their
>>>compliance requirements within Hadoop and allows integration with the 
>>>complete
>>>enterprise data ecosystem
>>>
>>>Atlas has been incubating since 2015-05-05.
>>>
>>>Three most important issues to address in the move towards graduation:
>>>
>>>  1. Podling name search is pending.?
>>>
>>>Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>>>aware of?
>>>
>>>  No specific issues at this time to report.
>>>
>>>How has the community developed since the last report?
>>>
>>>  1. ???We have added 4 new committers since the last report from different
>>>  organizations. Around 15 new contributors were added since the last 
>>> report.
>>>  The current number of contributors is around 60.
>>>  2. The activity on the atlas-dev mailing list stands at around 900 messages
>>>   per month between June and August. [1]
>>>
>>>How has the project developed since the last report?
>>>
>>>  1. A major release, 0.7-incubating, was made in the month of July.
>>> This release added several new features to make Atlas enterprise
>>> ready including: Authentication and authorization support, High
>>> availability, deeper integrations with other Hadoop components
>>> including Hive, HDFS, Falcon etc., Entity versioning, support for
>>> rolling upgrade, support for creating business taxonomies, enhanced
>>> user interface, better performance etc.
>>>  2. Work is proceeding in 0.8-incubating to stabilize many of these
>>>  features and also add several strategic improvements including
>>>  abstractions to the underlying graph database to make it easier
>>>  to move to later versions, etc.
>>>  3. A total of 302 issues were reported between June 1st 2016 and August 
>>> 31st
>>> 2016. 266 issues were resolved in the same time frame [2],[3]
>>>
>>>
>>>Date of last release:
>>>
>>>2016-07-09: 07-incubating [4]
>>>
>>>When were the last committers or PMC members elected?
>>>
>>>  1. The PPMC voted and elected 4 new members as committers to
>>>   the project on 2016-07-05: Tom Beerbower, Keval Bhatt,  David
>>>   Kantor and Darshan Kumar.
>>>
>>>[1] http://mail-archives.apache.org/mod_mbox/incubator-atlas-dev/
>>>[2] 
>>>https://issues.apache.org/jira/browse/ATLAS-1149?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202016-06-01%20AND%20created%20%3C%3D%202016-08-31
>>>[3] 
>>>https://issues.apache.org/jira/browse/ATLAS-775?jql=project%20%3D%20ATLAS%20AND%20resolved%20%3E%3D%202016-06-01%20AND%20resolved%20%3C%3D%202016-08-31
>>>[4]
>>>https://mail-archives.apache.org/mod_mbox/www-announce/201607.mbox/%3ccaabv78fuzcv51e4pn8fg7nwkjyouqo9z2wnhsiz2estbtvj...@mail.gmail.com%3E
>>>
>>>
>>>
>>>
>>>
>>>

[jira] [Resolved] (ATLAS-972) Create entity response for a request with multiple entities is not returning back all definitions

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala resolved ATLAS-972.

Resolution: Duplicate

> Create entity response for a request with multiple entities is not returning 
> back all definitions
> -
>
> Key: ATLAS-972
> URL: https://issues.apache.org/jira/browse/ATLAS-972
> Project: Atlas
>  Issue Type: Bug
>    Reporter: Hemanth Yamijala
>
> Create multiple entities in the same POST request to 
> http:///api/atlas/entities. The response contains an 
> element called definition. But this contains only the first entity object in 
> the request and not all entity definitions. This is inconsistent.



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

[jira] [Commented] (ATLAS-1153) When ATLAS_HOOK topic is not created by Atlas, it is not reading messages from the beginning

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-1153:
-

[~ayubkhan], was there any offset committed for the topic before you deleted 
and recreated it?

> When ATLAS_HOOK topic is not created by Atlas, it is not reading messages 
> from the beginning
> 
>
> Key: ATLAS-1153
> URL: https://issues.apache.org/jira/browse/ATLAS-1153
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Khan
> Fix For: trunk
>
>
> When ATLAS_HOOK topic is not created by Atlas, it is not reading messages 
> from the beginning
> Steps to repro: 
> 1. Stop atlas.
> 2. Delete ATLAS_HOOK Topic and check it is actually deleted.
> 3. Create some hive tables(more than 3, preferrable) from hive client.
> 4. Now check that ATLAS_HOOK topic is created and also has messages for above 
> hive tables.
> 5. Now restart Atlas. Ideally Atlas should start consuming messages from 
> offset '0' but looks like it is consuming the latest one.
> I have also verified that 'auto.offset.reset' is set to 'smallest', which 
> should ideally force the consumer to read messages from offset '0'.
> {noformat}
> 2016-09-01 10:46:41,378 INFO  - [main:] ~ Property auto.commit.enable is 
> overridden to false (VerifiableProperties:68)
> 2016-09-01 10:46:41,379 INFO  - [main:] ~ Property auto.offset.reset is 
> overridden to smallest (VerifiableProperties:68)
> 2016-09-01 10:46:41,379 WARN  - [main:] ~ Property bootstrap.servers is not 
> valid (VerifiableProperties:83)
> 2016-09-01 10:46:41,379 INFO  - [main:] ~ Property group.id is overridden to 
> atlas (VerifiableProperties:68)
> 2016-09-01 10:46:41,379 WARN  - [main:] ~ Property hook.group.id is not valid 
> (VerifiableProperties:83)
> 2016-09-01 10:46:41,379 WARN  - [main:] ~ Property key.deserializer is not 
> valid (VerifiableProperties:83)
> 2016-09-01 10:46:41,380 WARN  - [main:] ~ Property key.serializer is not 
> valid (VerifiableProperties:83)
> {noformat}
> Kafka commands
> {noformat}
> [root@atlas-pixie-dust-test-7-unsecure-1 bin]# ./kafka-topics.sh --zookeeper 
> 172.22.74.193:2181,172.22.74.192:2181 --list
> ATLAS_ENTITIES
> ATLAS_HOOK
> __consumer_offsets
> [root@atlas-pixie-dust-test-7-unsecure-1 bin]# ./kafka-topics.sh --zookeeper 
> 172.22.74.193:2181,172.22.74.192:2181 --topic ATLAS_HOOK --delete
> Topic ATLAS_HOOK is marked for deletion.
> Note: This will have no impact if delete.topic.enable is not set to true.
> [root@atlas-pixie-dust-test-7-unsecure-1 bin]# ./kafka-topics.sh --zookeeper 
> 172.22.74.193:2181,172.22.74.192:2181 --list
> ATLAS_ENTITIES
> __consumer_offsets
> {noformat}
> Atlas logs showing initOffset set to 3, ideally this should be set to zero.
> {noformat}
> 2016-09-01 10:46:41,590 INFO  - [main:] ~ 
> [atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c], begin 
> rebalancing consumer 
> atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c try #0 
> (ZookeeperConsumerConnector:68)
> 2016-09-01 10:46:41,841 INFO  - [main:] ~ 
> [ConsumerFetcherManager-1472726801467] Stopping leader finder thread 
> (ConsumerFetcherManager:68)
> 2016-09-01 10:46:41,841 INFO  - [main:] ~ 
> [ConsumerFetcherManager-1472726801467] Stopping all fetchers 
> (ConsumerFetcherManager:68)
> 2016-09-01 10:46:41,842 INFO  - [main:] ~ 
> [ConsumerFetcherManager-1472726801467] All connections stopped 
> (ConsumerFetcherManager:68)
> 2016-09-01 10:46:41,843 INFO  - [main:] ~ 
> [atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c], Cleared 
> all relevant queues for this fetcher (ZookeeperConsumerConnector:68)
> 2016-09-01 10:46:41,845 INFO  - [main:] ~ 
> [atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c], Cleared 
> the data chunks in all the consumer message iterators 
> (ZookeeperConsumerConnector:68)
> 2016-09-01 10:46:41,849 INFO  - [main:] ~ 
> [atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c], Releasing 
> partition ownership (ZookeeperConsumerConnector:68)
> 2016-09-01 10:46:41,900 INFO  - [main:] ~ Starting round-robin assignment 
> with consumers 
> ArrayBuffer(atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c) 
> (RoundRobinAssignor:68)
> 2016-09-01 10:46:41,901 INFO  - [main:] ~ Consumer 
> atlas_atlas-pixie-dust-test-7-unsecure-1-1472726801437-dc09262c rebalancing 
> the following partitions for topic ATLAS_HOOK: ArrayBuffer(0) 
> (RoundRobinAssignor:68)
> 2016-09

Re: Podling Report Reminder - September 2016

[Hemanth Yamijala]

Hello Chris,

Thanks for checking. I don't think we've filed one - we will pursue this along 
with others in the dev community.

Thanks
Hemanth

From: Chris Douglas 
Sent: Thursday, September 01, 2016 7:42 AM
To: dev@atlas.incubator.apache.org
Subject: Re: Podling Report Reminder - September 2016

In its last report [1], Atlas cited the following issues blocking graduation:

  1. Podling name search is pending.
  2. Expand the community and add more committers.
  3. The upcoming release for Atlas (0.7-incubating) will be nearly 6 months
 since the last one. We would like to improve on this by making more
 frequent releases, and also encourage the community to discuss in
 release roadmaps etc.

Has the PODLINGNAMESEARCH [2,3] JIRA been filed, yet? I looked, but
couldn't find it. This appears to be the only significant blocker for
graduation. Atlas released 0.7 since its last report and can pursue
its community growth as a TLP. -C

[1] wiki.apache.org/incubator/June2016
[2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH
[3] http://incubator.apache.org/guides/names.html


On Tue, Aug 30, 2016 at 3:46 AM,   wrote:
> 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, 21 September 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, September 07).
>
> 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/September2016
>
> 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

[jira] [Resolved] (ATLAS-1150) A Cassandra node gets corrupted and contains only "key" and "column1" columns

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala resolved ATLAS-1150.
-
Resolution: Invalid

Not an Atlas issue. Please file against the right component

> A Cassandra node  gets corrupted and contains only "key" and "column1" columns
> --
>
> Key: ATLAS-1150
> URL: https://issues.apache.org/jira/browse/ATLAS-1150
> Project: Atlas
>  Issue Type: Bug
>Reporter: Michal Lefler
>




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

[jira] [Commented] (ATLAS-1110) Improve Atlas Entity Rest API to show Hive column type (e.g int) as a JSON Object.

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-1110:
-

The entity definition for a hive column already defines the column type as an 
attribute. When we GET the entity using Atlas REST API, we should be seeing a 
*values* attribute which is a map that contains all the attributes defined for 
a type with the values of the specific entity being retrieved. In the report 
above, I am not sure if the entire response is captured. Can you please check 
the entire response, or paste it here for reference?

> Improve Atlas Entity Rest API to show Hive column type (e.g int) as a JSON 
> Object. 
> ---
>
> Key: ATLAS-1110
> URL: https://issues.apache.org/jira/browse/ATLAS-1110
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Radley
>
> Issuing a REST call to see the details of an entity which is a Hive column I 
> issue: 
> curl h --user admin:admin 
> http://127.0.0.1:21000/api/atlas/v1/entities/d4e349c4-353b-4f03-8bc0-e894d559b74e
> I get
> "href": 
> "http://127.0.0.1:21000/api/atlas/v1/entities/d4e349c4-353b-4f03-8bc0-e894d559b74e;,
> "name": "total_emp",
> "id": "d4e349c4-353b-4f03-8bc0-e894d559b74e",
> "type": "hive_column",
> "creation_time": "2016-06-24:00:20:13",
> "entityText": "hive_column  type int table hive_table  createTime Fri 
> Jun 24 00:20:10 UTC 2016 lastAccessTime Fri Jun 24 00:20:10 UTC 2016 
> retention 0 parameters  numFiles 1 COLUMN_STATS_ACCURATE true 
> transient_lastDdlTime 1466727619 totalSize 46069 tableType MANAGED_TABLE 
> temporary false qualifiedName default.sample_08@Sandbox name sample_08 owner 
> hive qualifiedName default.sample_08.total_emp@Sandbox name total_emp owner 
> hive",
> "modified_time": "2016-06-24:00:20:24",
> "owner": "hive",
> "qualifiedName": "default.sample_08.total_emp@Sandbox",
> "state": "ACTIVE",
> "version": 0,
> "super_types": [
> "Asset",
> "Referenceable"
> ],
> I am looking to get hold of the real type (int in this case) - I can see that 
> in the entityText there as an int. It would be really helpful if this type 
> (and the other information) was properly exposed in the API as json objects;  
> not a text string that I need to parse which potentially could change its 
> content.



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

[jira] [Commented] (ATLAS-1083) Perf experiments: With 25 threads/users running to ~20 hours - trying to create unique class type with "com.thinkaurelius.titan.diskstorage.locking.PermanentLockingExce

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-1083:
-

[~ayubkhan], There are two config parameters that help with this locking 
performance. These are documented here: 
http://atlas.incubator.apache.org/Configuration.html under the "Performance 
Configuration Items" section. For greater number of users, we might need to 
configure these to higher than the default values for avoiding this exception. 
Can you please try out with these and see how it goes?

> Perf experiments: With 25 threads/users running to ~20 hours - trying to 
> create unique class type with 
> "com.thinkaurelius.titan.diskstorage.locking.PermanentLockingException: Could 
> not lock the keyColumn KeyColumn" - seems like deadlock situation.
> ---
>
> Key: ATLAS-1083
> URL: https://issues.apache.org/jira/browse/ATLAS-1083
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
> Attachments: CreateTypes.jmx, jstackdump.txt
>
>
> Perf experiments: With 25 threads/users running to ~20 hours - trying to 
> create unique class type fails with 
> "com.thinkaurelius.titan.diskstorage.locking.PermanentLockingException: Could 
> not lock the keyColumn KeyColumn" - seems like deadlock situation.
> *HDP-Build: HDP-2.5.0.0-1114*
> Steps to reproduce:
> 1. With 25 users per second, create a unique class type.
> 2. Run this for approximately 20 hours.
> 3. Below exception is seen in the application logs
> 4. Looking at the jstack dump, possibly this is because some of the threads 
> are waiting for the lock which is held other thread
> 5. Attaching jstack trace and jmeter jmx file used for the same.
> 6. Providing application log link for reference.
> {noformat}
> 2016-08-03 06:09:36,164 ERROR - [qtp1342234299-63262 - 
> b63be1d3-5ce9-484c-a907-70fc2aa5a047:] ~ Could not commit transaction 
> [102122] due to exception (StandardTitanGraph:731)
> com.thinkaurelius.titan.diskstorage.locking.PermanentLockingException: Could 
> not lock the keyColumn KeyColumn [k=0x  0-  0-  0-  0-  0-  0-  2-  9, c=0x 
> 16-200] on CF {} e
>   at 
> com.thinkaurelius.titan.diskstorage.hbase.HBaseKeyColumnValueStore.handleLockFailure(HBaseKeyColumnValueStore.java:161)
>   at 
> com.thinkaurelius.titan.diskstorage.hbase.HBaseKeyColumnValueStore.acquireLock(HBaseKeyColumnValueStore.java:142)
>   at 
> com.thinkaurelius.titan.diskstorage.keycolumnvalue.KCVSProxy.acquireLock(KCVSProxy.java:40)
>   at 
> com.thinkaurelius.titan.diskstorage.BackendTransaction.acquireEdgeLock(BackendTransaction.java:220)
>   at 
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.prepareCommit(StandardTitanGraph.java:466)
>   at 
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.commit(StandardTitanGraph.java:635)
>   at 
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1337)
>   at 
> com.thinkaurelius.titan.graphdb.database.management.ManagementSystem.commit(ManagementSystem.java:207)
>   at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.commit(GraphBackedSearchIndexer.java:387)
>   at 
> org.apache.atlas.repository.graph.GraphBackedSearchIndexer.onAdd(GraphBackedSearchIndexer.java:188)
>   at 
> org.apache.atlas.services.DefaultMetadataService.onTypesAdded(DefaultMetadataService.java:684)
>   at 
> org.apache.atlas.services.DefaultMetadataService.createOrUpdateTypes(DefaultMetadataService.java:254)
>   at 
> org.apache.atlas.services.DefaultMetadataService.createType(DefaultMetadataService.java:237)
>   at 
> org.apache.atlas.web.resources.TypesResource.submit(TypesResource.java:94)
>   at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatche

Re: [ANNOUNCE] New Committer: Darshan Kumar

[Hemanth Yamijala]

Congratulations, Darshan!

On Fri, Jul 29, 2016 at 12:25 PM, Shwetha Shivalingamurthy
 wrote:
> Hi All,
>
> The Apache Atlas PPMC has asked Darshan Kumar to become a committer and we
> are pleased to announce that he has accepted.
>
> Darshan contributed to the initial version of Atlas UI. Congratulations
> Darshan and welcome onboard!
>
>
> Regards,
> Apache Atlas PPMC Team
>
>
>

Re: [ANNOUNCE] New Committer: Keval Bhatt

[Hemanth Yamijala]

Congratulations, Keval!

On Fri, Jul 29, 2016 at 12:23 PM, Shwetha Shivalingamurthy
 wrote:
> Hi All,
>
> The Apache Atlas PPMC has asked Keval Bhatt to become a committer and we
> are pleased to announce that he has accepted.
>
> Keval has been a consistent contributor to Atlas and has contributed to
> the latest version of Atlas UI. Congratulations Keval and welcome onboard!
>
>
> Regards,
> Apache Atlas PPMC Team
>
>
>
>
>

Re: [ANNOUNCE] New Committer: Tom Beerbower

[Hemanth Yamijala]

Congratulations, Tom!

On Fri, Jul 29, 2016 at 12:21 PM, Shwetha Shivalingamurthy
 wrote:
> Hi All,
>
> The Apache Atlas PPMC has asked Tom Beerbower to become a committer and we
> are pleased to announce that he has accepted.
>
> Tom has been a consistent contributor to Atlas and has contributed entity
> notifications, hbase and solr integrations and other fixes.
> Congratulations Tom and welcome onboard!
>
>
> Regards,
> Apache Atlas PPMC Team
>
>
>

[jira] [Commented] (ATLAS-1057) Build break

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-1057:
-

I tried compiling when I saw this error, and it did indeed fail. But I retried 
it just now and it seems to be working fine. Maybe a transient repo issue? Can 
you please try again and see if it is working?

> Build break
> ---
>
> Key: ATLAS-1057
> URL: https://issues.apache.org/jira/browse/ATLAS-1057
> Project: Atlas
>  Issue Type: Bug
>Reporter: David Radley
>
> I am installing Atlas for the first time. By 
> git clone https://git-wip-us.apache.org/repos/asf/incubator-atlas.git atlas
> cd atlas
> export MAVEN_OPTS="-Xmx1536m -XX:MaxPermSize=512m" && mvn clean install
> I get an error building titan which looks like a dependancy issue. the 
> console shows:
>  
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) 
> on project atlas-titan: Error resolving project artifact: Could not transfer 
> artifact org.restlet.jee:org.restlet:pom:2.3.0 from/to apache.snapshots.repo 
> (https://repository.apache.org/content/groups/snapshots): handshake alert:  
> unrecognized_name for project org.restlet.jee:org.restlet:jar:2.3.0 -> [Help 
> 1]
>  



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

[jira] [Created] (ATLAS-1022) Update typesystem wiki with details

[Hemanth Yamijala (JIRA)]

Hemanth Yamijala created ATLAS-1022:
---

 Summary: Update typesystem wiki with details
 Key: ATLAS-1022
 URL: https://issues.apache.org/jira/browse/ATLAS-1022
 Project: Atlas
  Issue Type: Improvement
Reporter: Hemanth Yamijala
Assignee: Hemanth Yamijala


The current typesystem wiki page has a few issues:

* The descriptions are a bit too terse and can be expanded from a newbie's 
perspective.
* The formatting is messed up.

Since the type system is so central to Atlas, it can be given some more love.



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

[jira] [Assigned] (ATLAS-1021) Update Atlas architecture wiki

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala reassigned ATLAS-1021:
---

Assignee: Hemanth Yamijala

> Update Atlas architecture wiki
> --
>
> Key: ATLAS-1021
> URL: https://issues.apache.org/jira/browse/ATLAS-1021
> Project: Atlas
>  Issue Type: Improvement
>    Reporter: Hemanth Yamijala
>    Assignee: Hemanth Yamijala
>
> There have been some new additions to the Atlas architecture including new 
> apps like Business Taxonomy. This JIRA is to update the wiki with this 
> information.



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

Re: Review Request 49941: ATLAS-998: determine HA mode from property atlas.server.ids, instead of atlas.server.ha.enabled

[Hemanth Yamijala]

> On July 12, 2016, 5:52 a.m., Shwetha GS wrote:
> > common/src/main/java/org/apache/atlas/ha/HAConfiguration.java, line 65
> > 
> >
> > To make it backward compatible, as 0.7 is already out, can the check be 
> > if ha.enabled or ids > 1?
> 
> Madhan Neethiraj wrote:
> The fix is to remove 'ha.enabled' property. Instead of keeping it for 
> backward compatibility, I would suggest to document the removal of this 
> property in the next release notes.
> 
> Shwetha GS wrote:
> The fix is to use ids property to enable HA. For someone upgrading, all 
> these are manual changes and add to upgrade checklist and its better to 
> minimise if possible.
> 
> Can you update docs/src/site/twiki/HighAvailability.twiki? 
> 
> Its difficult to compile this list during release. Can you create 
> upgrade.twiki under docs/src/site/twiki/ and add to it?

One other suggestion (can be done later in a follow-up JIRA as well): We could 
log a warning if we find the ha enabled property in the configuration and 
mention we're not using it as it is no longer supported.

We also need to change docs/src/site/twiki/Configuration.twiki, under High 
Availability properties.


- Hemanth


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


On July 13, 2016, 6:20 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/49941/
> ---
> 
> (Updated July 13, 2016, 6:20 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-998
> https://issues.apache.org/jira/browse/ATLAS-998
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Updated to use atlas.server.ids property to determine if multiple instances 
> of Atlas are configured to run (in HA mode), instead of 
> atlas.server.ha.enabled
> 
> 
> Diffs
> -
> 
>   common/src/main/java/org/apache/atlas/ha/HAConfiguration.java f3c9bc5 
>   common/src/test/java/org/apache/atlas/ha/HAConfigurationTest.java a3129c9 
>   
> repository/src/test/java/org/apache/atlas/repository/audit/HBaseBasedAuditRepositoryHATest.java
>  2f7edb4 
>   
> repository/src/test/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexerMockTest.java
>  94dd298 
>   
> repository/src/test/java/org/apache/atlas/services/DefaultMetadataServiceMockTest.java
>  393b539 
>   
> webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerTest.java
>  7860eb6 
>   
> webapp/src/test/java/org/apache/atlas/web/service/ActiveInstanceElectorServiceTest.java
>  2b7691f 
>   webapp/src/test/java/org/apache/atlas/web/service/ServiceStateTest.java 
> 77aba88 
> 
> Diff: https://reviews.apache.org/r/49941/diff/
> 
> 
> Testing
> ---
> 
> - Verified that all unit tests succeed
> - Verified that when multiple instances are listed in 'atlas.server.ids' 
> configuration, Atlas server takes HA code path
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: authentication with v0.7

[Hemanth Yamijala]

Hi Herman,

Sorry, it is not possible to use Apache Atlas 0.7 without an authentication 
mode. The simplest authentication setup is file based authentication the 
details of which are documented here: 
http://atlas.incubator.apache.org/Authentication-Authorization.html

To use the 0.7 server, you would need to use the 0.7 version of the Atlas 
client. With it, you can look at the QuickStart example to see how 
authentication is implemented in the client library.

https://github.com/apache/incubator-atlas/blob/0.7-incubating/webapp/src/main/java/org/apache/atlas/examples/QuickStart.java

Specifically, this constructor of AtlasClient: 
https://github.com/apache/incubator-atlas/blob/0.7-incubating/client/src/main/java/org/apache/atlas/AtlasClient.java#L144

Hope this helps.

Thanks
Hemanth

From: Herman Yu 
Sent: Wednesday, July 06, 2016 8:07 PM
To: dev@atlas.incubator.apache.org
Subject: authentication with v0.7

Hi,

Is there a way to disable authentication with v0.7 (no login page with UI and 
REST calls doesn’t require U/P)? We are testing codes (uses atlasClient)  built 
for v0.5 on v0.7 on a sandbox environment, it fails with authentication. v0.7 
is configured using simple file based authentication.

I tried set all authentication.method to false in atlas-application.properties, 
it seems still default to simple, UI still displays login page and REST calls 
still failed with authentication failure.

if not, where is the best place to find changes required to atlasClient based 
codes to make it work with authentication?

Thanks
Herman.

[jira] [Resolved] (ATLAS-992) Added support for message queue properties an Selectors in Apache.NMS.MSMQ

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala resolved ATLAS-992.

Resolution: Invalid

This does not seem to be an Apache Atlas project's issue. Could you please file 
this against the right component?

> Added support for message queue properties an Selectors in Apache.NMS.MSMQ
> --
>
> Key: ATLAS-992
> URL: https://issues.apache.org/jira/browse/ATLAS-992
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Stephane Ramet
> Attachments: 2016-07-05 - Apache.NMS.MSMQ.patch
>
>
> The proposed package implements the following enhancements :
> 1. Support for communication of message properties between compatible peers
> The DefaultMessageConverter has been enhanced, so as to marshall custom 
> message properties in the MSMQ Message.Extension field, along with the 
> NMSCorrelationID which was already marshalled in this field.
> An additional flag specifies whether the MSMQ Message.Label field should be 
> populated with the NMSType (as currently - default value) or with the value 
> of a message property called "Label".
> 2. Support for selectors
> A parser for selection strings has been introduced.
> It is based on the Apache.ActiveMQ V4 implementation, ported from Java to C#.
> MessageReaders have been developped, that support various types of filtering:
> - no filtering when no selector strings are specified.
> - filtering based on the Id (NMSMessageID), CorrelationId (NMSCorrelationID) 
> or LookupId properties.
> - filtering based on any other valid selection string.
> MessageReaders have been introduced in MessageConsumers and QueueBrowsers.
> The generic filtering system, based on a selection string, has - at least - 
> two limitations:
> - it cannot be fully included in the build chains: the source code is 
> generated from SelectorParser.csc (a port of ActiveMQ's SelectorParser.jj) by 
> CSharpCC (https://github.com/deveel/csharpcc, a port of JavaCC, now 
> unmaintained). Due to limitations and/or bugs in the CSharpCC (eg. support 
> for namespace {}), the generated code must be rectified manually. A port to 
> another parser generator (eg. ANTLR) would certainly be required.
> - selection is performed by the client, by browsing through the messages in 
> the queue, via MessageQueue.GetMessageEnumerator2(), and retrieving only the 
> matching messages via MessageQueue.ReceiveByLookupId. When the queue gets 
> very long and the relevant messages are sparse, performance becomes an issue.



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

[VOTE] Release Apache Atlas version 0.7-incubating RC2

[Hemanth Yamijala]

Hi all,

This is a call for a vote on the Apache Atlas 0.7-incubating release
(release candidate RC2).

A vote was held on developer mailing list and it passed with 7 +1s.

Vote thread: https://s.apache.org/Czm4
Results thread: https://s.apache.org/PAeO

The source tarball (*.tar.gz), signature (*.asc), checksum (*.md5, *.sha512):
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.0-incubating-rc2/

The SHA512 checksum of the archive is
8B923CEA 2CDD32C8 7CE9A066 38002BFA 14F666DC C56F95AF 2805D5C1 08B58F9E 436E3E3C
61B40908 474C67E7 782E720E 1BFA3678 B8099EBC 282F64C2 C16A48C4

The commit id (15748e7bc5ed019a63326f201258e3a55d512d96) to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=commit;h=15748e7bc5ed019a63326f201258e3a55d512d96

The tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=log;h=refs/tags/release-0.7-rc2

The list of fixed issues:
https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=blob;f=release-log.txt;hb=refs/heads/0.7-incubating

Keys to verify the signature of the release artifact are available at:
http://www.apache.org/dist/incubator/atlas/KEYS
PGP release keys:
http://pgp.mit.edu/pks/lookup?op=vindex=0xA0E6F9F5D96BF0FD

Note that this is a source only release and we are voting on the
source release-0.7-incubating-rc2.

Please download, test, and try it out.

Vote will be open for at least 72 hours till 9th July, 2016 1 AM Pacific time.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thank you!

Regards,
Hemanth

[jira] [Commented] (ATLAS-979) Search: search on boolean values is not working

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-979:


Yes.

> Search: search on boolean values is not working
> ---
>
> Key: ATLAS-979
> URL: https://issues.apache.org/jira/browse/ATLAS-979
> Project: Atlas
>  Issue Type: Bug
>    Reporter: Hemanth Yamijala
>
> Create an type with a boolean attribute and an entity of the type. Search 
> using DSL with the query "typeName where boolean_attribute = true". This is 
> failing with an exception as below:
> {code}
> org.apache.atlas.discovery.DiscoveryException: Invalid expression : 
> hbase_table where isEnabled = true
> at 
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:139)
> at 
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.searchByDSL(GraphBackedDiscoveryService.java:124)
> at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
> at 
> org.apache.atlas.web.resources.MetadataDiscoveryResource.searchUsingQueryDSL(MetadataDiscoveryResource.java:116)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> ...
> Caused by: org.apache.atlas.AtlasException: Cannot combine types: boolean and 
> boolean
> at org.apache.atlas.query.TypeUtils$.combinedType(TypeUtils.scala:56)
> at 
> org.apache.atlas.query.Expressions$ComparisonExpression.dataType$lzycompute(Expressions.scala:639)
> at 
> org.apache.atlas.query.Expressions$ComparisonExpression.dataType(Expressions.scala:628)
> at 
> org.apache.atlas.query.Expressions$ComparisonExpression.dataType(Expressions.scala:623)
> at 
> org.apache.atlas.query.Expressions$FilterExpression.dataType$lzycompute(Expressions.scala:672)
> at 
> org.apache.atlas.query.Expressions$FilterExpression.dataType(Expressions.scala:667)
> at 
> org.apache.atlas.query.QueryProcessor$.validate(QueryProcessor.scala:49)
> at 
> org.apache.atlas.query.QueryProcessor.validate(QueryProcessor.scala)
> at 
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:144)
> at 
> org.apache.atlas.discovery.graph.GraphBackedDiscoveryService.evaluate(GraphBackedDiscoveryService.java:134)
> {code} 



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

[jira] [Commented] (ATLAS-970) Remove glyphicon from login.jsp

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-970:


[~kevalbhatt18], I see two references to this here:

{code}
dashboardv2/public/css/scss/form.scss:.input-group-btn .glyphicon {
dashboardv2/public/css/scss/loader.scss:.glyphicon-spin {
{code}

Are these required, or can they also be removed?

Other than that, looks good to me.

> Remove glyphicon from login.jsp
> ---
>
> Key: ATLAS-970
> URL: https://issues.apache.org/jira/browse/ATLAS-970
> Project: Atlas
>  Issue Type: Bug
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Blocker
> Attachments: ATLAS-970.patch
>
>




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

[jira] [Created] (ATLAS-985) ENTITY_DELETE entity notification does not change state of deleted entity

[Hemanth Yamijala (JIRA)]

Hemanth Yamijala created ATLAS-985:
--

 Summary: ENTITY_DELETE entity notification does not change state 
of deleted entity
 Key: ATLAS-985
 URL: https://issues.apache.org/jira/browse/ATLAS-985
 Project: Atlas
  Issue Type: Bug
Reporter: Hemanth Yamijala


* Delete an entity.
* Look at the corresponding Entity notification in ATLAS_ENTITIES topic.

The event has the right details for the deleted entity (GUID, etc,) but the 
state is set to ACTIVE still. This is slightly confusing as the entity was 
deleted.



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

[jira] [Created] (ATLAS-984) TRAIT_DELETE entity notification event does not contain the deleted trait information

[Hemanth Yamijala (JIRA)]

Hemanth Yamijala created ATLAS-984:
--

 Summary: TRAIT_DELETE entity notification event does not contain 
the deleted trait information
 Key: ATLAS-984
 URL: https://issues.apache.org/jira/browse/ATLAS-984
 Project: Atlas
  Issue Type: Bug
Reporter: Hemanth Yamijala


* Disassociate a trait instance from an entity.
* Look at the corresponding Entity notification event that is triggered. 

The event contains a traits structure which is empty. This provides no 
information when integrating about what the trait is that was deleted.




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

[jira] [Created] (ATLAS-983) Search: When selecting an attribute that is a reference or set of references, not all attribute definitions are returned.

[Hemanth Yamijala (JIRA)]

Hemanth Yamijala created ATLAS-983:
--

 Summary: Search: When selecting an attribute that is a reference 
or set of references, not all attribute definitions are returned.
 Key: ATLAS-983
 URL: https://issues.apache.org/jira/browse/ATLAS-983
 Project: Atlas
  Issue Type: Bug
Reporter: Hemanth Yamijala


DSL Search allows to select an attribute that is a reference or collection of 
other references. For e.g. query="hive_table, select columns"

As part of the search response, a dataType attribute is returned that is 
supposed to contain a list of attribute definitions pertaining to the entity 
that is being returned in the search results. In this case, it does not return 
all the attribute definitions, but only the first.



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