Re: Total number of results in search results (total count)

2019-05-08 Thread Apoorv Naik
The reasoning behind the exclusion of the total count is that the DSL query
is optimized to look at a smaller sub-graph (as small as possible), if the
total count has to be returned then we would have to start looking at a
bigger (potentially the complete graph) graph. As far as I can tell,
there's no better way of doing it as of now.

*Apoorv Naik*


On Wed, May 8, 2019 at 12:47 PM Verdan Mahmood 
wrote:

> Repost: any help or suggestions?
>
> Best,
> *Verdan Mahmood*
> (+31) 655 576 560
>
>
> -- Forwarded message -
> From: Verdan Mahmood 
> Date: Mon, May 6, 2019 at 3:21 PM
> Subject: Total number of results in search results (total count)
> To: 
>
>
> Hi,
> So we are using Atlas's DSL search API and need to get the total count
> along with paginated results.
> And to solve this problem, at the moment we are making two queries, one is
> to count all the entities and the second one to get the paginated result
> using the limit parameters.
>
> Is there a way to include the total count within the search response? Or
> any other nicer solution?
>
> Best,
> *Verdan Mahmood*
> (+31) 655 576 560
>


Re: Start with/Ends with/contains Elastic search queries in atlas with IDX_QRY_OFFENDING_CHARS.

2019-04-22 Thread Apoorv Naik
https://github.com/apache/atlas/blob/master/repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java

This is where the query is getting formed, I don't recall where the double
quotes are getting injected around the attribute value. Let me dig into
this more but someone more active should be able to assist you in a
better way.

On Mon, Apr 22, 2019 at 9:18 AM Apoorv Naik  wrote:

> AFAIK, the current implementation of the search is tuned for Solr. For
> Elastic search, you'll have to make some adjustments. I think the query
> provider logic is pluggable and configurable, so if you create a ES
> specific provider and configure Atlas to use that, this problem can be
> fixed.
>
> On Mon, Apr 22, 2019 at 8:55 AM Nallapati, Sreenivasulu <
> sreenivasulu_nallap...@intuit.com> wrote:
>
>> Hello Atlas team,
>>
>>
>>
>> Have observed when if there is a ['@','/',' ','-'] char in the attribute
>> filter query (ex: table-) in Start with/Ends with/contains queries, the
>> Elastic search query becomes
>>
>> Start with => "table-"*
>>
>> Ends with => *"table-"
>>
>> Contains  => *"table-"*
>>
>>
>>
>> The question is, the * should be outside of double quotes ("table-"*) or
>> with in double quotes ("table-*")? Elasticsearch is returning all the
>> entitites in the system if * is outside of the double quotes and it takes
>> very long times with offset and limit paginations.
>>
>> We are assuming the * should be with in double quotes.
>>
>> Please clarify, is this a expected behaviour or a bug
>>
>>
>>
>> It is very critical for our use case with special chars in the attribute
>> filter search.
>>
>>
>>
>>
>>
>> ---
>>
>> Regards,
>>
>> Sreeni
>>
>


Re: Start with/Ends with/contains Elastic search queries in atlas with IDX_QRY_OFFENDING_CHARS.

2019-04-22 Thread Apoorv Naik
AFAIK, the current implementation of the search is tuned for Solr. For
Elastic search, you'll have to make some adjustments. I think the query
provider logic is pluggable and configurable, so if you create a ES
specific provider and configure Atlas to use that, this problem can be
fixed.

On Mon, Apr 22, 2019 at 8:55 AM Nallapati, Sreenivasulu <
sreenivasulu_nallap...@intuit.com> wrote:

> Hello Atlas team,
>
>
>
> Have observed when if there is a ['@','/',' ','-'] char in the attribute
> filter query (ex: table-) in Start with/Ends with/contains queries, the
> Elastic search query becomes
>
> Start with => "table-"*
>
> Ends with => *"table-"
>
> Contains  => *"table-"*
>
>
>
> The question is, the * should be outside of double quotes ("table-"*) or
> with in double quotes ("table-*")? Elasticsearch is returning all the
> entitites in the system if * is outside of the double quotes and it takes
> very long times with offset and limit paginations.
>
> We are assuming the * should be with in double quotes.
>
> Please clarify, is this a expected behaviour or a bug
>
>
>
> It is very critical for our use case with special chars in the attribute
> filter search.
>
>
>
>
>
> ---
>
> Regards,
>
> Sreeni
>


Re: Special characters attribute filter search behaviour

2019-04-22 Thread Apoorv Naik
Hi Sreenivasulu,

The reasoning behind this code block is as follows.

The solr schema for JanusGraph is configured with a StandardTokenizer and
this cause the index to be created in a way that any index query with
special characters gets tokenized into smaller chunks and gives back wrong
results.

e.g. With the StandardTokenizer you can't index the email address, it gets
tokenized and the special characters are stripped out. So when you fire the
index query with the same email address it'll tokenize the email again and
the smaller tokens get used in the query. Now this produces false positives
as the smaller tokenized values might be present in some other entity.

This problem only arises when Atlas does a direct index query, the graph
query works fine because the graph layer has other mechanisms of retrieval.
But as you've seen, the query becomes slower.

Here's what can be done to fix this problem,

1. Change the Tokenizers/Analyzers in the solr.xml or the schema file to a
more suitable one.
2. Delete the indexes in JanusGraph and use the index repair utility to
rebuild the indexes.

Keep in mind that that re-indexing is a large overhead for Atlas. It might
take days or weeks to complete on an existing cluster with lots of data.
This solution is more suited to a new install of Atlas where the data is
minimal. Please let me know if you've any further questions.

On Sun, Apr 21, 2019 at 11:16 PM Nallapati, Sreenivasulu <
sreenivasulu_nallap...@intuit.com> wrote:

> Hi Apoorv/Madhan,
>
>
>
> Can you please help us understanding the below issue?
>
>
>
>
>
> ---
>
> Regards,
>
> Sreeni
>
>
>
> *From: *"Nallapati, Sreenivasulu" 
> *Date: *Sunday, 21 April 2019 at 11:24 PM
> *To: *"dev@atlas.apache.org" , "
> u...@atlas.apache.org" 
> *Subject: *Special characters attribute filter search behaviour
>
>
>
> Hello Atlas team,
>
>
>
> We are facing some performance issue with respect to the Entity Type
> attribute filter search.
>
>
>
> [image: cid:image001.png@01D4F899.68EC7A40]
>
>
>
>
>
> What is the reason behind  for going  in-memory or graph query in case of 
> special
> characters in string attribute filter query, even though the attribute is
> indexed? . Its taking very very long time to get the results back and we
> are getting gateway timeouts.
>
> The below code snippet says “in-memory or graph query in case” but
> doesn’t explain what is the reason behind it.
>
>
>
> private boolean isIndexSearchable(FilterCriteria filterCriteria,
> AtlasStructType structType) throws AtlasBaseException {
>
> String  qualifiedName = structType.getQualifiedAttributeName(
> filterCriteria.getAttributeName());
>
> Set indexedKeys   = context.getIndexedKeys();
>
> boolean ret   = indexedKeys != null && indexedKeys
> .contains(qualifiedName);
>
>
>
> if (ret) { // index exists
>
> // for string type attributes, don't use index query in the
> following cases:
>
> //   - operation is NEQ, as it might return fewer entries due
> to *tokenization* of vertex property value
>
> //   - value-to-compare has special characters
>
> AtlasType attributeType = structType.getAttributeType(
> filterCriteria.getAttributeName());
>
>
>
> if 
> (AtlasBaseTypeDef.ATLAS_TYPE_STRING.equals(attributeType.getTypeName()))
> {
>
> if (filterCriteria.getOperator() ==
> SearchParameters.Operator.NEQ) {
>
> if (LOG.isDebugEnabled()) {
>
> LOG.debug("NEQ operator found for string
> attribute {}, deferring to in-memory or graph query (might cause poor
> performance)", qualifiedName);
>
> }
>
>
>
> ret = false;
>
> } else if 
> (hasIndexQuerySpecialChar(filterCriteria.getAttributeValue()))
> {
>
> if (LOG.isDebugEnabled()) {
>
> LOG.debug("special characters found in filter
> value {}, deferring to in-memory or graph query (might cause poor
> performance)", filterCriteria.getAttributeValue());
>
> }
>
>
>
> ret = false;
>
> }
>
> }
>
> }
>
>
>
> if (LOG.isDebugEnabled()) {
>
> if (!ret) {
>
> LOG.debug("Not using index query for: attribute='{}',
> operator='{}', value='{}'", qualifiedName, filterCriteria.getOperator(),
> filterCriteria.getAttributeValue());
>
> }
>
> }
>
>
>
> return ret;
>
> }
>
>
>
>
>
>
>
>
>
> ---
>
> Regards,
>
> Sreeni
>


Re: Consensus for migration of git repositories to gitbox

2019-01-10 Thread Apoorv Naik
The migration is now complete. Please update the base url of the local git
repo to point to gitbox.apache.org instead of the git-wip-us URL.

https://gitbox.apache.org/repos/asf?p=atlas.git --> This is the new home of
Atlas codebase

For people who are interested in using github as integration point please
refer to the following link
https://reference.apache.org/committer/github

The associated INFRA ticket was INFRA-17611, please reach out to me or post
comments on the INFRA ticket directly in case you run into any issues.

*Apoorv Naik*


On Thu, Jan 10, 2019 at 2:44 AM David Radley 
wrote:

> Hi Madhan,
> +1 I like the idea of being pro active with this.
>
> We are looking to demo master Atlas code at a conference in the following
> week, so we need to have a working Atlas master build, so it would be good
> to make this change asap.
>
> On a related subject, would it be possible for the community to not make
> any big changes (types, software level changes or API changes) coming up
> to the week of the 16th of February - so the Atlas / Egeria demo continues
> to build. If there are big changes you need in, could I request that the
> community be informed and given a change to assess the impact during this
> period and potentially delay pervasive changes,
> many thanks , David.
>
>
> From:   Madhan Neethiraj 
> To: "dev@atlas.apache.org" 
> Date:   10/01/2019 07:37
> Subject:Re: Consensus for migration of git repositories to gitbox
>
>
>
> +1
>
> Thanks Apoorv for volunteering. Please keep the community updated of the
> progress and actions to be done by each to access the migrated repo.
>
> Thanks,
> Madhan
>
>
>
>
> On 1/9/19, 11:01 PM, "Ashutosh Mestry"  wrote:
>
> +1 for migrating Atlas repositories.
>
> Thanks Apoorv!
>
> ~ ashutosh
>
> On 1/9/19, 10:58 PM, "Nixon Rodrigues"
>  wrote:
>
> Thanks Apoorv for volunteering this effort
>
> +1 for migrating Atlas repositories to gitbox server.
>
> Regards,
> Nixon
>
>
>
> On Thu, Jan 10, 2019 at 11:50 AM Apoorv Naik
>  wrote:
>
> > Hi Atlas devs,
> >
> > There's an ASF initiative to migrate the git-wip-us-apache.org
> > repositories
> > to the gitbox server before Feb 7, after which it'll be mass
> migrated
> > without a warning. I volunteer to take this migration effort to
> avoid any
> > disruption to commit activity.
> >
> > PMCs and committers, please share your +1 or -1 vote for this
> move (this is
> > the first step in starting the migration)
> >
> > *Apoorv Naik*
> >
>
>
>
>
>
>
>
>
> 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 scaling question

2018-11-20 Thread Apoorv Naik
As of now only ONE instance can be active at a time. Atlas does not have
the capability to concurrently talk to same JanusGraph across different
instances.

In this ACTIVE-PASSIVE setup the REST calls will get directed to the active
instance.

Hope this helps.

*Apoorv Naik*


On Tue, Nov 20, 2018 at 10:19 AM abhay kumar  wrote:

> Hi,
> I have been trying to find out about how apache atlas horizontally scales.
> There is no information provided in apache atlas document. Could you please
> help me understand how atlas scales out.
> 1. Can multiple instances of it deployed on different machines ( all
> connected to same backend storage e.g. cassandra) and have instances to
> actively take rest calls for processing ( create/read/update/search types
> and entities).
> 2.  Would there be any issue with locking/transaction if all instances
> process the request ?
>
> I understand that the backend storage can be scaled out but I do not know
> apache atlas process, which uses janusdb, scales out.
>
> Thanks & Regards,
> Abhay
>


Re: RE: Need Help!!! Atlas Installation Error

2018-11-02 Thread Apoorv Naik
Not that I know of.

*Apoorv Naik*


On Fri, Nov 2, 2018 at 9:42 AM Mahender Shankesi <
mahender.x.shank...@gsk.com> wrote:

> Apoorv/Dev Team,
>
>
>
> We are facing challenges on install Atlas on HDinsight cluster, did anyone
> able to install it earlier on Azure HDInsight Clusters?
>
>
>
> Mahender
>
>
>
> *From:* Apoorv Naik 
> *Sent:* Wednesday, October 24, 2018 3:37 PM
> *To:* Mahender Shankesi 
> *Cc:* Shankesi Mahender ; Madhan Neethiraj <
> mad...@apache.org>; dev 
> *Subject:* Re: RE: Need Help!!! Atlas Installation Error
>
>
>
> *EXTERNAL*
>
> There are a bunch of models that get loaded during the startup process.
> typically the files will follow **_model.json *pattern.
>
>
>
> *https://github.com/apache/atlas/tree/master/addons/models
> <https://github.com/apache/atlas/tree/master/addons/models>*
>
>
>
>
>
> *Apoorv Naik*
>
>
>
>
>
> On Wed, Oct 24, 2018 at 12:22 PM Mahender Shankesi <
> mahender.x.shank...@gsk.com> wrote:
>
> Apoorv,
>
>
>
> My atlas is up and running. I tried to find a datamodel for the tables we
> loaded as quick_start.py I couldn’t find one. I saw the data is coming up
> but not sure how the backend data model works. If some one from your team
> has a data model can you please share with me.
>
>
>
> Thanks,
>
> Mahender
>
>
>
> *From:* Apoorv Naik 
> *Sent:* Friday, October 19, 2018 3:52 PM
> *To:* Mahender Shankesi ; Apoorv Naik <
> apoorvn...@apache.org>
> *Cc:* Shankesi Mahender ; Madhan Neethiraj <
> mad...@apache.org>; dev 
> *Subject:* Re: RE: Need Help!!! Atlas Installation Error
>
>
>
> *EXTERNAL*
>
> Everything should be available on atlas.apache.org if you get stuck
> please reach out to the community and mention any gaps in the documentation
> (if any).
>
>
>
>
>
> On Oct 19, 2018 at 12:48 PM,  > wrote:
>
> Apoorv,
>
>
>
> Thanks for your email.  I did installed one more time with only HBASE
> installed this time it worked and was able to view through browser. I will
> get back to you if I have any issues.
>
>
>
> Do you have any other documentation on Atlas for further study.
>
>
>
> Mahender
>
>
>
>
>
>
>
> *From:* Apoorv Naik 
> *Sent:* Friday, October 19, 2018 2:55 PM
> *To:* Mahender Shankesi 
> *Cc:* Shankesi Mahender ; Madhan Neethiraj <
> mad...@apache.org>; dev 
> *Subject:* Re: Need Help!!! Atlas Installation Error
>
>
>
> *EXTERNAL*
>
> I tried checking the classpath for duplicate netty dependency but couldn't
> find it.
>
>
>
> Can you clean your local maven repo and run the following command ? Please
> share the output if you see multiple netty JARs in the output.
>
>
>
> *mvn dependency:build-classpath -Pdist,embedded-cassandra-solr -pl webapp*
>
>
>
> On Fri, Oct 19, 2018 at 9:19 AM Mahender Shankesi <
> mahender.x.shank...@gsk.com> wrote:
>
> Apoorv,
>
>
>
> Any update on this?
>
>
>
> Mahender
>
>
>
> *From:* Apoorv Naik 
> *Sent:* Wednesday, October 17, 2018 12:11 PM
> *To:* Mahender Shankesi 
> *Cc:* Shankesi Mahender ; Madhan Neethiraj <
> mad...@apache.org>; dev 
> *Subject:* Re: Need Help!!! Atlas Installation Error
>
>
>
> *EXTERNAL*
>
> Hi Mahender,
>
>
>
> Sorry I didn't have time to investigate this. I'll try looking at it today
> or tomorrow.
>
>
>
> On Wed, Oct 17, 2018 at 6:56 AM Mahender Shankesi <
> mahender.x.shank...@gsk.com> wrote:
>
> Dev Team,
>
>
>
> Any update on this?
>
>
>
> Mahender
>
>
>
> *From:* Shankesi Mahender 
> *Sent:* Monday, October 15, 2018 9:30 AM
> *To:* apoorvn...@apache.org; Mahender Shankesi <
> mahender.x.shank...@gsk.com>
> *Cc:* Madhan Neethiraj ; dev@atlas.apache.org
> *Subject:* Re: Need Help!!! Atlas Installation Error
>
>
>
> *EXTERNAL*
>
> Apoorv/Dev Team,
>
>
>
> Any update on the below request? For tracking purpose I have created a
> JIRA ticket with Apache.
>
>
>
> https://issues.apache.org/jira/browse/ATLAS-2919
>
>
>
> Meanwhile can anyone share the Datamodel of ATLAS.
>
>
>
> Thanks & Regards,
>
> Mahender
>
>
>
>
>
>
>
>
>
>
>
> On Thu, Oct 11, 2018 at 6:44 PM Shankesi Mahender 
> wrote:
>
> Thanks Apoorv.
>
>
>
> Mahender
>
>
>
> On Thu, Oct 11, 2018 at 4:21 PM Apoorv Naik  wrote:
>
> This looks like an issue with the packaging, a wrong version of netty is
> getting pulled in. I'll try to find the source and update th

Re: Review Request 69120: Code and plugin changes to ensure correct REST docs are generated

2018-10-24 Thread Apoorv Naik


> On Oct. 22, 2018, 4:42 p.m., Madhan Neethiraj wrote:
> > webapp/src/main/java/org/apache/atlas/web/rest/TypesREST.java
> > Lines 61 (patched)
> > <https://reviews.apache.org/r/69120/diff/1/?file=2101822#file2101822line61>
> >
> > I guess this will endup adding "@Consumes(json)" to all APIs - even the 
> > ones that don't need any body. 
> > 
> > Would this cause failure if REST client doesn't specify "Content-Type: 
> > application/json"? Please verify.
> 
> Apoorv Naik wrote:
> This worked with POSTMAN and the UI didn't have any issues. Will check 
> with the Java REST Client as well.

This works with the AtlasClientV2 as well. Should be good to commit.


- Apoorv


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


On Oct. 22, 2018, 4:31 p.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69120/
> ---
> 
> (Updated Oct. 22, 2018, 4:31 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Code changes include standardizing the addition of Consumes, Produces 
> annotation to the REST class instead of each method.
> Plugin changes include upgrade and config changes to enununciate.
> 
> 
> Diffs
> -
> 
>   build-tools/src/main/resources/enunciate.xml dafd66f99 
>   pom.xml 91ec2c806 
>   webapp/src/main/java/org/apache/atlas/web/rest/DiscoveryREST.java 82d6f3594 
>   webapp/src/main/java/org/apache/atlas/web/rest/EntityREST.java 5747f9240 
>   webapp/src/main/java/org/apache/atlas/web/rest/GlossaryREST.java 8ae8f9993 
>   webapp/src/main/java/org/apache/atlas/web/rest/LineageREST.java 8b0316b4d 
>   webapp/src/main/java/org/apache/atlas/web/rest/RelationshipREST.java 
> 1014184fe 
>   webapp/src/main/java/org/apache/atlas/web/rest/TypesREST.java 2091fdf0c 
> 
> 
> Diff: https://reviews.apache.org/r/69120/diff/1/
> 
> 
> Testing
> ---
> 
> Tested locally and uploaded the latest website to apache.
> 
> 
> Thanks,
> 
> Apoorv Naik
> 
>



Re: RE: Need Help!!! Atlas Installation Error

2018-10-24 Thread Apoorv Naik
There are a bunch of models that get loaded during the startup process.
typically the files will follow **_model.json *pattern.

*https://github.com/apache/atlas/tree/master/addons/models
<https://github.com/apache/atlas/tree/master/addons/models>*


*Apoorv Naik*


On Wed, Oct 24, 2018 at 12:22 PM Mahender Shankesi <
mahender.x.shank...@gsk.com> wrote:

> Apoorv,
>
>
>
> My atlas is up and running. I tried to find a datamodel for the tables we
> loaded as quick_start.py I couldn’t find one. I saw the data is coming up
> but not sure how the backend data model works. If some one from your team
> has a data model can you please share with me.
>
>
>
> Thanks,
>
> Mahender
>
>
>
> *From:* Apoorv Naik 
> *Sent:* Friday, October 19, 2018 3:52 PM
> *To:* Mahender Shankesi ; Apoorv Naik <
> apoorvn...@apache.org>
> *Cc:* Shankesi Mahender ; Madhan Neethiraj <
> mad...@apache.org>; dev 
> *Subject:* Re: RE: Need Help!!! Atlas Installation Error
>
>
>
> *EXTERNAL*
>
> Everything should be available on atlas.apache.org if you get stuck
> please reach out to the community and mention any gaps in the documentation
> (if any).
>
>
>
>
>
> On Oct 19, 2018 at 12:48 PM,  > wrote:
>
> Apoorv,
>
>
>
> Thanks for your email.  I did installed one more time with only HBASE
> installed this time it worked and was able to view through browser. I will
> get back to you if I have any issues.
>
>
>
> Do you have any other documentation on Atlas for further study.
>
>
>
> Mahender
>
>
>
>
>
>
>
> *From:* Apoorv Naik 
> *Sent:* Friday, October 19, 2018 2:55 PM
> *To:* Mahender Shankesi 
> *Cc:* Shankesi Mahender ; Madhan Neethiraj <
> mad...@apache.org>; dev 
> *Subject:* Re: Need Help!!! Atlas Installation Error
>
>
>
> *EXTERNAL*
>
> I tried checking the classpath for duplicate netty dependency but couldn't
> find it.
>
>
>
> Can you clean your local maven repo and run the following command ? Please
> share the output if you see multiple netty JARs in the output.
>
>
>
> *mvn dependency:build-classpath -Pdist,embedded-cassandra-solr -pl webapp*
>
>
>
> On Fri, Oct 19, 2018 at 9:19 AM Mahender Shankesi <
> mahender.x.shank...@gsk.com> wrote:
>
> Apoorv,
>
>
>
> Any update on this?
>
>
>
> Mahender
>
>
>
> *From:* Apoorv Naik 
> *Sent:* Wednesday, October 17, 2018 12:11 PM
> *To:* Mahender Shankesi 
> *Cc:* Shankesi Mahender ; Madhan Neethiraj <
> mad...@apache.org>; dev 
> *Subject:* Re: Need Help!!! Atlas Installation Error
>
>
>
> *EXTERNAL*
>
> Hi Mahender,
>
>
>
> Sorry I didn't have time to investigate this. I'll try looking at it today
> or tomorrow.
>
>
>
> On Wed, Oct 17, 2018 at 6:56 AM Mahender Shankesi <
> mahender.x.shank...@gsk.com> wrote:
>
> Dev Team,
>
>
>
> Any update on this?
>
>
>
> Mahender
>
>
>
> *From:* Shankesi Mahender 
> *Sent:* Monday, October 15, 2018 9:30 AM
> *To:* apoorvn...@apache.org; Mahender Shankesi <
> mahender.x.shank...@gsk.com>
> *Cc:* Madhan Neethiraj ; dev@atlas.apache.org
> *Subject:* Re: Need Help!!! Atlas Installation Error
>
>
>
> *EXTERNAL*
>
> Apoorv/Dev Team,
>
>
>
> Any update on the below request? For tracking purpose I have created a
> JIRA ticket with Apache.
>
>
>
> https://issues.apache.org/jira/browse/ATLAS-2919
>
>
>
> Meanwhile can anyone share the Datamodel of ATLAS.
>
>
>
> Thanks & Regards,
>
> Mahender
>
>
>
>
>
>
>
>
>
>
>
> On Thu, Oct 11, 2018 at 6:44 PM Shankesi Mahender 
> wrote:
>
> Thanks Apoorv.
>
>
>
> Mahender
>
>
>
> On Thu, Oct 11, 2018 at 4:21 PM Apoorv Naik  wrote:
>
> This looks like an issue with the packaging, a wrong version of netty is
> getting pulled in. I'll try to find the source and update the thread.
>
>
>
> On Thu, Oct 11, 2018 at 1:10 PM Shankesi Mahender 
> wrote:
>
> Please find attached the application log. Did some more debugging and
> found out that starting cassandra is an issue.
>
>
>
> Any help would be greatly appreciated.
>
>
>
> I  got at one situation where I can't proceed further.
>
>
>
> Regards,
>
> Mahender
>
>
>
> On Thu, Oct 11, 2018 at 12:56 PM Shankesi Mahender 
> wrote:
>
> Madhan/Dev team,
>
>
>
> I'm able to install by changing the command  mvn clean -DskipTests package
> -Pdist,embedded-cassandra-solr
>
>
>
> I faced the same issue with executing the curl command again..
>
>

Re: Review Request 69133: ATLAS-2934: utility to detect and repair incorrect entity state

2018-10-23 Thread Apoorv Naik

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




repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityStoreV1.java
Lines 259 (patched)
<https://reviews.apache.org/r/69133/#comment294595>

Same multi-responsibility concept is being applied here. 

I feel it's better to break this down into checkState and fixState methods.



repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityStoreV1.java
Lines 866 (patched)
<https://reviews.apache.org/r/69133/#comment294593>

This method is performing two different actions. Ideally a method should 
only perform one action.

Also when I look at checkState method signature, the initial impression I 
get is that this would perform a diagnostic kind of operation, but internally 
it does some corrections as well on the basis of the boolean flag. If possible, 
please make separate methods to address these actions.



repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityStoreV1.java
Lines 872 (patched)
<https://reviews.apache.org/r/69133/#comment294594>

Can't we get the EntityGraphRetriever object using injection at class level 
?

Here for each guid a new object gets created.


- Apoorv Naik


On Oct. 24, 2018, 1:25 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69133/
> ---
> 
> (Updated Oct. 24, 2018, 1:25 a.m.)
> 
> 
> Review request for atlas, Abhishek Kadam, Apoorv Naik, Ashutosh Mestry, keval 
> bhatt, Kapildeo Nayak, Nixon Rodrigues, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2934
> https://issues.apache.org/jira/browse/ATLAS-2934
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch adds a REST API to scan specified entities for inconsistency of 
> __traitNames property value and fix it. If the property value does not match 
> the classification vertices associated with the entity, the value will be 
> updated to reflect the associated vertices.
> 
> 
> Diffs
> -
> 
>   
> intg/src/main/java/org/apache/atlas/model/instance/AtlasCheckStateRequest.java
>  PRE-CREATION 
>   
> intg/src/main/java/org/apache/atlas/model/instance/AtlasCheckStateResult.java 
> PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasEntityStore.java
>  6a1a88f4f 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityStoreV1.java
>  449a9588e 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphRetriever.java
>  0445e2798 
>   webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 
> b53ac69c4 
>   webapp/src/test/java/org/apache/atlas/web/resources/AdminResourceTest.java 
> 2f4b3d9bb 
> 
> 
> Diff: https://reviews.apache.org/r/69133/diff/1/
> 
> 
> Testing
> ---
> 
> Verified that the new API detects and fixes __traitNames property, for the 
> inconsistencies introduced. Here is a sample response from the call:
> 
> {
> "state":   "FIXED",
> "entitiesScanned":   19021,
> "entitiesFixed": 1,
> "entitiesNotFixed":  0,
> "entitiesOk":19020,
> "entitiesPartiallyFixed":0,
> "entities": {
> "e87a1236-eeb4-4474-8cfd-a82117b8d1cd": {
> "guid": "e87a1236-eeb4-4474-8cfd-a82117b8d1cd",
> "name": "testDb.testTable@myCluster",
> "state":"FIXED",
> "status":   "ACTIVE",
> "typeName": "hive_table",
> "issues": [
> "incorrect property: __traitNames has missing 
> classifications: [DATA_QUALITY]",
> "incorrect property: __traitNames has unassigned 
> classifications: [UNKNOWN_TAG2, UNKNOWN_TAG]"
> ]
> }
> }
> }
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>



[jira] [Updated] (ATLAS-2932) Update DSL to use Java Traversal API

2018-10-23 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2932:
---
Attachment: 0002-ATLAS-2932-Update-DSL-to-use-Tinkerpop-Java-APIs-ins.patch

> Update DSL to use Java Traversal API
> 
>
> Key: ATLAS-2932
> URL: https://issues.apache.org/jira/browse/ATLAS-2932
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0, trunk
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.1.0
>
> Attachments: 
> 0002-ATLAS-2932-Update-DSL-to-use-Tinkerpop-Java-APIs-ins.patch
>
>
> Change DSL code to use Java Tinkerpop Traversals instead of 
> GremlinScriptEngine



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Review Request 69131: ATLAS-2932: Update DSL to use Tinkerpop APIs instead of GremlinScriptEngine

2018-10-23 Thread Apoorv Naik

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

Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, and Sarath 
Subramanian.


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


Repository: atlas


Description
---

Updated code runs a lot faster.

Existing: 91s (best case)
Updated:  25s (best case)


Diffs
-

  
repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java 
2378d6bb3 
  repository/src/main/java/org/apache/atlas/query/AtlasDSL.java b8a744b35 
  repository/src/main/java/org/apache/atlas/query/DSLVisitor.java 700da955f 
  repository/src/main/java/org/apache/atlas/query/GremlinClauseList.java 
71179772a 
  repository/src/main/java/org/apache/atlas/query/GremlinQueryComposer.java 
17c837bb3 
  repository/src/main/java/org/apache/atlas/query/GremlinTraversal.java 
PRE-CREATION 
  repository/src/main/java/org/apache/atlas/query/IdentifierHelper.java 
e74c0f5a0 
  repository/src/main/java/org/apache/atlas/query/Lookup.java ec95f5d89 
  repository/src/main/java/org/apache/atlas/query/RegistryBasedLookup.java 
e0fb4d821 
  repository/src/main/java/org/apache/atlas/query/SelectClauseComposer.java 
999fe5c8b 
  repository/src/main/java/org/apache/atlas/query/SelectClauseMetadata.java 
PRE-CREATION 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
 f03262faa 
  
repository/src/main/java/org/apache/atlas/util/AtlasNumericTypeComparator.java 
PRE-CREATION 
  
repository/src/main/java/org/apache/atlas/util/AtlasRepositoryConfiguration.java
 bf16145a3 
  repository/src/main/java/org/apache/atlas/util/DSLProjectionUtil.java 
PRE-CREATION 
  repository/src/test/java/org/apache/atlas/query/DSLQueriesTest.java 36ec3d255 
  repository/src/test/java/org/apache/atlas/query/GremlinQueryComposerTest.java 
568667054 


Diff: https://reviews.apache.org/r/69131/diff/1/


Testing
---

Existing DSL tests run successfully.


Thanks,

Apoorv Naik



[jira] [Updated] (ATLAS-2520) Use JanusGraph traversal over gremlin script

2018-10-23 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2520:
---
Attachment: (was: 0001-DSL-using-graph-traversal.patch)

> Use JanusGraph traversal over gremlin script 
> -
>
> Key: ATLAS-2520
> URL: https://issues.apache.org/jira/browse/ATLAS-2520
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0-alpha
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.1.0
>
> Attachments: 
> 0001-ATLAS-2520-Introduce-JanusGraphTraversal-to-deprecat.patch, Screen Shot 
> 2018-06-05 at 6.16.42 PM.png, Screen Shot 2018-06-05 at 6.19.33 PM.png
>
>
> Currently lot of code in Atlas follow a concept of GremlinQueryProvider which 
> gives TP2 and TP3 queries depending on the graph backend being used. Since 
> Atlas 1.0 is primarily going to rely on JanusGraph, it makes a more sense to 
> remove TP2 related queries/abstractions and use the GraphTraversal Java API 
> provided by JanusGraph.
>  
> PRO: Lot of unused code can be removed, more expressive Graph 
> querying/traversal.
> CONS: Decommissioning TP2 completely is a major engineering effort



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-2520) Use JanusGraph traversal over gremlin script

2018-10-23 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2520:
---
Attachment: 0001-ATLAS-2520-Introduce-JanusGraphTraversal-to-deprecat.patch

> Use JanusGraph traversal over gremlin script 
> -
>
> Key: ATLAS-2520
> URL: https://issues.apache.org/jira/browse/ATLAS-2520
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0-alpha
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.1.0
>
> Attachments: 
> 0001-ATLAS-2520-Introduce-JanusGraphTraversal-to-deprecat.patch, Screen Shot 
> 2018-06-05 at 6.16.42 PM.png, Screen Shot 2018-06-05 at 6.19.33 PM.png
>
>
> Currently lot of code in Atlas follow a concept of GremlinQueryProvider which 
> gives TP2 and TP3 queries depending on the graph backend being used. Since 
> Atlas 1.0 is primarily going to rely on JanusGraph, it makes a more sense to 
> remove TP2 related queries/abstractions and use the GraphTraversal Java API 
> provided by JanusGraph.
>  
> PRO: Lot of unused code can be removed, more expressive Graph 
> querying/traversal.
> CONS: Decommissioning TP2 completely is a major engineering effort



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ATLAS-2932) Update DSL to use Java Traversal API

2018-10-23 Thread Apoorv Naik (JIRA)
Apoorv Naik created ATLAS-2932:
--

 Summary: Update DSL to use Java Traversal API
 Key: ATLAS-2932
 URL: https://issues.apache.org/jira/browse/ATLAS-2932
 Project: Atlas
  Issue Type: Bug
Affects Versions: 1.0.0, trunk
Reporter: Apoorv Naik
Assignee: Apoorv Naik
 Fix For: 1.1.0


Change DSL code to use Java Tinkerpop Traversals instead of GremlinScriptEngine



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Review Request 69120: Code and plugin changes to ensure correct REST docs are generated

2018-10-22 Thread Apoorv Naik


> On Oct. 22, 2018, 4:42 p.m., Madhan Neethiraj wrote:
> > webapp/src/main/java/org/apache/atlas/web/rest/TypesREST.java
> > Lines 61 (patched)
> > <https://reviews.apache.org/r/69120/diff/1/?file=2101822#file2101822line61>
> >
> > I guess this will endup adding "@Consumes(json)" to all APIs - even the 
> > ones that don't need any body. 
> > 
> > Would this cause failure if REST client doesn't specify "Content-Type: 
> > application/json"? Please verify.

This worked with POSTMAN and the UI didn't have any issues. Will check with the 
Java REST Client as well.


- Apoorv


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


On Oct. 22, 2018, 4:31 p.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69120/
> ---
> 
> (Updated Oct. 22, 2018, 4:31 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Nixon Rodrigues, 
> and Sarath Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Code changes include standardizing the addition of Consumes, Produces 
> annotation to the REST class instead of each method.
> Plugin changes include upgrade and config changes to enununciate.
> 
> 
> Diffs
> -
> 
>   build-tools/src/main/resources/enunciate.xml dafd66f99 
>   pom.xml 91ec2c806 
>   webapp/src/main/java/org/apache/atlas/web/rest/DiscoveryREST.java 82d6f3594 
>   webapp/src/main/java/org/apache/atlas/web/rest/EntityREST.java 5747f9240 
>   webapp/src/main/java/org/apache/atlas/web/rest/GlossaryREST.java 8ae8f9993 
>   webapp/src/main/java/org/apache/atlas/web/rest/LineageREST.java 8b0316b4d 
>   webapp/src/main/java/org/apache/atlas/web/rest/RelationshipREST.java 
> 1014184fe 
>   webapp/src/main/java/org/apache/atlas/web/rest/TypesREST.java 2091fdf0c 
> 
> 
> Diff: https://reviews.apache.org/r/69120/diff/1/
> 
> 
> Testing
> ---
> 
> Tested locally and uploaded the latest website to apache.
> 
> 
> Thanks,
> 
> Apoorv Naik
> 
>



Review Request 69120: Code and plugin changes to ensure correct REST docs are generated

2018-10-22 Thread Apoorv Naik

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

Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Nixon Rodrigues, 
and Sarath Subramanian.


Repository: atlas


Description
---

Code changes include standardizing the addition of Consumes, Produces 
annotation to the REST class instead of each method.
Plugin changes include upgrade and config changes to enununciate.


Diffs
-

  build-tools/src/main/resources/enunciate.xml dafd66f99 
  pom.xml 91ec2c806 
  webapp/src/main/java/org/apache/atlas/web/rest/DiscoveryREST.java 82d6f3594 
  webapp/src/main/java/org/apache/atlas/web/rest/EntityREST.java 5747f9240 
  webapp/src/main/java/org/apache/atlas/web/rest/GlossaryREST.java 8ae8f9993 
  webapp/src/main/java/org/apache/atlas/web/rest/LineageREST.java 8b0316b4d 
  webapp/src/main/java/org/apache/atlas/web/rest/RelationshipREST.java 
1014184fe 
  webapp/src/main/java/org/apache/atlas/web/rest/TypesREST.java 2091fdf0c 


Diff: https://reviews.apache.org/r/69120/diff/1/


Testing
---

Tested locally and uploaded the latest website to apache.


Thanks,

Apoorv Naik



[jira] [Resolved] (ATLAS-2929) Fix netty issues when running with embedded Cassandra

2018-10-21 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-2929.

Resolution: Fixed

> Fix netty issues when running with embedded Cassandra
> -
>
> Key: ATLAS-2929
> URL: https://issues.apache.org/jira/browse/ATLAS-2929
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.1.0, 2.0.0
>
>
> This is resolved by pull request # 13 on Github



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (ATLAS-2929) Fix netty issues when running with embedded Cassandra

2018-10-21 Thread Apoorv Naik (JIRA)


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

Apoorv Naik commented on ATLAS-2929:


Fixes ATLAS-2919

> Fix netty issues when running with embedded Cassandra
> -
>
> Key: ATLAS-2929
> URL: https://issues.apache.org/jira/browse/ATLAS-2929
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.1.0, 2.0.0
>
>
> This is resolved by pull request # 13 on Github



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ATLAS-2929) Fix netty issues when running with embedded Cassandra

2018-10-21 Thread Apoorv Naik (JIRA)
Apoorv Naik created ATLAS-2929:
--

 Summary: Fix netty issues when running with embedded Cassandra
 Key: ATLAS-2929
 URL: https://issues.apache.org/jira/browse/ATLAS-2929
 Project: Atlas
  Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Apoorv Naik
Assignee: Apoorv Naik
 Fix For: 1.1.0, 2.0.0


This is resolved by pull request # 13 on Github



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [VOTE] Release Apache Atlas v 0.8.3 - RC0

2018-10-20 Thread Apoorv Naik
+1 for the release Ashutosh.

1. Verified signature
2. Built with embedded hbase and solr profile
3. Basic search and DSL works as expected

Thanks for putting in the effort towards this release.

*Apoorv Naik*


On Sat, Oct 20, 2018 at 11:35 AM Sarath Subramanian 
wrote:

> Thanks Ashutosh for putting together release candidate #0 for Apache Atlas
> 0.8.3
>
> Verified the following:
>
>- Verified PGP Signature and hash
>- Build the source using embedded HBase and Solr profile, build was
>successful
>- Ran quick start and validated basic functionality - basic search,
>import-export, advanced search.
>
> +1 for release of Apache Atlas 0.8.3 rc0
>
> Thanks,
> Sarath
>
> On Wed, Oct 17, 2018 at 4:14 PM Ashutosh Mestry 
> wrote:
>
> > Apache Atlas 0.8.3 Release Candidate #0 is now available for a vote
> within
> > dev community.
> >
> > Links to the release artifacts are given below. 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)
> >
> > Ashutosh Mestry
> >
> > List of issues addressed in this release:
> >
> https://issues.apache.org/jira/browse/ATLAS-2924?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.8.3%20ORDER%20BY%20key%20DESC
> >
> > Git tag for the release:
> > https://github.com/apache/atlas/tree/release-0.8.3-rc0
> >
> > Sources for the release:
> >
> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz
> >
> > Source release verification:
> > PGP Signature:
> >
> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz.asc
> > SHA512
> > <
> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz.ascSHA512
> >
> > Hash:
> >
> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz.sha512
> >
> > Keys to verify the signature of the release artifacts are available at:
> > https://dist.apache.org/repos/dist/dev/atlas/KEYS
> >
> >
> >
>


Re: RE: Need Help!!! Atlas Installation Error

2018-10-19 Thread Apoorv Naik
Everything should be available on atlas.apache.org if you get stuck please
reach out to the community and mention any gaps in the documentation (if
any).



On Oct 19, 2018 at 12:48 PM, > wrote:

Apoorv,



Thanks for your email.  I did installed one more time with only HBASE
installed this time it worked and was able to view through browser. I will
get back to you if I have any issues.



Do you have any other documentation on Atlas for further study.



Mahender







*From:* Apoorv Naik 
*Sent:* Friday, October 19, 2018 2:55 PM
*To:* Mahender Shankesi 
*Cc:* Shankesi Mahender ; Madhan Neethiraj <
mad...@apache.org>; dev 
*Subject:* Re: Need Help!!! Atlas Installation Error



*EXTERNAL*

I tried checking the classpath for duplicate netty dependency but couldn't
find it.



Can you clean your local maven repo and run the following command ? Please
share the output if you see multiple netty JARs in the output.



*mvn dependency:build-classpath -Pdist,embedded-cassandra-solr -pl webapp*



On Fri, Oct 19, 2018 at 9:19 AM Mahender Shankesi <
mahender.x.shank...@gsk.com> wrote:

Apoorv,



Any update on this?



Mahender



*From:* Apoorv Naik 
*Sent:* Wednesday, October 17, 2018 12:11 PM
*To:* Mahender Shankesi 
*Cc:* Shankesi Mahender ; Madhan Neethiraj <
mad...@apache.org>; dev 
*Subject:* Re: Need Help!!! Atlas Installation Error



*EXTERNAL*

Hi Mahender,



Sorry I didn't have time to investigate this. I'll try looking at it today
or tomorrow.



On Wed, Oct 17, 2018 at 6:56 AM Mahender Shankesi <
mahender.x.shank...@gsk.com> wrote:

Dev Team,



Any update on this?



Mahender



*From:* Shankesi Mahender 
*Sent:* Monday, October 15, 2018 9:30 AM
*To:* apoorvn...@apache.org; Mahender Shankesi 
*Cc:* Madhan Neethiraj ; dev@atlas.apache.org
*Subject:* Re: Need Help!!! Atlas Installation Error



*EXTERNAL*

Apoorv/Dev Team,



Any update on the below request? For tracking purpose I have created a JIRA
ticket with Apache.



https://issues.apache.org/jira/browse/ATLAS-2919



Meanwhile can anyone share the Datamodel of ATLAS.



Thanks & Regards,

Mahender











On Thu, Oct 11, 2018 at 6:44 PM Shankesi Mahender 
wrote:

Thanks Apoorv.



Mahender



On Thu, Oct 11, 2018 at 4:21 PM Apoorv Naik  wrote:

This looks like an issue with the packaging, a wrong version of netty is
getting pulled in. I'll try to find the source and update the thread.



On Thu, Oct 11, 2018 at 1:10 PM Shankesi Mahender 
wrote:

Please find attached the application log. Did some more debugging and found
out that starting cassandra is an issue.



Any help would be greatly appreciated.



I  got at one situation where I can't proceed further.



Regards,

Mahender



On Thu, Oct 11, 2018 at 12:56 PM Shankesi Mahender 
wrote:

Madhan/Dev team,



I'm able to install by changing the command  mvn clean -DskipTests package
-Pdist,embedded-cassandra-solr



I faced the same issue with executing the curl command again..



$

curl -u admin:admin http://myip:21000/api/atlas/admin/version
<http://10.41.64.19:21000/api/atlas/admin/version>

curl: (7) Failed to connect to myip port 21000: Connection refused

$

curl -u admin:admin https://myip/api/atlas/admin/version
<https://10.41.64.19:21443/api/atlas/admin/version>

curl: (7) Failed to connect to myip port 21443: Connection refused



I went to atlas_config.py and change the DEFAULT_ATLAS_SERVER_HOST to my
ip. None of them seems to be working.



$ netstat -a | grep 21000

netstat -a | grep 21443



Didn't return anything.



Do I need to do anything extra which is not documented in the instructions?



Thanks for your help.



Mahender



On Wed, Oct 10, 2018 at 11:54 PM Shankesi Mahender 
wrote:

Dev team,



I'm able to install when I changed the command like below.



mvn clean -DskipTests package -Pdist,embedded-cassandra-solr.



After that when I started apache server I'm getting the below error.



 File "atlas_start.py", line 107

print "Cannot run setup when server is running."

   ^

SyntaxError: Missing parentheses in call to 'print'



I tried to stop the server if it is already started but I got the same kind
of error.



File "atlas_stop.py", line 63

print "Apache Atlas Server stopped!!!\n"

   ^

SyntaxError: Missing parentheses in call to 'print'



Can  anyone help me on this?



Thanks,

Mahender







On Wed, Oct 10, 2018 at 4:23 PM Mahender Shankesi 
wrote:

I changed it but still not working.



Mahender

Sent from my iPhone


On Oct 10, 2018, at 4:03 PM, Madhan Neethiraj  wrote:

(copying dev list)



Mahender – the port # to use is “21000”; the curl commands you listed show
“2100”. Please try after correcting this.



@Pierre – perhaps you can help with the question on Cassandra?



Madhan





*From: *Shankesi Mahender 
*Date: *Wednesday, October 10, 2018 at 12:37 PM
*To: *

Re: Need Help!!! Atlas Installation Error

2018-10-19 Thread Apoorv Naik
I tried checking the classpath for duplicate netty dependency but couldn't
find it.

Can you clean your local maven repo and run the following command ? Please
share the output if you see multiple netty JARs in the output.

*mvn dependency:build-classpath -Pdist,embedded-cassandra-solr -pl webapp*


On Fri, Oct 19, 2018 at 9:19 AM Mahender Shankesi <
mahender.x.shank...@gsk.com> wrote:

> Apoorv,
>
>
>
> Any update on this?
>
>
>
> Mahender
>
>
>
> *From:* Apoorv Naik 
> *Sent:* Wednesday, October 17, 2018 12:11 PM
> *To:* Mahender Shankesi 
> *Cc:* Shankesi Mahender ; Madhan Neethiraj <
> mad...@apache.org>; dev 
> *Subject:* Re: Need Help!!! Atlas Installation Error
>
>
>
> *EXTERNAL*
>
> Hi Mahender,
>
>
>
> Sorry I didn't have time to investigate this. I'll try looking at it today
> or tomorrow.
>
>
>
> On Wed, Oct 17, 2018 at 6:56 AM Mahender Shankesi <
> mahender.x.shank...@gsk.com> wrote:
>
> Dev Team,
>
>
>
> Any update on this?
>
>
>
> Mahender
>
>
>
> *From:* Shankesi Mahender 
> *Sent:* Monday, October 15, 2018 9:30 AM
> *To:* apoorvn...@apache.org; Mahender Shankesi <
> mahender.x.shank...@gsk.com>
> *Cc:* Madhan Neethiraj ; dev@atlas.apache.org
> *Subject:* Re: Need Help!!! Atlas Installation Error
>
>
>
> *EXTERNAL*
>
> Apoorv/Dev Team,
>
>
>
> Any update on the below request? For tracking purpose I have created a
> JIRA ticket with Apache.
>
>
>
> https://issues.apache.org/jira/browse/ATLAS-2919
>
>
>
> Meanwhile can anyone share the Datamodel of ATLAS.
>
>
>
> Thanks & Regards,
>
> Mahender
>
>
>
>
>
>
>
>
>
>
>
> On Thu, Oct 11, 2018 at 6:44 PM Shankesi Mahender 
> wrote:
>
> Thanks Apoorv.
>
>
>
> Mahender
>
>
>
> On Thu, Oct 11, 2018 at 4:21 PM Apoorv Naik  wrote:
>
> This looks like an issue with the packaging, a wrong version of netty is
> getting pulled in. I'll try to find the source and update the thread.
>
>
>
> On Thu, Oct 11, 2018 at 1:10 PM Shankesi Mahender 
> wrote:
>
> Please find attached the application log. Did some more debugging and
> found out that starting cassandra is an issue.
>
>
>
> Any help would be greatly appreciated.
>
>
>
> I  got at one situation where I can't proceed further.
>
>
>
> Regards,
>
> Mahender
>
>
>
> On Thu, Oct 11, 2018 at 12:56 PM Shankesi Mahender 
> wrote:
>
> Madhan/Dev team,
>
>
>
> I'm able to install by changing the command  mvn clean -DskipTests package
> -Pdist,embedded-cassandra-solr
>
>
>
> I faced the same issue with executing the curl command again..
>
>
>
> $
> 
> curl -u admin:admin http://myip:21000/api/atlas/admin/version
> <http://10.41.64.19:21000/api/atlas/admin/version>
>
> curl: (7) Failed to connect to myip port 21000: Connection refused
>
> $
> 
> curl -u admin:admin https://myip/api/atlas/admin/version
> <https://10.41.64.19:21443/api/atlas/admin/version>
>
> curl: (7) Failed to connect to myip port 21443: Connection refused
>
>
>
> I went to atlas_config.py and change the DEFAULT_ATLAS_SERVER_HOST to my
> ip. None of them seems to be working.
>
>
>
> $ netstat -a | grep 21000
>
> netstat -a | grep 21443
>
>
>
> Didn't return anything.
>
>
>
> Do I need to do anything extra which is not documented in the instructions?
>
>
>
> Thanks for your help.
>
>
>
> Mahender
>
>
>
> On Wed, Oct 10, 2018 at 11:54 PM Shankesi Mahender 
> wrote:
>
> Dev team,
>
>
>
> I'm able to install when I changed the command like below.
>
>
>
> mvn clean -DskipTests package -Pdist,embedded-cassandra-solr.
>
>
>
> After that when I started apache server I'm getting the below error.
>
>
>
>  File "atlas_start.py", line 107
>
> print "Cannot run setup when server is running."
>
>^
>
> SyntaxError: Missing parentheses in call to 'print'
>
>
>
> I tried to stop the server if it is already started but I got the same
> kind of error.
>
>
>
> File "atlas_stop.py", line 63
>
> print "Apache Atlas Server stopped!!!\n"
>
>^
>
> SyntaxError: Missing parentheses in call to 'print'
>
>
>
> Can  anyone help me on this?
>
>
>
> Thanks,
>
> Mahender
>
>
>
>
>
>
>
> On Wed, Oct 10, 2018 at 4:23 PM Mahender Shankesi 
> wrote:
>
> I changed it but

Re: Need Help!!! Atlas Installation Error

2018-10-17 Thread Apoorv Naik
Hi Mahender,

Sorry I didn't have time to investigate this. I'll try looking at it today
or tomorrow.

On Wed, Oct 17, 2018 at 6:56 AM Mahender Shankesi <
mahender.x.shank...@gsk.com> wrote:

> Dev Team,
>
>
>
> Any update on this?
>
>
>
> Mahender
>
>
>
> *From:* Shankesi Mahender 
> *Sent:* Monday, October 15, 2018 9:30 AM
> *To:* apoorvn...@apache.org; Mahender Shankesi <
> mahender.x.shank...@gsk.com>
> *Cc:* Madhan Neethiraj ; dev@atlas.apache.org
> *Subject:* Re: Need Help!!! Atlas Installation Error
>
>
>
> *EXTERNAL*
>
> Apoorv/Dev Team,
>
>
>
> Any update on the below request? For tracking purpose I have created a
> JIRA ticket with Apache.
>
>
>
> https://issues.apache.org/jira/browse/ATLAS-2919
>
>
>
> Meanwhile can anyone share the Datamodel of ATLAS.
>
>
>
> Thanks & Regards,
>
> Mahender
>
>
>
>
>
>
>
>
>
>
>
> On Thu, Oct 11, 2018 at 6:44 PM Shankesi Mahender 
> wrote:
>
> Thanks Apoorv.
>
>
>
> Mahender
>
>
>
> On Thu, Oct 11, 2018 at 4:21 PM Apoorv Naik  wrote:
>
> This looks like an issue with the packaging, a wrong version of netty is
> getting pulled in. I'll try to find the source and update the thread.
>
>
>
> On Thu, Oct 11, 2018 at 1:10 PM Shankesi Mahender 
> wrote:
>
> Please find attached the application log. Did some more debugging and
> found out that starting cassandra is an issue.
>
>
>
> Any help would be greatly appreciated.
>
>
>
> I  got at one situation where I can't proceed further.
>
>
>
> Regards,
>
> Mahender
>
>
>
> On Thu, Oct 11, 2018 at 12:56 PM Shankesi Mahender 
> wrote:
>
> Madhan/Dev team,
>
>
>
> I'm able to install by changing the command  mvn clean -DskipTests package
> -Pdist,embedded-cassandra-solr
>
>
>
> I faced the same issue with executing the curl command again..
>
>
>
> $
> 
> curl -u admin:admin http://myip:21000/api/atlas/admin/version
> <http://10.41.64.19:21000/api/atlas/admin/version>
>
> curl: (7) Failed to connect to myip port 21000: Connection refused
>
> $
> 
> curl -u admin:admin https://myip/api/atlas/admin/version
> <https://10.41.64.19:21443/api/atlas/admin/version>
>
> curl: (7) Failed to connect to myip port 21443: Connection refused
>
>
>
> I went to atlas_config.py and change the DEFAULT_ATLAS_SERVER_HOST to my
> ip. None of them seems to be working.
>
>
>
> $ netstat -a | grep 21000
>
> netstat -a | grep 21443
>
>
>
> Didn't return anything.
>
>
>
> Do I need to do anything extra which is not documented in the instructions?
>
>
>
> Thanks for your help.
>
>
>
> Mahender
>
>
>
> On Wed, Oct 10, 2018 at 11:54 PM Shankesi Mahender 
> wrote:
>
> Dev team,
>
>
>
> I'm able to install when I changed the command like below.
>
>
>
> mvn clean -DskipTests package -Pdist,embedded-cassandra-solr.
>
>
>
> After that when I started apache server I'm getting the below error.
>
>
>
>  File "atlas_start.py", line 107
>
> print "Cannot run setup when server is running."
>
>^
>
> SyntaxError: Missing parentheses in call to 'print'
>
>
>
> I tried to stop the server if it is already started but I got the same
> kind of error.
>
>
>
> File "atlas_stop.py", line 63
>
> print "Apache Atlas Server stopped!!!\n"
>
>^
>
> SyntaxError: Missing parentheses in call to 'print'
>
>
>
> Can  anyone help me on this?
>
>
>
> Thanks,
>
> Mahender
>
>
>
>
>
>
>
> On Wed, Oct 10, 2018 at 4:23 PM Mahender Shankesi 
> wrote:
>
> I changed it but still not working.
>
>
>
> Mahender
>
> Sent from my iPhone
>
>
> On Oct 10, 2018, at 4:03 PM, Madhan Neethiraj  wrote:
>
> (copying dev list)
>
>
>
> Mahender – the port # to use is “21000”; the curl commands you listed show
> “2100”. Please try after correcting this.
>
>
>
> @Pierre – perhaps you can help with the question on Cassandra?
>
>
>
> Madhan
>
>
>
>
>
> *From: *Shankesi Mahender 
> *Date: *Wednesday, October 10, 2018 at 12:37 PM
> *To: *"mad...@apache.org" 
> *Subject: *Re: Need Help!!! Atlas Installation Error
>
>
>
> Madhan,
>
>
>
> I followed the instructions in the below site..
>
>
>
> 

[jira] [Commented] (ATLAS-2924) Use encoded property name in getEncodedProperty() and setEncodedProperty() methods

2018-10-16 Thread Apoorv Naik (JIRA)


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

Apoorv Naik commented on ATLAS-2924:


+1 Changes look good.

> Use encoded property name in getEncodedProperty() and setEncodedProperty() 
> methods
> --
>
> Key: ATLAS-2924
> URL: https://issues.apache.org/jira/browse/ATLAS-2924
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Affects Versions: 0.8.2, 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: trunk, 0.8.3, 1.1.0
>
> Attachments: 
> 0001-ATLAS-2924-Use-encoded-property-name-in-getEncodedPr-branch-0.8.patch, 
> 0001-ATLAS-2924-Use-encoded-property-name-in-getEncodedPr-master.patch
>
>
> Use encoded property name in all access to getEncodedProperty() and 
> setEncodedProperty() methods



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Need Help!!! Atlas Installation Error

2018-10-11 Thread Apoorv Naik
This looks like an issue with the packaging, a wrong version of netty is
getting pulled in. I'll try to find the source and update the thread.

On Thu, Oct 11, 2018 at 1:10 PM Shankesi Mahender 
wrote:

> Please find attached the application log. Did some more debugging and
> found out that starting cassandra is an issue.
>
> Any help would be greatly appreciated.
>
> I  got at one situation where I can't proceed further.
>
> Regards,
> Mahender
>
> On Thu, Oct 11, 2018 at 12:56 PM Shankesi Mahender 
> wrote:
>
>> Madhan/Dev team,
>>
>> I'm able to install by changing the command  mvn clean -DskipTests
>> package -Pdist,embedded-cassandra-solr
>>
>> I faced the same issue with executing the curl command again..
>>
>> $
>> 
>> curl -u admin:admin http://myip:21000/api/atlas/admin/version
>> 
>>
>> curl: (7) Failed to connect to myip port 21000: Connection refused
>>
>> $
>> 
>> curl -u admin:admin https://myip/api/atlas/admin/version
>> 
>>
>> curl: (7) Failed to connect to myip port 21443: Connection refused
>>
>>
>> I went to atlas_config.py and change the DEFAULT_ATLAS_SERVER_HOST to my
>> ip. None of them seems to be working.
>>
>>
>>
>> $ netstat -a | grep 21000
>>
>> netstat -a | grep 21443
>>
>>
>> Didn't return anything.
>>
>> Do I need to do anything extra which is not documented in the
>> instructions?
>>
>> Thanks for your help.
>>
>> Mahender
>>
>> On Wed, Oct 10, 2018 at 11:54 PM Shankesi Mahender 
>> wrote:
>>
>>> Dev team,
>>>
>>> I'm able to install when I changed the command like below.
>>>
>>> mvn clean -DskipTests package -Pdist,embedded-cassandra-solr.
>>>
>>> After that when I started apache server I'm getting the below error.
>>>
>>>  File "atlas_start.py", line 107
>>> print "Cannot run setup when server is running."
>>>^
>>> SyntaxError: Missing parentheses in call to 'print'
>>>
>>> I tried to stop the server if it is already started but I got the same
>>> kind of error.
>>>
>>> File "atlas_stop.py", line 63
>>> print "Apache Atlas Server stopped!!!\n"
>>>^
>>> SyntaxError: Missing parentheses in call to 'print'
>>>
>>> Can  anyone help me on this?
>>>
>>> Thanks,
>>> Mahender
>>>
>>>
>>>
>>> On Wed, Oct 10, 2018 at 4:23 PM Mahender Shankesi 
>>> wrote:
>>>
 I changed it but still not working.

 Mahender

 Sent from my iPhone

 On Oct 10, 2018, at 4:03 PM, Madhan Neethiraj 
 wrote:

 (copying dev list)



 Mahender – the port # to use is “21000”; the curl commands you listed
 show “2100”. Please try after correcting this.



 @Pierre – perhaps you can help with the question on Cassandra?



 Madhan





 *From: *Shankesi Mahender 
 *Date: *Wednesday, October 10, 2018 at 12:37 PM
 *To: *"mad...@apache.org" 
 *Subject: *Re: Need Help!!! Atlas Installation Error



 Madhan,



 I followed the instructions in the below site..



 https://atlas.apache.org/InstallationSteps.html



 I did it in two machines one Azure VM and one Azure Hdinisights.



 Hdinsights I'm able to install all steps correctly and run apache_start
 properly. However I'm not able to run the curl command..



 sshuser@XXX:~/xyz/apache-atlas-sources-1.1.0/distro/target/apache-atlas-1.1.0/bin$
 curl -u admin:admin
 https://xxx.azurehdinsight.net:2100/api/atlas/admin/version

 ^C

 sshuser@xxx:~/xxx/apache-atlas-sources-1.1.0/distro/target/apache-atlas-1.1.0/bin$
 curl -u admin:admin https://localhost:2100/api/atlas/admin/version

 curl: (7) Failed to connect to localhost port 2100: Connection refused





 However I'm facing challenges in install the steps in VM..



 mvn clean package -Pdist,embedded-cassandra-solr



 I'm getting the below error and it is hanging there..




 pache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)

 at
 org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)

 at
 org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)

 at
 org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)

 at
 org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)

 at
 org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)

 at
 

Re: Need Help!!! Atlas Installation Error

2018-10-11 Thread Apoorv Naik
Do you see a application.log file somewhere? If yes, please share the same.
Did you get past the python issue ?


On Oct 11, 2018 at 11:01 AM, >
wrote:

Madhan/Dev team,

I'm able to install by changing the command  mvn clean -DskipTests package
-Pdist,embedded-cassandra-solr

I faced the same issue with executing the curl command again..

$

curl -u admin:admin http://myip:21000/api/atlas/admin/version


curl: (7) Failed to connect to myip port 21000: Connection refused

$

curl -u admin:admin https://myip/api/atlas/admin/version


curl: (7) Failed to connect to myip port 21443: Connection refused


I went to atlas_config.py and change the DEFAULT_ATLAS_SERVER_HOST to my
ip. None of them seems to be working.



$ netstat -a | grep 21000

netstat -a | grep 21443


Didn't return anything.

Do I need to do anything extra which is not documented in the instructions?

Thanks for your help.

Mahender

On Wed, Oct 10, 2018 at 11:54 PM Shankesi Mahender 
wrote:

> Dev team,
>
> I'm able to install when I changed the command like below.
>
> mvn clean -DskipTests package -Pdist,embedded-cassandra-solr.
>
> After that when I started apache server I'm getting the below error.
>
>  File "atlas_start.py", line 107
> print "Cannot run setup when server is running."
>^
> SyntaxError: Missing parentheses in call to 'print'
>
> I tried to stop the server if it is already started but I got the same
> kind of error.
>
> File "atlas_stop.py", line 63
> print "Apache Atlas Server stopped!!!\n"
>^
> SyntaxError: Missing parentheses in call to 'print'
>
> Can  anyone help me on this?
>
> Thanks,
> Mahender
>
>
>
> On Wed, Oct 10, 2018 at 4:23 PM Mahender Shankesi 
> wrote:
>
>> I changed it but still not working.
>>
>> Mahender
>>
>> Sent from my iPhone
>>
>> On Oct 10, 2018, at 4:03 PM, Madhan Neethiraj  wrote:
>>
>> (copying dev list)
>>
>>
>>
>> Mahender – the port # to use is “21000”; the curl commands you listed
>> show “2100”. Please try after correcting this.
>>
>>
>>
>> @Pierre – perhaps you can help with the question on Cassandra?
>>
>>
>>
>> Madhan
>>
>>
>>
>>
>>
>> *From: *Shankesi Mahender 
>> *Date: *Wednesday, October 10, 2018 at 12:37 PM
>> *To: *"mad...@apache.org" 
>> *Subject: *Re: Need Help!!! Atlas Installation Error
>>
>>
>>
>> Madhan,
>>
>>
>>
>> I followed the instructions in the below site..
>>
>>
>>
>> https://atlas.apache.org/InstallationSteps.html
>>
>>
>>
>> I did it in two machines one Azure VM and one Azure Hdinisights.
>>
>>
>>
>> Hdinsights I'm able to install all steps correctly and run apache_start
>> properly. However I'm not able to run the curl command..
>>
>>
>>
>> sshuser@XXX:~/xyz/apache-atlas-sources-1.1.0/distro/target/apache-atlas-1.1.0/bin$
>> curl -u admin:admin
>> https://xxx.azurehdinsight.net:2100/api/atlas/admin/version
>>
>> ^C
>>
>> sshuser@xxx:~/xxx/apache-atlas-sources-1.1.0/distro/target/apache-atlas-1.1.0/bin$
>> curl -u admin:admin https://localhost:2100/api/atlas/admin/version
>>
>> curl: (7) Failed to connect to localhost port 2100: Connection refused
>>
>>
>>
>>
>>
>> However I'm facing challenges in install the steps in VM..
>>
>>
>>
>> mvn clean package -Pdist,embedded-cassandra-solr
>>
>>
>>
>> I'm getting the below error and it is hanging there..
>>
>>
>>
>>
>> pache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)
>>
>> at
>> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)
>>
>> at
>> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)
>>
>> at
>> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)
>>
>> at
>> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)
>>
>> at
>> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)
>>
>> at
>> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)
>>
>> at
>> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)
>>
>> at
>> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)
>>
>> at
>> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)
>>
>>
>>
>>
>>
>> Any help is greatly appreciated..
>>
>>
>>
>>
>>
>> Mahender
>>
>> at org.a
>>
>>
>>
>> On Tue, Oct 9, 2018 at 3:09 PM Madhan Neethiraj 
>> wrote:
>>
>> Mahender,
>>
>>
>>
>> “port 80”? Atlas should be listening in port 21000 by default. Which URL
>> are you getting this error for?
>>
>>
>>
>> Thanks,
>>
>> Madhan
>>
>>
>>
>>

Re: Need Help!!! Atlas Installation Error

2018-10-10 Thread Apoorv Naik
Python version mismatch. I think you're using Python3 and the current atlas 
scripts are Python 2 specific.

On 10/10/18, 8:57 PM, "Shankesi Mahender"  wrote:

Dev team,

I'm able to install when I changed the command like below.

mvn clean -DskipTests package -Pdist,embedded-cassandra-solr.

After that when I started apache server I'm getting the below error.

 File "atlas_start.py", line 107
print "Cannot run setup when server is running."
   ^
SyntaxError: Missing parentheses in call to 'print'

I tried to stop the server if it is already started but I got the same kind
of error.

File "atlas_stop.py", line 63
print "Apache Atlas Server stopped!!!\n"
   ^
SyntaxError: Missing parentheses in call to 'print'

Can  anyone help me on this?

Thanks,
Mahender



On Wed, Oct 10, 2018 at 4:23 PM Mahender Shankesi 
wrote:

> I changed it but still not working.
>
> Mahender
>
> Sent from my iPhone
>
> On Oct 10, 2018, at 4:03 PM, Madhan Neethiraj  wrote:
>
> (copying dev list)
>
>
>
> Mahender – the port # to use is “21000”; the curl commands you listed show
> “2100”. Please try after correcting this.
>
>
>
> @Pierre – perhaps you can help with the question on Cassandra?
>
>
>
> Madhan
>
>
>
>
>
> *From: *Shankesi Mahender 
> *Date: *Wednesday, October 10, 2018 at 12:37 PM
> *To: *"mad...@apache.org" 
> *Subject: *Re: Need Help!!! Atlas Installation Error
>
>
>
> Madhan,
>
>
>
> I followed the instructions in the below site..
>
>
>
> https://atlas.apache.org/InstallationSteps.html
>
>
>
> I did it in two machines one Azure VM and one Azure Hdinisights.
>
>
>
> Hdinsights I'm able to install all steps correctly and run apache_start
> properly. However I'm not able to run the curl command..
>
>
>
> 
sshuser@XXX:~/xyz/apache-atlas-sources-1.1.0/distro/target/apache-atlas-1.1.0/bin$
> curl -u admin:admin
> https://xxx.azurehdinsight.net:2100/api/atlas/admin/version
>
> ^C
>
> 
sshuser@xxx:~/xxx/apache-atlas-sources-1.1.0/distro/target/apache-atlas-1.1.0/bin$
> curl -u admin:admin https://localhost:2100/api/atlas/admin/version
>
> curl: (7) Failed to connect to localhost port 2100: Connection refused
>
>
>
>
>
> However I'm facing challenges in install the steps in VM..
>
>
>
> mvn clean package -Pdist,embedded-cassandra-solr
>
>
>
> I'm getting the below error and it is hanging there..
>
>
>
>
> 
pache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)
>
> at
> 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)
>
> at
> 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)
>
> at
> 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)
>
> at
> 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)
>
> at
> 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)
>
> at
> 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)
>
> at
> 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)
>
> at
> 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)
>
> at
> 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)
>
>
>
>
>
> Any help is greatly appreciated..
>
>
>
>
>
> Mahender
>
> at org.a
>
>
>
> On Tue, Oct 9, 2018 at 3:09 PM Madhan Neethiraj  wrote:
>
> Mahender,
>
>
>
> “port 80”? Atlas should be listening in port 21000 by default. Which URL
> are you getting this error for?
>
>
>
> Thanks,
>
> Madhan
>
>
>
>
>
>
>
>
>
> *From: *Shankesi Mahender 
> *Date: *Tuesday, October 9, 2018 at 11:56 AM
> *To: *"mad...@apache.org" 
> *Subject: *Re: Need Help!!! Atlas Installation Error
>
>
>
> Thanks Madhan..
>
>
>
> When I tried to run the curl command with admin:admin I got below error.
>
>
>
> curl: (7) Failed to 

[jira] [Resolved] (ATLAS-1553) Property loading framework

2018-10-10 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-1553.

Resolution: Won't Do

> Property loading framework
> --
>
> Key: ATLAS-1553
> URL: https://issues.apache.org/jira/browse/ATLAS-1553
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8-incubating
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
>
> I see that atlas has multiple ways of loading properties/configuration, I 
> think it'd be a better idea to introduce a property/config frameworkthat 
> produces apache commons configuration object or java properties object for 
> more streamlined use. I've seen 3 mixes of config 
> Load directly into property files
> Use spring bean placeholder
> Read into apache commons configuration



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (ATLAS-1954) UTs and ITs

2018-10-10 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-1954.

Resolution: Fixed

> UTs and ITs
> ---
>
> Key: ATLAS-1954
> URL: https://issues.apache.org/jira/browse/ATLAS-1954
> Project: Atlas
>  Issue Type: Sub-task
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
>
> Add Unit test for all possible cases, ITs might a simple extension to those



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (ATLAS-1956) AtlasSearchResult to include filter attributes by default

2018-10-10 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-1956.

Resolution: Fixed

> AtlasSearchResult to include filter attributes by default
> -
>
> Key: ATLAS-1956
> URL: https://issues.apache.org/jira/browse/ATLAS-1956
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: trunk
>    Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: trunk
>
>
> If no attributes are specified in the SearchParameters then by default 
> AtlasSearchResult should include the attributes present in the filter criteria



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (ATLAS-2149) Cleanup V1 typedef listener interfaces

2018-10-10 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-2149.

Resolution: Fixed

> Cleanup V1 typedef listener interfaces
> --
>
> Key: ATLAS-2149
> URL: https://issues.apache.org/jira/browse/ATLAS-2149
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8-incubating, 1.0.0
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0, 0.8.1, 0.8-incubating
>
>
> Currently GraphBackedSearchIndexer implements typedef change listener for V1 
> and V2 structures, this change removes the V1 dependency to avoid any 
> conflict/race during the index creation



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (ATLAS-2210) Add relationship methods to AtlasClientV2

2018-10-10 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-2210.

Resolution: Won't Do

> Add relationship methods to AtlasClientV2
> -
>
> Key: ATLAS-2210
> URL: https://issues.apache.org/jira/browse/ATLAS-2210
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Andrew Hulbert
>    Assignee: Apoorv Naik
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (ATLAS-2218) Test stability across branches

2018-10-10 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-2218.

Resolution: Fixed

> Test stability across branches
> --
>
> Key: ATLAS-2218
> URL: https://issues.apache.org/jira/browse/ATLAS-2218
> Project: Atlas
>  Issue Type: Bug
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
>
> The tests are pretty inconsistent in runs across master and branch-0.8. This 
> has been preventing a clean build in apache jenkins for a while now. This 
> JIRA is aimed at ensuring build success across master and latest release 
> branch.
> Goals:
> 1. Make IT runs consistent
> 2. Make UTs run successfully on both
> 3. Separate UTs and ITs in webapp module
> 4. Fix UTs in distro module



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (ATLAS-2335) [DSL] Query with multiple aggregator of same type fails

2018-10-10 Thread Apoorv Naik (JIRA)


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

Apoorv Naik commented on ATLAS-2335:


Janusgraph java traversal fixes this issue.

> [DSL] Query with multiple aggregator of same type fails
> ---
>
> Key: ATLAS-2335
> URL: https://issues.apache.org/jira/browse/ATLAS-2335
> Project: Atlas
>  Issue Type: Bug
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
>
> eg DB select min(name), min(owner)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (ATLAS-2225) Split properties per module and concatenate in distro

2018-10-10 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-2225.

Resolution: Later

> Split properties per module and concatenate in distro
> -
>
> Key: ATLAS-2225
> URL: https://issues.apache.org/jira/browse/ATLAS-2225
> Project: Atlas
>  Issue Type: Improvement
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (ATLAS-2479) [Docs] Update Atlas user docs and REST API specs

2018-10-10 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-2479.

Resolution: Fixed

> [Docs] Update Atlas user docs and REST API specs 
> -
>
> Key: ATLAS-2479
> URL: https://issues.apache.org/jira/browse/ATLAS-2479
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0-alpha
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (ATLAS-1746) Test refactor and cleanup

2018-10-10 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-1746.

Resolution: Later

> Test refactor and cleanup
> -
>
> Key: ATLAS-1746
> URL: https://issues.apache.org/jira/browse/ATLAS-1746
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating, 1.0.0
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
>
> Currently the tests have different coding patterns, someplace we rely on DI 
> for getting Objects other places we manually create instances of classes (or 
> dependencies) under test.
> Ideally it should only be done either by DI or hand construct all the time 
> rather than relying on DI. The former seems to be a cleaner approach as we 
> get to validate the DI behavior as well.
> The patch will remove all manual instantiations and replace them with 
> Injectable components



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (ATLAS-1683) Add bean validation to request bodies

2018-10-10 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-1683.

Resolution: Later

> Add bean validation to request bodies
> -
>
> Key: ATLAS-1683
> URL: https://issues.apache.org/jira/browse/ATLAS-1683
> Project: Atlas
>  Issue Type: Bug
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
>
> Add java bean validation to all resources consuming request bodies, better to 
> handle data validation even before reaching the graph store.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Need Help!!! Atlas Installation Error

2018-10-10 Thread Apoorv Naik
Can you share the startup stack trace ? I've run into similar issue and might 
be able to help after having more context.

On 10/10/18, 1:49 PM, "Mahender Shankesi"  wrote:

I changed it but still not working.

Mahender

Sent from my iPhone

> On Oct 10, 2018, at 4:03 PM, Madhan Neethiraj  wrote:
> 
> (copying dev list)
>  
> Mahender – the port # to use is “21000”; the curl commands you listed 
show “2100”. Please try after correcting this.
>  
> @Pierre – perhaps you can help with the question on Cassandra?
>  
> Madhan
>  
>  
> From: Shankesi Mahender 
> Date: Wednesday, October 10, 2018 at 12:37 PM
> To: "mad...@apache.org" 
> Subject: Re: Need Help!!! Atlas Installation Error
>  
> Madhan,
>  
> I followed the instructions in the below site..
>  
> https://atlas.apache.org/InstallationSteps.html
>  
> I did it in two machines one Azure VM and one Azure Hdinisights.
>  
> Hdinsights I'm able to install all steps correctly and run apache_start 
properly. However I'm not able to run the curl command..
>  
> 
sshuser@XXX:~/xyz/apache-atlas-sources-1.1.0/distro/target/apache-atlas-1.1.0/bin$
 curl -u admin:admin https://xxx.azurehdinsight.net:2100/api/atlas/admin/version
> ^C
> 
sshuser@xxx:~/xxx/apache-atlas-sources-1.1.0/distro/target/apache-atlas-1.1.0/bin$
 curl -u admin:admin https://localhost:2100/api/atlas/admin/version
> curl: (7) Failed to connect to localhost port 2100: Connection refused
>  
>  
> However I'm facing challenges in install the steps in VM..
>  
> mvn clean package -Pdist,embedded-cassandra-solr
>  
> I'm getting the below error and it is hanging there..
>  
> 
pache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)
> at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)
> at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)
> at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)
> at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)
> at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)
> at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)
> at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)
> at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase.getGraphInstance(AtlasJanusGraphDatabase.java:117)
> at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.(AtlasJanusGraph.java:93)
>  
>  
> Any help is greatly appreciated..
>  
>  
> Mahender
> at org.a
>  
> On Tue, Oct 9, 2018 at 3:09 PM Madhan Neethiraj  wrote:
> Mahender,
>  
> “port 80”? Atlas should be listening in port 21000 by default. Which URL 
are you getting this error for?
>  
> Thanks,
> Madhan
>  
>  
>  
>  
> From: Shankesi Mahender 
> Date: Tuesday, October 9, 2018 at 11:56 AM
> To: "mad...@apache.org" 
> Subject: Re: Need Help!!! Atlas Installation Error
>  
> Thanks Madhan..
>  
> When I tried to run the curl command with admin:admin I got below error.
>  
> curl: (7) Failed to connect to ipaddress port 80: Connection refused
>  
> When I tried to start atlas_start.py I got the following error
>  
>   File "atlas_start.py", line 107
> print "Cannot run setup when server is running."
>^
> SyntaxError: Missing parentheses in call to 'print'
>  
> Do you know anything about this?
>  
> Thanks for your help.
>  
> Mahender
>  
> On Tue, Oct 9, 2018 at 2:07 PM Madhan Neethiraj  wrote:
> Mahender,
>  
> Default username:password is: admin:admin. Please try with these and let 
me know.
>  
> Thanks,
> Madhan
>  
>  
>  
>  
> From: Shankesi Mahender 
> Date: Tuesday, October 9, 2018 at 6:03 AM
> To: Shankesi Mahender 
> Subject: Need Help!!! Atlas Installation Error
>  
> I’m trying to install Apache Atlas on my Hdinsight cluster and following 
the instructions from the below page.
>  
> https://atlas.apache.org/InstallationSteps.html
>  
> I was able to install correctly until the below point.
>  
> curl -u username:password http://localhost:21000/api/atlas/admin/version
> 
>  
> When I execute this command it is throwing an error, I have replace the 
localhost with my azure hdinsight 

Re: Review Request 68893: ATLAS-2905: Generate lineage information for process entities

2018-10-02 Thread Apoorv Naik

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


Ship it!




Ship It!

- Apoorv Naik


On Oct. 2, 2018, 5:43 a.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68893/
> ---
> 
> (Updated Oct. 2, 2018, 5:43 a.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, keval bhatt, Madhan 
> Neethiraj, and Nixon Rodrigues.
> 
> 
> Bugs: ATLAS-2905
> https://issues.apache.org/jira/browse/ATLAS-2905
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Currently lineage information is generated only for DataSet entities and its 
> derivatives. Lineage information should also be generated for Process 
> entities and in UI lineage tab should be enabled for any process entities and 
> lineage rendered.
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/AtlasErrorCode.java 47726aa6e 
>   
> repository/src/main/java/org/apache/atlas/discovery/EntityLineageService.java 
> 5d02ea541 
>   
> repository/src/main/java/org/apache/atlas/util/AtlasGremlin2QueryProvider.java
>  82243ad2a 
>   
> repository/src/main/java/org/apache/atlas/util/AtlasGremlin3QueryProvider.java
>  9585a57a1 
>   
> repository/src/main/java/org/apache/atlas/util/AtlasGremlinQueryProvider.java 
> 8555b4c43 
> 
> 
> Diff: https://reviews.apache.org/r/68893/diff/1/
> 
> 
> Testing
> ---
> 
> Validated through REST:
> 
> curl -X GET 
> http://ctr-e138-1518143905142-494504-01-03.hwx.site:21000/api/atlas/v2/lineage/07050484-a2e7-4118-af2a-b59b39c3c0d5
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>



Re: Question about Metadata store

2018-10-01 Thread Apoorv Naik
Only hbase, Cassandra and berkeleyje are supported are storage backend. This 
dependency is from JanusGraph. I think for audits you can still implement a 
custom repository but not for the core storage.

Sent from Nine

From: Weiqing Yang 
Sent: Tuesday, October 2, 2018 5:59 AM
To: dev@atlas.apache.org
Subject: Question about Metadata store

Hi All,

Per the Atlas documents, the default metadata store is HBase. Is it
possible to use other metadata stores like MySQL instead of HBase? I am
wondering if the metadata store is configurable/pluginable?

Looking forward to your reply. Thank you.

Best regards,
WQ Yang


Re: Review Request 68870: ATLAS-2786: updated HBase and Solr clients to use all zookeeper entires

2018-09-27 Thread Apoorv Naik

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



Looks like we need to port it over for Janusgraph as well.

- Apoorv Naik


On Sept. 28, 2018, 3 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68870/
> ---
> 
> (Updated Sept. 28, 2018, 3 a.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, keval bhatt, Nixon 
> Rodrigues, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2786
> https://issues.apache.org/jira/browse/ATLAS-2786
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Due to incorrect use of Apache commons configiration class, only the first 
> host specified in zookeeper connection sttring was being used to connect to 
> HBase and Solr. This causes failure when the first zookeeper host is not 
> reachable.
> 
> 
> Diffs
> -
> 
>   
> graphdb/titan0/src/main/java/com/thinkaurelius/titan/diskstorage/solr/Solr5Index.java
>  90d24e4d8 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/HBaseBasedAuditRepository.java
>  774934c7f 
> 
> 
> Diff: https://reviews.apache.org/r/68870/diff/1/
> 
> 
> Testing
> ---
> 
> In an environment with 3 zookeepers, verified that Atlas service is not 
> impacted when any one zookeeper instance (including the first one) is not 
> reachable.
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>



Re: Review Request 68870: ATLAS-2786: updated HBase and Solr clients to use all zookeeper entires

2018-09-27 Thread Apoorv Naik

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


Ship it!




Ship It!

- Apoorv Naik


On Sept. 28, 2018, 3 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68870/
> ---
> 
> (Updated Sept. 28, 2018, 3 a.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, keval bhatt, Nixon 
> Rodrigues, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2786
> https://issues.apache.org/jira/browse/ATLAS-2786
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Due to incorrect use of Apache commons configiration class, only the first 
> host specified in zookeeper connection sttring was being used to connect to 
> HBase and Solr. This causes failure when the first zookeeper host is not 
> reachable.
> 
> 
> Diffs
> -
> 
>   
> graphdb/titan0/src/main/java/com/thinkaurelius/titan/diskstorage/solr/Solr5Index.java
>  90d24e4d8 
>   
> repository/src/main/java/org/apache/atlas/repository/audit/HBaseBasedAuditRepository.java
>  774934c7f 
> 
> 
> Diff: https://reviews.apache.org/r/68870/diff/1/
> 
> 
> Testing
> ---
> 
> In an environment with 3 zookeepers, verified that Atlas service is not 
> impacted when any one zookeeper instance (including the first one) is not 
> reachable.
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>



Re: Review Request 68792: ATLAS-2882: refactored import transformer creation to set context in constructor

2018-09-21 Thread Apoorv Naik

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


Ship it!




Ship It!

- Apoorv Naik


On Sept. 21, 2018, 12:33 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68792/
> ---
> 
> (Updated Sept. 21, 2018, 12:33 a.m.)
> 
> 
> Review request for atlas, Abhishek Kadam, Apoorv Naik, Ashutosh Mestry, keval 
> bhatt, Nixon Rodrigues, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2882
> https://issues.apache.org/jira/browse/ATLAS-2882
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> - refactored import transformer creation to set context in constructor
> - fixed incorrect ObjectIdEquals.matches()
> 
> 
> Diffs
> -
> 
>   intg/src/main/java/org/apache/atlas/entitytransform/Action.java fa1855893 
>   
> intg/src/main/java/org/apache/atlas/entitytransform/AtlasEntityTransformer.java
>  e9b2afdf7 
>   intg/src/main/java/org/apache/atlas/entitytransform/BaseEntityHandler.java 
> dd6c66539 
>   intg/src/main/java/org/apache/atlas/entitytransform/Condition.java 
> 174b9b48b 
>   intg/src/main/java/org/apache/atlas/entitytransform/NeedsContext.java 
> 5c16bcfbc 
>   
> intg/src/test/java/org/apache/atlas/entitytransform/TransformationHandlerTest.java
>  c76f95916 
> 
> 
> Diff: https://reviews.apache.org/r/68792/diff/1/
> 
> 
> Testing
> ---
> 
> Pre-commit tests run - 
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/678/
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>



Re: Review Request 68752: ATLAS-2878: avoid retrieval of entiyWithExtInfo when extInfo is not needed

2018-09-18 Thread Apoorv Naik

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



Changes look good. Waiting for the PreCommit to finish up.

- Apoorv Naik


On Sept. 18, 2018, 8:13 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68752/
> ---
> 
> (Updated Sept. 18, 2018, 8:13 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, keval bhatt, Nixon 
> Rodrigues, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2878
> https://issues.apache.org/jira/browse/ATLAS-2878
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Reviewed all occurances of entityWithExtInfo retrieval; where extInfo was not 
> needed/used, updated the code to retrieve entity without extInfo.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/FullTextMapperV2.java
>  76acf8ce9 
>   server-api/src/main/java/org/apache/atlas/RequestContext.java f810dc9e8 
> 
> 
> Diff: https://reviews.apache.org/r/68752/diff/1/
> 
> 
> Testing
> ---
> 
> Pre-commit test runs - 
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/668/
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>



Re: Draft board report for Apache Atlas: September 2018

2018-09-13 Thread Apoorv Naik
+1 for the report. Thanks for putting this together. 

On 9/13/18, 12:46 AM, "Ayub Khan Pathan"  wrote:

Madhan,

You might want to consider adding export-import feature enhancements to the 
report.

Rest everything looks good to me, +1.

Thanks for putting together this report.

Regards
Ayub Khan

On 9/13/18, 12:28 AM, "Madhan Neethiraj"  wrote:

Atlas team,

 

Please review the draft board report below and send your 
feedback/comments.

 

Thanks,

Madhan

 

 

## Description:

  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

 

## Issues:

  There are no issues requiring board attention at this time.

 

## Activity:

  - team has been busy working on maint releases 1.1.0 and 0.8.3

  - vote to release 1.1.0 concluded on 9/12/2018. Release announcement 
will go out in next few days

  - release 0.8.3 is likely to be around mid October-2018

  - updated authorization model to support access control on 
relationship operations

  - added support for AWS S3 datatypes, in Atlas server and Hive hook

  - updated JanusGraph version from 0.2.0 to 0.3.0

  - updated hooks to send Kafka notifications asynchronously

  - updated classification propagation with options to handle 
entity-deletes

  - updated notification module to send notification after successful 
commit

  - added timestamp in notifications sent from Atlas server

  - will start work on supporting Hadoop 3, HBase 2, Solr 7 in master 
branch

 

## Health report:

  - 1 new contributor added in last 3 months: Kapildeo Nayak

 

## PMC changes:

  - Currently 33 PMC members

  - No new PMC members added in last 3 months

  - Last PMC member addition was on 6/21/2017

 

## Committer base changes:

  - Currently 37 committers

  - No new committers added in last 3 months

  - Last addition to committer role was on 1/9/2018

 

## Releases:

  0.8.3plan to release by 10/15/2018

  1.1.0plan to release by 09/15/2018

  1.0.0was released on 06/02/2018

  0.8.2was released on 02/05/2018

  1.0.0-alpha  was released on 01/25/2018

  0.8.1was released on 08/29/2017

  0.8-incubating   was released on 03/16/2017

  0.7.1-incubating was released on 01/26/2017

  0.7-incubating   was released on 07/09/2016

  0.6-incubating   was released on 12/31/2015

  0.5-incubating   was released on 07/11/2015

 

 







Re: Review Request 68691: Export Service: Hdfs path entities are created before starting export

2018-09-11 Thread Apoorv Naik

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



Looks good to me. Can you run it through the PreCommit pipeline ?

- Apoorv Naik


On Sept. 11, 2018, 10:32 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68691/
> ---
> 
> (Updated Sept. 11, 2018, 10:32 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Madhan Neethiraj, Nixon Rodrigues, and 
> Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2869
> https://issues.apache.org/jira/browse/ATLAS-2869
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> - _HdfsPathCreator_ class creates hdfs_path entity based on parameters.
> - _ExportService_ uses the new class.
> 
> 
> **CURL**
> 
> curl -X POST -u admin:admin -H "Content-Type: application/json" -H 
> "Cache-Control: no-cache" -d @../docs/export-options.json 
> http://localhost:21000/api/atlas/admin/export > ../docs/hr.zip
> 
> _export-options.json_
> ```
> {
> "itemsToExport": [
> { "typeName": "hdfs_path", "uniqueAttributes": { "path": 
> "/warehouse/hr" }}
> ],
> "options": {
> "fetchType": "full",
> "matchType": "startsWith",
> "skipLineage": "true",
> "replicatedTo": "clx",
> "changeMarker": 0
> }
> }
> ```
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/ExportService.java
>  aded67caf 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/HdfsPathEntityCreator.java
>  PRE-CREATION 
>   
> repository/src/test/java/org/apache/atlas/repository/impexp/HdfsPathEntityCreatorTest.java
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/68691/diff/1/
> 
> 
> Testing
> ---
> 
> **Unit tests**
> 
> New tests added.
> 
> **Functional tests**
> 
> Verified via UI.
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>



Re: Review Request 68583: ATLAS-2844: added eventTime field in EntityNotificationV2

2018-08-31 Thread Apoorv Naik

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


Ship it!




Ship It!

- Apoorv Naik


On Aug. 30, 2018, 10:52 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68583/
> ---
> 
> (Updated Aug. 30, 2018, 10:52 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, Graham Wallis, and 
> Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2844
> https://issues.apache.org/jira/browse/ATLAS-2844
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> updated EntityNotificationV2 with addition of 'eventTime' attribute. Here is 
> a sample notification message with this change:
> 
> {
>   "type":"ENTITY_NOTIFICATION_V2",
>   "entity": {"typeName":"hive_table",
>  "attributes":{"owner":"hive",
>"createTime":1535622192000,
>"qualifiedName":"test.testtbl2@cl1",
>"name":"testtbl2"},
>  "guid":"8bc1ba7b-3c76-4311-81ae-c05fd07d667b",
>  "status":"ACTIVE",
>  "displayText":"testtbl2"
>  },
>   "operationType":"ENTITY_CREATE",
>   "eventTime":1535622192647
> }
> 
> 
> Diffs
> -
> 
>   
> intg/src/main/java/org/apache/atlas/model/notification/EntityNotification.java
>  6cdae8925 
>   
> webapp/src/main/java/org/apache/atlas/notification/EntityNotificationListenerV2.java
>  c70011f24 
> 
> 
> Diff: https://reviews.apache.org/r/68583/diff/1/
> 
> 
> Testing
> ---
> 
> Verified that the notification includes eventTime attribute - as shown above.
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>



Re: Review Request 68584: ATLAS-2853: updated to send entity-notifications after successful graph transaction commit

2018-08-31 Thread Apoorv Naik

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


Ship it!




Ship It!

- Apoorv Naik


On Aug. 31, 2018, 4:12 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68584/
> ---
> 
> (Updated Aug. 31, 2018, 4:12 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, Graham Wallis, keval 
> bhatt, Nixon Rodrigues, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2853
> https://issues.apache.org/jira/browse/ATLAS-2853
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> updated to send entity notifications only after graph transaction is committed
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityChangeNotifier.java
>  783d62fb3 
>   
> webapp/src/main/java/org/apache/atlas/notification/EntityNotificationListenerV2.java
>  c70011f24 
>   
> webapp/src/main/java/org/apache/atlas/notification/EntityNotificationSender.java
>  PRE-CREATION 
>   
> webapp/src/main/java/org/apache/atlas/notification/NotificationEntityChangeListener.java
>  1eeecefc1 
> 
> 
> Diff: https://reviews.apache.org/r/68584/diff/2/
> 
> 
> Testing
> ---
> 
> Verified that the notifications are sent post transaction commit.
> 
> Pre-commit test run: 
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/645
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>



[jira] [Resolved] (ATLAS-2848) Fix property name in ApplicationProperties class

2018-08-29 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-2848.

Resolution: Fixed

> Fix property name in ApplicationProperties class
> 
>
> Key: ATLAS-2848
> URL: https://issues.apache.org/jira/browse/ATLAS-2848
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.1.0
>
>
> {color:#00} atlas.graph.cache.tx-cache.size is wrong, change to 
> atlas.graph.cache.tx-cache-size{color}
> {color:#00}courtesy: zhaxiaodong9860 (pull request #8){color}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-2848) Fix property name in ApplicationProperties class

2018-08-29 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2848:
---
Fix Version/s: (was: 0.8.3)

> Fix property name in ApplicationProperties class
> 
>
> Key: ATLAS-2848
> URL: https://issues.apache.org/jira/browse/ATLAS-2848
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.1.0
>
>
> {color:#00} atlas.graph.cache.tx-cache.size is wrong, change to 
> atlas.graph.cache.tx-cache-size{color}
> {color:#00}courtesy: zhaxiaodong9860 (pull request #8){color}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-2848) Fix property name in ApplicationProperties class

2018-08-29 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2848:
---
Affects Version/s: (was: 0.8.2)
   (was: 0.8.1)

> Fix property name in ApplicationProperties class
> 
>
> Key: ATLAS-2848
> URL: https://issues.apache.org/jira/browse/ATLAS-2848
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.1.0
>
>
> {color:#00} atlas.graph.cache.tx-cache.size is wrong, change to 
> atlas.graph.cache.tx-cache-size{color}
> {color:#00}courtesy: zhaxiaodong9860 (pull request #8){color}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ATLAS-2848) Fix property name in ApplicationProperties class

2018-08-29 Thread Apoorv Naik (JIRA)
Apoorv Naik created ATLAS-2848:
--

 Summary: Fix property name in ApplicationProperties class
 Key: ATLAS-2848
 URL: https://issues.apache.org/jira/browse/ATLAS-2848
 Project: Atlas
  Issue Type: Bug
Affects Versions: 1.0.0, 0.8.2, 0.8.1
Reporter: Apoorv Naik
Assignee: Apoorv Naik
 Fix For: 0.8.3, 1.1.0


{color:#00} atlas.graph.cache.tx-cache.size is wrong, change to 
atlas.graph.cache.tx-cache-size{color}

{color:#00}courtesy: zhaxiaodong9860 (pull request #8){color}

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Hello, When i install the atlas with solr5 cloud. I met the problem, Please help

2018-08-27 Thread Apoorv Naik
What errors are you seeing on the server side ? Is atlas not able to start ? Or 
search results are inconsistent ? 
It'd be helpful if you could share the application.log file.

On 8/27/18, 1:23 PM, "Brice"  wrote:

I too am having this issue.

This is from  print(atlas_classpath) in the start_atlas_server function
of  atlas_start.py:

/opt/apache-atlas-1.0.0/conf:

/opt/apache-atlas-1.0.0/server/webapp/atlas/WEB-INF/classes:

/opt/apache-atlas-1.0.0/server/webapp/atlas/WEB-INF/lib/*:

/opt/apache-atlas-1.0.0/libext/*:

/opt/solr-5.5.1/*:

/opt/hbase-1.1.9/conf/

"/opt/solr-5.5.1/*" was added manually by me in the script

Thanks for any help




Review Request 68478: ATLAS-2834: Atlas authorizer init should be done in HA mode

2018-08-22 Thread Apoorv Naik

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

Review request for atlas and Madhan Neethiraj.


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


Repository: atlas


Description
---

See JIRA


Diffs
-

  
repository/src/main/java/org/apache/atlas/repository/store/bootstrap/AtlasTypeDefStoreInitializer.java
 5fa37d961 


Diff: https://reviews.apache.org/r/68478/diff/1/


Testing
---


Thanks,

Apoorv Naik



[jira] [Updated] (ATLAS-2834) In HA environment, authorizer initialization is done only on first access.

2018-08-22 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2834:
---
Attachment: 0001-ATLAS-2834-Init-authorizer-when-Atlas-is-in-HA-mode.patch

> In HA environment, authorizer initialization is done only on first access.
> --
>
> Key: ATLAS-2834
> URL: https://issues.apache.org/jira/browse/ATLAS-2834
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Anuja Leekha
>Priority: Major
>  Labels: atlas
> Fix For: 1.1.0
>
> Attachments: 
> 0001-ATLAS-2834-Init-authorizer-when-Atlas-is-in-HA-mode.patch
>
>
> In HA environment, Atlas doesn't make a call to Ranger to download Atlas 
> policies unless it is accessed for the first time.
> This is not an HA specific feature and the behavior should be consistent with 
> non HA feature - of downloading Atlas policies from Ranger when Atlas is 
> restarted after enabling Ranger plugin.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (ATLAS-2834) In HA environment, authorizer initialization is done only on first access.

2018-08-22 Thread Apoorv Naik (JIRA)


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

Apoorv Naik reassigned ATLAS-2834:
--

Assignee: Apoorv Naik

> In HA environment, authorizer initialization is done only on first access.
> --
>
> Key: ATLAS-2834
> URL: https://issues.apache.org/jira/browse/ATLAS-2834
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Anuja Leekha
>    Assignee: Apoorv Naik
>Priority: Major
>  Labels: atlas
> Fix For: 1.1.0
>
> Attachments: 
> 0001-ATLAS-2834-Init-authorizer-when-Atlas-is-in-HA-mode.patch
>
>
> In HA environment, Atlas doesn't make a call to Ranger to download Atlas 
> policies unless it is accessed for the first time.
> This is not an HA specific feature and the behavior should be consistent with 
> non HA feature - of downloading Atlas policies from Ranger when Atlas is 
> restarted after enabling Ranger plugin.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Error: Mandatory attribute value missing in type Referenceable

2018-08-22 Thread Apoorv Naik
Like the message states, you'll have to set the "qualifiedName" attribute for 
the storm AtlasEntity. 
Please refer to the storm model JSON to ensure that you pass all the required  
attributes when attempting a create.

On 8/22/18, 7:25 AM, "anshu shukla"  wrote:

Hi,

I am trying to create instances for the storm_topology type in Atlas.
*My logic goes here:*

AtlasEntity storm_topology = new AtlasEntity("storm_topology");

storm_topology.setAttribute("nodes",
AtlasTypeUtil.toObjectIds(Arrays.asList(*entity_stormNode_temp*)));

where  *entity_stormNode_temp is the return type of createInstance()
function for storm_node type.*

*Error:*
*Exception in thread "main" org.apache.atlas.AtlasServiceException:
Metadata service API org.apache.atlas.AtlasClientV2$API_V2@78452606 failed
with status 404 (Not Found) Response Body
({"errorCode":"ATLAS-404-00-007","errorMessage":"Invalid instance
creation/updation parameters passed : storm_topology.qualifiedName:
mandatory attribute value missing in type Referenceable"})*

-- 
Thanks & Regards,
Anshu Shukla




Re: Pre-installed models

2018-08-21 Thread Apoorv Naik
If you remove all folders except the one named *base model* then Atlas will not 
load the other types.

HTH

On 8/21/18, 8:09 PM, "Allen Cheng"  wrote:

Hi,  Atlas experts

When we install and start a new Atlas server instance, there are a few type
models that are automatically pre-installed, e.g. Hive, Storm, HBase, HDFS,
etc. There are new models added in Atlas 1.0.

Is there any way to skip installing some of the models, and only install
the ones I want?   Is there any property that controls this?  Or if I
remove some of the model json files in the install sir, will it work?

Thanks

Allen




Re: Review Request 68435: ATLAS-2830: Tag Propagation, Entity Delete : Classification update notification not sent to entities down the lineage present after the deleted entity.

2018-08-21 Thread Apoorv Naik

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




repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java
Lines 1672 (patched)
<https://reviews.apache.org/r/68435/#comment291160>

Handle null, isActive doesn't do that right now.



repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java
Lines 1685 (patched)
<https://reviews.apache.org/r/68435/#comment291161>

same here


- Apoorv Naik


On Aug. 21, 2018, 5:13 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68435/
> ---
> 
> (Updated Aug. 21, 2018, 5:13 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, and 
> Nixon Rodrigues.
> 
> 
> Bugs: ATLAS-2830
> https://issues.apache.org/jira/browse/ATLAS-2830
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> 1. Create a lineage like the following :
> 
> table1 -> table2 > table3 -> table4 > table5
> 
> 2. Add tag1 to table1 ( with default false value for 
> removePropagationsOnEntityDelete , propagate to True)
> 3. drop table3
> 4. Edit some tag attributes of tag1 associated to table1.
> 5. In Atlas , the tag1 attributes are updated down the lineage till table5.
> 6. But , CLASSIFICATION_UPDATE notification is sent to ATLAS_ENTITIES only 
> till table3. No notification is sent for table4 and table5.
> 
> 
> Diffs
> -
> 
>   repository/src/main/java/org/apache/atlas/repository/graph/GraphHelper.java 
> 78ed74d65 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java
>  7eb32148a 
> 
> 
> Diff: https://reviews.apache.org/r/68435/diff/3/
> 
> 
> Testing
> ---
> 
> Precommit: 
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/601/console
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>



[jira] [Updated] (ATLAS-2827) Unable to persist vertex when indexed string attribute is really long

2018-08-17 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2827:
---
Attachment: (was: 0001-Indexed-string-compaction-patch.patch)

> Unable to persist vertex when indexed string attribute is really long
> -
>
> Key: ATLAS-2827
> URL: https://issues.apache.org/jira/browse/ATLAS-2827
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8.1, 0.8.2, 1.0.0, trunk
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.3, 1.1.0
>
>
> Titan/Janus  creates an inverted index key which exceeds the row length 
> restriction imposed by HBase hence the vertex fails to persist with backend 
> exception.
>  
> Solution:
> In the entity graph mapping, before persisting the  vertex we need to trim 
> down the value (although it'll cause data loss) to avoid Atlas becoming non 
> functional for such edge cases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Review Request 68388: ATLAS-2355: Fix for IT failures in branch-0.8

2018-08-16 Thread Apoorv Naik

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


Ship it!




Ship It!

- Apoorv Naik


On Aug. 16, 2018, 5:39 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68388/
> ---
> 
> (Updated Aug. 16, 2018, 5:39 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-2355
> https://issues.apache.org/jira/browse/ATLAS-2355
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> - backported fix for IT failures from master branch
> - updated assert() with useful message to enable quicker troubleshooting of 
> failures
> 
> 
> Diffs
> -
> 
>   webapp/src/test/java/org/apache/atlas/web/integration/BasicSearchIT.java 
> 5806a10d6 
>   
> webapp/src/test/java/org/apache/atlas/web/integration/EntityJerseyResourceIT.java
>  f2a78010a 
>   webapp/src/test/resources/json/search-parameters/entity-filters.json 
> 67b0b51f5 
> 
> 
> Diff: https://reviews.apache.org/r/68388/diff/1/
> 
> 
> Testing
> ---
> 
> verified that the fix addresses failures in BasicSearchIT and 
> EntityJerseyResourceIT.
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>



[jira] [Updated] (ATLAS-2827) Unable to persist vertex when indexed string attribute is really long

2018-08-16 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2827:
---
Affects Version/s: trunk
   0.8.1
   0.8.2
   1.0.0

> Unable to persist vertex when indexed string attribute is really long
> -
>
> Key: ATLAS-2827
> URL: https://issues.apache.org/jira/browse/ATLAS-2827
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8.1, 0.8.2, 1.0.0, trunk
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
>
> Titan/Janus  creates an inverted index key which exceeds the row length 
> restriction imposed by HBase hence the vertex fails to persist with backend 
> exception.
>  
> Solution:
> In the entity graph mapping, before persisting the  vertex we need to trim 
> down the value (although it'll cause data loss) to avoid Atlas becoming non 
> functional for such edge cases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ATLAS-2827) Unable to persist vertex when indexed string attribute is really long

2018-08-16 Thread Apoorv Naik (JIRA)
Apoorv Naik created ATLAS-2827:
--

 Summary: Unable to persist vertex when indexed string attribute is 
really long
 Key: ATLAS-2827
 URL: https://issues.apache.org/jira/browse/ATLAS-2827
 Project: Atlas
  Issue Type: Improvement
Reporter: Apoorv Naik
Assignee: Apoorv Naik


Titan/Janus  creates an inverted index key which exceeds the row length 
restriction imposed by HBase hence the vertex fails to persist with backend 
exception.

 

Solution:

In the entity graph mapping, before persisting the  vertex we need to trim down 
the value (although it'll cause data loss) to avoid Atlas becoming non 
functional for such edge cases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Queries regarding the type system

2018-08-15 Thread Apoorv Naik
1. Model file based type creation ensures that the models are available as soon 
as Atlas starts up and is ready.
2. RelationshipDefs in Atlas are used to define relation between the types, eg. 
Hive_table HAS hive_column(s), hive_db HAS hive_table(s) and so on
3. Relationships are used to inject dynamic attributes into the end1 or end2 
type.
4. For more explanation on RelationshipCategory please refer to the 
AtlasRelationshipDef class, the comments around RelationshipCategory should be 
self explanatory
5. ownedRef constraint is kind of a "containment" restriction, an ownedRef type 
can't exist without the entity/instance of the type that defines it and 
inverseRef is kind of a "reverse pointer" to the "container" type. 

e.g. hive_columns are ownedRef under hive_table that means a column entity 
can't exist without the presence of hive_table and it's inverseRef states that 
the type "hive_table" would have an attribute "columns" of type hive_column 

NOTE: If you want to build a model using relationships then you can ignore the 
attribute constraints "ownedRef" and "inverseRef". Relationships are 
recommended over traditional attributes definitions when trying to model custom 
types (starting from Atlas 1.0)

On 8/15/18, 9:44 AM, "anshu shukla"  wrote:

Hi,

I have the following queries regarding the type system in Atlas.


   1. What is the diff between the new Type creation using the model file
   (JSON) and using the createClassTypeDef() function as done in quickstart
   example? And if both are same then which one is preferred one.
   2. Is there any place where I can read more about the

   *relationshipDefs* as discussed in the model files.like -

   -

  What does *relationshipCategory* exactly means and how it is
iterpreted by Atlas.

  -

  How can i define them in the Java code (same as in model file..)

  -

  What is correct interpretation of CONSTRAINT_TYPE_OWNED_REF,

  CONSTRAINT_TYPE_INVERSE_REF and CONSTRAINT_PARAM_ATTRIBUTE.




-- 
Thanks & Regards,
Anshu Shukla




Review Request 68358: Dependency upgrades

2018-08-14 Thread Apoorv Naik

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

Review request for atlas.


Repository: atlas


Description
---

Upgrading to latest stable (non-breaking) dependencies


Diffs
-

  pom.xml f4686bf83 
  webapp/pom.xml ab86a78e1 


Diff: https://reviews.apache.org/r/68358/diff/1/


Testing
---

https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/570/console


Thanks,

Apoorv Naik



[jira] [Resolved] (ATLAS-2817) Update to JanusGraph 0.3.x

2018-08-13 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-2817.

Resolution: Fixed

> Update to JanusGraph 0.3.x
> --
>
> Key: ATLAS-2817
> URL: https://issues.apache.org/jira/browse/ATLAS-2817
> Project: Atlas
>  Issue Type: Improvement
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Attachments: 0001-Janusgraph-update-to-0.3.0.patch
>
>
> There are couple of index related improvements in this version which helps 
> resolve the slowness in few of our DSL queries. This upgrade would speed up 
> DSL execution.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (ATLAS-2817) Update to JanusGraph 0.3.x

2018-08-13 Thread Apoorv Naik (JIRA)


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

Apoorv Naik commented on ATLAS-2817:


Committed to master : 
https://git-wip-us.apache.org/repos/asf?p=atlas.git;a=commit;h=4ddceacb0dc4add848a97a445a3091624aaaff7e

> Update to JanusGraph 0.3.x
> --
>
> Key: ATLAS-2817
> URL: https://issues.apache.org/jira/browse/ATLAS-2817
> Project: Atlas
>  Issue Type: Improvement
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Attachments: 0001-Janusgraph-update-to-0.3.0.patch
>
>
> There are couple of index related improvements in this version which helps 
> resolve the slowness in few of our DSL queries. This upgrade would speed up 
> DSL execution.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Review Request 68330: JanusGraph upgrade to 0.3.0

2018-08-13 Thread Apoorv Naik

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

Review request for atlas.


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


Repository: atlas


Description
---

Version upgrade to inherit some index related enhancement.


Diffs
-

  graphdb/janus/pom.xml 32ec2614f 
  
graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusGraph.java
 00bb57786 


Diff: https://reviews.apache.org/r/68330/diff/1/


Testing
---

https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/560/console


Thanks,

Apoorv Naik



[jira] [Updated] (ATLAS-2817) Update to JanusGraph 0.3.x

2018-08-13 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2817:
---
Attachment: 0001-Janusgraph-update-to-0.3.0.patch

> Update to JanusGraph 0.3.x
> --
>
> Key: ATLAS-2817
> URL: https://issues.apache.org/jira/browse/ATLAS-2817
> Project: Atlas
>  Issue Type: Improvement
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Attachments: 0001-Janusgraph-update-to-0.3.0.patch
>
>
> There are couple of index related improvements in this version which helps 
> resolve the slowness in few of our DSL queries. This upgrade would speed up 
> DSL execution.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (ATLAS-2812) Upgrade commons-fileupload to 1.3.3

2018-08-10 Thread Apoorv Naik (JIRA)


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

Apoorv Naik commented on ATLAS-2812:


Looks good for commit. Thanks Sarath.

> Upgrade commons-fileupload to 1.3.3
> ---
>
> Key: ATLAS-2812
> URL: https://issues.apache.org/jira/browse/ATLAS-2812
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating, 0.8.1, 0.8.2
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.0.0, 0.8.3, 1.1.0
>
> Attachments: 0001-ATLAS-2812-Upgrade-commons-fileupload-to-1.3.3.patch
>
>
> Atlas packages commons-fileupload-1.2.1.jar which has a potential security 
> vulnerability
> Need to upgrade to 1.3.1+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (ATLAS-2816) Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2

2018-08-09 Thread Apoorv Naik (JIRA)


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

Apoorv Naik edited comment on ATLAS-2816 at 8/10/18 4:12 AM:
-

One suggestion, use the followReferences flag instead of hardcoding the 
ignoreRelationship param. This would make is easier to toggle if certain 
deployment scenario wants to use the relationship details to be captured in the 
entityText. Also follow this guideline for patch creation,

 
 # Work on a local branch
 # Commit the patch on local branch
 # Generate patch using "git format-patch origin/master" (this way you get 
credit by including author info in the patch)
 # Attach the patch to JIRA

 

HTH


was (Author: apoorvnaik):
One suggestion, use the followReferences flag instead of hardcoding the 
ignoreRelationship param. This would make is easier to toggle if certain 
deployment scenario wants to use the relationship details to be captured in the 
entityText.

 

HTH

> Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2
> 
>
> Key: ATLAS-2816
> URL: https://issues.apache.org/jira/browse/ATLAS-2816
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Chengbing Liu
>Assignee: Apoorv Naik
>Priority: Major
> Attachments: ATLAS-2816.01.patch
>
>
> We encountered a problem when using Hive bridge in production. One database 
> has 5000+ tables. Importing the first table costs only tens of milliseconds, 
> and then it becomes slower with more tables. In the end, it costs 1~2 seconds 
> to import one table.
> After investigation, we realized that it is not necessary for the 
> {{FullTextMapperV2}} to retrieve all the relationship of the database each 
> time a table is imported. The time complexity of importing a whole database 
> actually goes to O(n^2) (n is number of tables).
> We propose to add a parameter to the constructor of {{EntityGraphRetriever}}: 
> {{ignoreRelationship}}. When set to true, {{mapVertexToAtlasEntity}} will 
> skip the {{mapRelationshipAttributes}} call. Since {{FullTextMapperV2}} will 
> not use relationship attributes of the entity, this can save plenty of time 
> when importing entities with a large number of relations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (ATLAS-2816) Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2

2018-08-09 Thread Apoorv Naik (JIRA)


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

Apoorv Naik commented on ATLAS-2816:


One suggestion, use the followReferences flag instead of hardcoding the 
ignoreRelationship param. This would make is easier to toggle if certain 
deployment scenario wants to use the relationship details to be captured in the 
entityText.

 

HTH

> Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2
> 
>
> Key: ATLAS-2816
> URL: https://issues.apache.org/jira/browse/ATLAS-2816
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Chengbing Liu
>Priority: Major
> Attachments: ATLAS-2816.01.patch
>
>
> We encountered a problem when using Hive bridge in production. One database 
> has 5000+ tables. Importing the first table costs only tens of milliseconds, 
> and then it becomes slower with more tables. In the end, it costs 1~2 seconds 
> to import one table.
> After investigation, we realized that it is not necessary for the 
> {{FullTextMapperV2}} to retrieve all the relationship of the database each 
> time a table is imported. The time complexity of importing a whole database 
> actually goes to O(n^2) (n is number of tables).
> We propose to add a parameter to the constructor of {{EntityGraphRetriever}}: 
> {{ignoreRelationship}}. When set to true, {{mapVertexToAtlasEntity}} will 
> skip the {{mapRelationshipAttributes}} call. Since {{FullTextMapperV2}} will 
> not use relationship attributes of the entity, this can save plenty of time 
> when importing entities with a large number of relations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (ATLAS-2816) Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2

2018-08-09 Thread Apoorv Naik (JIRA)


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

Apoorv Naik reassigned ATLAS-2816:
--

Assignee: Apoorv Naik

> Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2
> 
>
> Key: ATLAS-2816
> URL: https://issues.apache.org/jira/browse/ATLAS-2816
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Chengbing Liu
>    Assignee: Apoorv Naik
>Priority: Major
> Attachments: ATLAS-2816.01.patch
>
>
> We encountered a problem when using Hive bridge in production. One database 
> has 5000+ tables. Importing the first table costs only tens of milliseconds, 
> and then it becomes slower with more tables. In the end, it costs 1~2 seconds 
> to import one table.
> After investigation, we realized that it is not necessary for the 
> {{FullTextMapperV2}} to retrieve all the relationship of the database each 
> time a table is imported. The time complexity of importing a whole database 
> actually goes to O(n^2) (n is number of tables).
> We propose to add a parameter to the constructor of {{EntityGraphRetriever}}: 
> {{ignoreRelationship}}. When set to true, {{mapVertexToAtlasEntity}} will 
> skip the {{mapRelationshipAttributes}} call. Since {{FullTextMapperV2}} will 
> not use relationship attributes of the entity, this can save plenty of time 
> when importing entities with a large number of relations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (ATLAS-2816) Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2

2018-08-09 Thread Apoorv Naik (JIRA)


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

Apoorv Naik commented on ATLAS-2816:


Please submit a patch or create a review on reviewboard with suggested changes.

> Allow ignoring relationship in EntityGraphRetriever for FullTextMapperV2
> 
>
> Key: ATLAS-2816
> URL: https://issues.apache.org/jira/browse/ATLAS-2816
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Chengbing Liu
>Priority: Major
>
> We encountered a problem when using Hive bridge in production. One database 
> has 5000+ tables. Importing the first table costs only tens of milliseconds, 
> and then it becomes slower with more tables. In the end, it costs 1~2 seconds 
> to import one table.
> After investigation, we realized that it is not necessary for the 
> {{FullTextMapperV2}} to retrieve all the relationship of the database each 
> time a table is imported. The time complexity of importing a whole database 
> actually goes to O(n^2) (n is number of tables).
> We propose to add a parameter to the constructor of {{EntityGraphRetriever}}: 
> {{ignoreRelationship}}. When set to true, {{mapVertexToAtlasEntity}} will 
> skip the {{mapRelationshipAttributes}} call. Since {{FullTextMapperV2}} will 
> not use relationship attributes of the entity, this can save plenty of time 
> when importing entities with a large number of relations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Review Request 68270: Cluster Entity Updated after Successful Import if Replication Options are Available in Import Request

2018-08-08 Thread Apoorv Naik

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




repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphMapper.java
Lines 940 (patched)
<https://reviews.apache.org/r/68270/#comment290156>

Simplify double-negation to CollectionUtils.isEmpty



server-api/src/main/java/org/apache/atlas/RequestContextV1.java
Lines 138 (patched)
<https://reviews.apache.org/r/68270/#comment290158>

"this." is unnecessary here.



server-api/src/main/java/org/apache/atlas/RequestContextV1.java
Lines 141 (patched)
<https://reviews.apache.org/r/68270/#comment290159>

better variable name for "b"


- Apoorv Naik


On Aug. 8, 2018, 7:37 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68270/
> ---
> 
> (Updated Aug. 8, 2018, 7:37 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-2814
> https://issues.apache.org/jira/browse/ATLAS-2814
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> - New model _ReplicationDetails_ store replication timestamp.
> - _AuditWriter_ updates appropriate _AtlasCluster_ entity with 
> _ReplicationDetails_.
> 
> 
> Diffs
> -
> 
>   client/common/src/main/java/org/apache/atlas/AtlasBaseClient.java 
> f73ba2c6e6c9d05e86eb6c17f923a6dda1df5dd9 
>   intg/src/main/java/org/apache/atlas/model/clusterinfo/AtlasCluster.java 
> 3ce50e38b3af45521c2c83d0e6c05398747bcf86 
>   intg/src/main/java/org/apache/atlas/model/impexp/AtlasExportResult.java 
> 85a606c7d3b2158238b2a6defbb9185883434d78 
>   intg/src/main/java/org/apache/atlas/model/impexp/AtlasImportResult.java 
> bfb7637711e08e17fd5f5b16bf121ac541b631a4 
>   intg/src/main/java/org/apache/atlas/model/impexp/ReplicationDetails.java 
> PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/AuditsWriter.java 
> 6a3fbecda84dc48e0df1359c1b5a248958db0a4c 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/ClusterService.java
>  fd8e2bfe6bbdb7ae5e66ab67ecdf94e9527d9b09 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/ExportImportAuditService.java
>  e90b6b942d359f78ccf59ee955c4667f2033e6c4 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/ExportService.java
>  b15f828e470eaee972a4ee3f8447f404f813c699 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/ImportService.java
>  98ef389bd1bf8f87d23a06dc231d4d93f06b2231 
>   
> repository/src/main/java/org/apache/atlas/repository/ogm/AtlasClusterDTO.java 
> 424fb88a5ad2d84ac2245848d061892d40a3f50c 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphMapper.java
>  9e7a119a3abfb50401f9747dad1ffa55facc51ed 
>   
> repository/src/test/java/org/apache/atlas/repository/impexp/ClusterServiceTest.java
>  cfd272fb00a970ab0ba28f96b237de6bd5c694e1 
>   
> repository/src/test/java/org/apache/atlas/repository/impexp/ExportImportTestBase.java
>  fcf90d364950d3afa2c18689d8e22616cfcd3c19 
>   
> repository/src/test/java/org/apache/atlas/repository/impexp/ExportIncrementalTest.java
>  86ab22294918701270db3ba849f5b0532c1a21a4 
>   
> repository/src/test/java/org/apache/atlas/repository/impexp/ImportServiceTest.java
>  dc25e92d7115db31cbd7f99bd1a2cb5f75e766a5 
>   
> repository/src/test/java/org/apache/atlas/repository/impexp/ReplicationEntityAttributeTest.java
>  881368ce2c6803c8cf887a1fc91737c045c5e663 
>   server-api/src/main/java/org/apache/atlas/RequestContextV1.java 
> 8506d186978f579c6b18c4347fc7cb2636848f16 
>   webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 
> d4e72620b15f69d258e5a2a96521c65a7ef71114 
>   
> webapp/src/test/java/org/apache/atlas/web/resources/AdminExportImportTestIT.java
>  fc804d2e5a1debd7e728dca1773f91402d41fc26 
>   webapp/src/test/resources/json/export-incremental.json 
> 97108411f9e0c177ac13eb0a8ec3bd4475499f89 
>   webapp/src/test/resources/stocks-base.zip 
> 40c7f37eefb46a944921f6a74a916191704cb9a3 
> 
> 
> Diff: https://reviews.apache.org/r/68270/diff/1/
> 
> 
> Testing
> ---
> 
> **Unit tests**
> New tests added.
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>



Re: Review Request 68270: Cluster Entity Updated after Successful Import if Replication Options are Available in Import Request

2018-08-08 Thread Apoorv Naik

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




intg/src/main/java/org/apache/atlas/model/impexp/ReplicationDetails.java
Lines 21 (patched)
<https://reviews.apache.org/r/68270/#comment290155>

Wrong annotation. Use the non-shaded one


- Apoorv Naik


On Aug. 8, 2018, 7:37 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68270/
> ---
> 
> (Updated Aug. 8, 2018, 7:37 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-2814
> https://issues.apache.org/jira/browse/ATLAS-2814
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> - New model _ReplicationDetails_ store replication timestamp.
> - _AuditWriter_ updates appropriate _AtlasCluster_ entity with 
> _ReplicationDetails_.
> 
> 
> Diffs
> -
> 
>   client/common/src/main/java/org/apache/atlas/AtlasBaseClient.java 
> f73ba2c6e6c9d05e86eb6c17f923a6dda1df5dd9 
>   intg/src/main/java/org/apache/atlas/model/clusterinfo/AtlasCluster.java 
> 3ce50e38b3af45521c2c83d0e6c05398747bcf86 
>   intg/src/main/java/org/apache/atlas/model/impexp/AtlasExportResult.java 
> 85a606c7d3b2158238b2a6defbb9185883434d78 
>   intg/src/main/java/org/apache/atlas/model/impexp/AtlasImportResult.java 
> bfb7637711e08e17fd5f5b16bf121ac541b631a4 
>   intg/src/main/java/org/apache/atlas/model/impexp/ReplicationDetails.java 
> PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/AuditsWriter.java 
> 6a3fbecda84dc48e0df1359c1b5a248958db0a4c 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/ClusterService.java
>  fd8e2bfe6bbdb7ae5e66ab67ecdf94e9527d9b09 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/ExportImportAuditService.java
>  e90b6b942d359f78ccf59ee955c4667f2033e6c4 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/ExportService.java
>  b15f828e470eaee972a4ee3f8447f404f813c699 
>   
> repository/src/main/java/org/apache/atlas/repository/impexp/ImportService.java
>  98ef389bd1bf8f87d23a06dc231d4d93f06b2231 
>   
> repository/src/main/java/org/apache/atlas/repository/ogm/AtlasClusterDTO.java 
> 424fb88a5ad2d84ac2245848d061892d40a3f50c 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/EntityGraphMapper.java
>  9e7a119a3abfb50401f9747dad1ffa55facc51ed 
>   
> repository/src/test/java/org/apache/atlas/repository/impexp/ClusterServiceTest.java
>  cfd272fb00a970ab0ba28f96b237de6bd5c694e1 
>   
> repository/src/test/java/org/apache/atlas/repository/impexp/ExportImportTestBase.java
>  fcf90d364950d3afa2c18689d8e22616cfcd3c19 
>   
> repository/src/test/java/org/apache/atlas/repository/impexp/ExportIncrementalTest.java
>  86ab22294918701270db3ba849f5b0532c1a21a4 
>   
> repository/src/test/java/org/apache/atlas/repository/impexp/ImportServiceTest.java
>  dc25e92d7115db31cbd7f99bd1a2cb5f75e766a5 
>   
> repository/src/test/java/org/apache/atlas/repository/impexp/ReplicationEntityAttributeTest.java
>  881368ce2c6803c8cf887a1fc91737c045c5e663 
>   server-api/src/main/java/org/apache/atlas/RequestContextV1.java 
> 8506d186978f579c6b18c4347fc7cb2636848f16 
>   webapp/src/main/java/org/apache/atlas/web/resources/AdminResource.java 
> d4e72620b15f69d258e5a2a96521c65a7ef71114 
>   
> webapp/src/test/java/org/apache/atlas/web/resources/AdminExportImportTestIT.java
>  fc804d2e5a1debd7e728dca1773f91402d41fc26 
>   webapp/src/test/resources/json/export-incremental.json 
> 97108411f9e0c177ac13eb0a8ec3bd4475499f89 
>   webapp/src/test/resources/stocks-base.zip 
> 40c7f37eefb46a944921f6a74a916191704cb9a3 
> 
> 
> Diff: https://reviews.apache.org/r/68270/diff/1/
> 
> 
> Testing
> ---
> 
> **Unit tests**
> New tests added.
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>



[jira] [Created] (ATLAS-2817) Update to JanusGraph 0.3.x

2018-08-08 Thread Apoorv Naik (JIRA)
Apoorv Naik created ATLAS-2817:
--

 Summary: Update to JanusGraph 0.3.x
 Key: ATLAS-2817
 URL: https://issues.apache.org/jira/browse/ATLAS-2817
 Project: Atlas
  Issue Type: Improvement
Reporter: Apoorv Naik
Assignee: Apoorv Naik


There are couple of index related improvements in this version which helps 
resolve the slowness in few of our DSL queries. This upgrade would speed up DSL 
execution.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (ATLAS-2815) Slow UI load and REST improvement for entities with ownedRef

2018-08-07 Thread Apoorv Naik (JIRA)


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

Apoorv Naik commented on ATLAS-2815:


Awaiting build 
([https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/545/)]
 result.

> Slow UI load and REST improvement for entities with ownedRef
> 
>
> Key: ATLAS-2815
> URL: https://issues.apache.org/jira/browse/ATLAS-2815
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Abhishek Kadam
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 0.8.1, trunk, 1.1.0
>
> Attachments: ATLAS-2815.patch, ATLAS-2815_UI.patch
>
>
> The approach is to check if query param- 
> {color:#212121}*minExtInfo*:{color}*true* and the entity has schemaOptions, 
> then the server will send the attributes accordingly in referredEntities.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-2815) Slow UI load and REST improvement for entities with ownedRef

2018-08-07 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2815:
---
Issue Type: Improvement  (was: Bug)

> Slow UI load and REST improvement for entities with ownedRef
> 
>
> Key: ATLAS-2815
> URL: https://issues.apache.org/jira/browse/ATLAS-2815
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Abhishek Kadam
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 0.8.1, trunk, 1.1.0
>
> Attachments: ATLAS-2815.patch, ATLAS-2815_UI.patch
>
>
> The approach is to check if query param- 
> {color:#212121}*minExtInfo*:{color}*true* and the entity has schemaOptions, 
> then the server will send the attributes accordingly in referredEntities.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-2815) Slow UI load and REST improvement for entities with ownedRef

2018-08-07 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2815:
---
Summary: Slow UI load and REST improvement for entities with ownedRef  
(was: 'Properties' tab performance improvement )

> Slow UI load and REST improvement for entities with ownedRef
> 
>
> Key: ATLAS-2815
> URL: https://issues.apache.org/jira/browse/ATLAS-2815
> Project: Atlas
>  Issue Type: Bug
>Reporter: Abhishek Kadam
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 0.8.1, trunk, 1.1.0
>
> Attachments: ATLAS-2815.patch, ATLAS-2815_UI.patch
>
>
> The approach is to check if query param- 
> {color:#212121}*minExtInfo*:{color}*true* and the entity has schemaOptions, 
> then the server will send the attributes accordingly in referredEntities.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-2815) 'Properties' tab performance improvement

2018-08-07 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2815:
---
Fix Version/s: 1.1.0
   trunk

> 'Properties' tab performance improvement 
> -
>
> Key: ATLAS-2815
> URL: https://issues.apache.org/jira/browse/ATLAS-2815
> Project: Atlas
>  Issue Type: Bug
>Reporter: Abhishek Kadam
>Assignee: Abhishek Kadam
>Priority: Major
> Fix For: 0.8.1, trunk, 1.1.0
>
> Attachments: ATLAS-2815.patch, ATLAS-2815_UI.patch
>
>
> The approach is to check if query param- 
> {color:#212121}*minExtInfo*:{color}*true* and the entity has schemaOptions, 
> then the server will send the attributes accordingly in referredEntities.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (ATLAS-1957) MultiVertex graph query

2018-07-19 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-1957.

Resolution: Won't Do

> MultiVertex graph query
> ---
>
> Key: ATLAS-1957
> URL: https://issues.apache.org/jira/browse/ATLAS-1957
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: trunk
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Fix For: trunk
>
>
> There are lot of use cases where the graph query needs to be executed against 
> a given set of vertices, right now the only way to do it to first determine a 
> unique indexed attribute for those and then use that as the very first has 
> condition filter.
> e.g. graph.query().has("__guid", IN, Set guids)
> This makes it difficult to perform hops in the graph traversal using the 
> query API alone.
> Titan0 and Titan1 has the ability to perform queries on multiple vertices in 
> one go, which would benefit us in the future.
> This enhancement will track the implementation of the MultiVertexQuery 
> feature across Titan0 and Titan1



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (ATLAS-1958) Better graph traversal APIs

2018-07-19 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-1958.

Resolution: Won't Do

> Better graph traversal APIs 
> 
>
> Key: ATLAS-1958
> URL: https://issues.apache.org/jira/browse/ATLAS-1958
> Project: Atlas
>  Issue Type: Improvement
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
>
> Right now the only way to perform deep/complex graph traversals is through 
> the Gremlin API.
> Currently atlas has an ExpressionFactory abstraction which internally 
> generates groovy expression as per the compatible TinkerPop version. It 
> requires solid understanding of the TypeSystem, gremlin query structure, 
> required optimizations etc.
> Instead, TinkerPop itself supports a Gremlin pipeline (TP2) and a 
> GraphTraversal (TP3), which are good abstractions over the gremlin query 
> language. We should have a Querying abstraction in Atlas which is agnostic to 
> the underlying Graph implementation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-2786) [Atlas HA] Zookeeper connection issue

2018-07-17 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2786:
---
Fix Version/s: 1.1.0
   0.8.3
   trunk

> [Atlas HA] Zookeeper connection issue
> -
>
> Key: ATLAS-2786
> URL: https://issues.apache.org/jira/browse/ATLAS-2786
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.1, 0.8.2, 1.0.0
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Critical
> Fix For: trunk, 0.8.3, 1.1.0
>
> Attachments: 
> 0001-ATLAS-2786-Honor-ZK-server-ensemble-provided-in-conf.patch
>
>
> The curator client right now only connects to the very first zookeeper server 
> regardless of the number of zookeeper servers provided in the configuration.
>  
> Due to this behavior if the ZK (that Atlas connected to during startup) goes 
> down then Atlas fails to serve further request while constantly trying to 
> reconnect to the dead ZK server.
>  
> This patch makes the change in configuration parsing to allow fallback to 
> different ZK servers in case the primary goes down.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Review Request 67880: ATLAS-2786: Honor ZK server ensemble configuration

2018-07-10 Thread Apoorv Naik

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

Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, and Sarath 
Subramanian.


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


Repository: atlas


Description
---

Currently Atlas only connects to one ZK server even if configuration provides a 
ZK server cluster


Diffs
-

  common/src/main/java/org/apache/atlas/ha/HAConfiguration.java 7cfd553fb 


Diff: https://reviews.apache.org/r/67880/diff/1/


Testing
---

PreCommit on Master: 
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/515/
PreCommit on branch-1.0: 
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/516/
PreCommit on branch-0.8: 
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/517/


Thanks,

Apoorv Naik



[jira] [Created] (ATLAS-2786) [Atlas HA] Zookeeper connection issue

2018-07-10 Thread Apoorv Naik (JIRA)
Apoorv Naik created ATLAS-2786:
--

 Summary: [Atlas HA] Zookeeper connection issue
 Key: ATLAS-2786
 URL: https://issues.apache.org/jira/browse/ATLAS-2786
 Project: Atlas
  Issue Type: Improvement
Affects Versions: 1.0.0, 0.8.2, 0.8.1
Reporter: Apoorv Naik
Assignee: Apoorv Naik


The curator client right now only connects to the very first zookeeper server 
regardless of the number of zookeeper servers provided in the configuration.

 

Due to this behavior if the ZK (that Atlas connected to during startup) goes 
down then Atlas fails to serve further request while constantly trying to 
reconnect to the dead ZK server.

 

This patch makes the change in configuration parsing to allow fallback to 
different ZK servers in case the primary goes down.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-2786) [Atlas HA] Zookeeper connection issue

2018-07-10 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2786:
---
Issue Type: Bug  (was: Improvement)

> [Atlas HA] Zookeeper connection issue
> -
>
> Key: ATLAS-2786
> URL: https://issues.apache.org/jira/browse/ATLAS-2786
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.1, 0.8.2, 1.0.0
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Critical
>
> The curator client right now only connects to the very first zookeeper server 
> regardless of the number of zookeeper servers provided in the configuration.
>  
> Due to this behavior if the ZK (that Atlas connected to during startup) goes 
> down then Atlas fails to serve further request while constantly trying to 
> reconnect to the dead ZK server.
>  
> This patch makes the change in configuration parsing to allow fallback to 
> different ZK servers in case the primary goes down.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Atlas graph schema

2018-07-07 Thread Apoorv Naik
You can look at AtlasTypedefStoreV2, AtlasEntityStoreV2 for starting off. Also 
graphBackedSearchIndexer would be a good place to see how data is indexed .

Sent from Nine

From: Allen Cheng 
Sent: Saturday, July 7, 2018 5:57 PM
To: dev@atlas.apache.org
Subject: Atlas graph schema

Hi, Atlas experts

I am trying to learn a little about Atlas internals, (and wanted to
contribute to Atlas). I know Atlas stores data into a graph database.
Could you tell me where I can find Atlas's graph schema and model?  Is
there is documentation place where I can look?  Or if not, which code
module I can look into?

Regards,

Allen


[jira] [Resolved] (ATLAS-2780) Update AtlasAdminClient to accept username/password via cmdline

2018-07-05 Thread Apoorv Naik (JIRA)


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

Apoorv Naik resolved ATLAS-2780.

   Resolution: Fixed
Fix Version/s: 2.0.0
   1.1.0

> Update AtlasAdminClient to accept username/password via cmdline
> ---
>
> Key: ATLAS-2780
> URL: https://issues.apache.org/jira/browse/ATLAS-2780
> Project: Atlas
>  Issue Type: Improvement
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.1.0, 2.0.0
>
>
> Currently the code doesn't accept the username, password via cmdline options.
>  
> This change will allow a user to specify the combo using -u :



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Review Request 67837: Update AtlasAdminClient to accept credentials via cmdline

2018-07-05 Thread Apoorv Naik

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

(Updated July 5, 2018, 9:59 p.m.)


Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Nixon Rodrigues, 
and Sarath Subramanian.


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


Repository: atlas


Description
---

See JIRA


Diffs
-

  client/client-v1/src/main/java/org/apache/atlas/AtlasAdminClient.java 
f334f6c69 
  intg/src/main/java/org/apache/atlas/utils/AuthenticationUtil.java af32afccc 


Diff: https://reviews.apache.org/r/67837/diff/1/


Testing
---

Verified using the driver script and a direct run of AtlasAdminClient.main


Thanks,

Apoorv Naik



Review Request 67837: Update AtlasAdminClient to accept credentials via cmdline

2018-07-05 Thread Apoorv Naik

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

Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, Nixon Rodrigues, 
and Sarath Subramanian.


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


Repository: atlas


Description
---

See JIRA


Diffs
-

  client/client-v1/src/main/java/org/apache/atlas/AtlasAdminClient.java 
f334f6c69 
  intg/src/main/java/org/apache/atlas/utils/AuthenticationUtil.java af32afccc 


Diff: https://reviews.apache.org/r/67837/diff/1/


Testing
---

Verified using the driver script and a direct run of AtlasAdminClient.main


Thanks,

Apoorv Naik



[jira] [Created] (ATLAS-2780) Update AtlasAdminClient to accept username/password via cmdline

2018-07-05 Thread Apoorv Naik (JIRA)
Apoorv Naik created ATLAS-2780:
--

 Summary: Update AtlasAdminClient to accept username/password via 
cmdline
 Key: ATLAS-2780
 URL: https://issues.apache.org/jira/browse/ATLAS-2780
 Project: Atlas
  Issue Type: Improvement
Reporter: Apoorv Naik
Assignee: Apoorv Naik


Currently the code doesn't accept the username, password via cmdline options.

 

This change will allow a user to specify the combo using -u :



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Review Request 67605: ATLAS-2757: fix for NPE in Hive hook in handling column-rename on temporary table

2018-06-14 Thread Apoorv Naik

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


Ship it!




Ship It!

- Apoorv Naik


On June 14, 2018, 11:04 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67605/
> ---
> 
> (Updated June 14, 2018, 11:04 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, Nixon Rodrigues, 
> Ramesh Mani, Ruchi Solani, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2757
> https://issues.apache.org/jira/browse/ATLAS-2757
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Updated Hive hook to address NPE while processing column-rename on temporary 
> table
> 
> 
> Diffs
> -
> 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/events/AlterTableRenameCol.java
>  60aea9456 
> 
> 
> Diff: https://reviews.apache.org/r/67605/diff/1/
> 
> 
> Testing
> ---
> 
> Verified that Hive hook processes column-rename on  temporarary table 
> successfully.
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>



Review Request 67492: ATLAS-2746: Term/Category creation doesn't need Entity.UPDATE privilege for simple cases.

2018-06-07 Thread Apoorv Naik

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

Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, and Sarath 
Subramanian.


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


Repository: atlas


Description
---

See JIRA


Diffs
-

  repository/src/main/java/org/apache/atlas/glossary/GlossaryCategoryUtils.java 
be2f16e9d 
  repository/src/main/java/org/apache/atlas/glossary/GlossaryService.java 
ff5aa6ea7 
  repository/src/main/java/org/apache/atlas/glossary/GlossaryTermUtils.java 
4d65328ca 


Diff: https://reviews.apache.org/r/67492/diff/1/


Testing
---

PreCommit: 
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/468/


Thanks,

Apoorv Naik



[jira] [Updated] (ATLAS-2746) [Glossary] Simple Term/Category creation should work with CREATE privilege

2018-06-07 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2746:
---
Fix Version/s: 1.0.0
   trunk

> [Glossary] Simple Term/Category creation should work with CREATE privilege
> --
>
> Key: ATLAS-2746
> URL: https://issues.apache.org/jira/browse/ATLAS-2746
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0, trunk
>
>
> Currently this operation needs following privileges
>  
> Entity.READ, Entity.CREATE, Entity.UPDATE
>  
> with the change simple term/category creation without any other relations 
> e.g. children, parent, categorized terms etc. can work with
>  
> Entity.READ and Entity.CREATE



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ATLAS-2746) [Glossary] Simple Term/Category creation should work with CREATE privilege

2018-06-07 Thread Apoorv Naik (JIRA)
Apoorv Naik created ATLAS-2746:
--

 Summary: [Glossary] Simple Term/Category creation should work with 
CREATE privilege
 Key: ATLAS-2746
 URL: https://issues.apache.org/jira/browse/ATLAS-2746
 Project: Atlas
  Issue Type: Improvement
Reporter: Apoorv Naik
Assignee: Apoorv Naik


Currently this operation needs following privileges

 

Entity.READ, Entity.CREATE, Entity.UPDATE

 

with the change simple term/category creation without any other relations e.g. 
children, parent, categorized terms etc. can work with

 

Entity.READ and Entity.CREATE



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (ATLAS-2746) [Glossary] Simple Term/Category creation should work with CREATE privilege

2018-06-07 Thread Apoorv Naik (JIRA)


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

Apoorv Naik updated ATLAS-2746:
---
Affects Version/s: 1.0.0

> [Glossary] Simple Term/Category creation should work with CREATE privilege
> --
>
> Key: ATLAS-2746
> URL: https://issues.apache.org/jira/browse/ATLAS-2746
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0, trunk
>
>
> Currently this operation needs following privileges
>  
> Entity.READ, Entity.CREATE, Entity.UPDATE
>  
> with the change simple term/category creation without any other relations 
> e.g. children, parent, categorized terms etc. can work with
>  
> Entity.READ and Entity.CREATE



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (ATLAS-2520) Use JanusGraph traversal over gremlin script

2018-06-05 Thread Apoorv Naik (JIRA)


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

Apoorv Naik commented on ATLAS-2520:


Initial code changes show tremendous improvement in DSL execution.

For the DSLQueriesTest suite the (best case) numbers

TP2: 90s

TP3: 25s

> Use JanusGraph traversal over gremlin script 
> -
>
> Key: ATLAS-2520
> URL: https://issues.apache.org/jira/browse/ATLAS-2520
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0-alpha
>    Reporter: Apoorv Naik
>    Assignee: Apoorv Naik
>Priority: Major
> Attachments: Screen Shot 2018-06-05 at 6.16.42 PM.png, Screen Shot 
> 2018-06-05 at 6.19.33 PM.png
>
>
> Currently lot of code in Atlas follow a concept of GremlinQueryProvider which 
> gives TP2 and TP3 queries depending on the graph backend being used. Since 
> Atlas 1.0 is primarily going to rely on JanusGraph, it makes a more sense to 
> remove TP2 related queries/abstractions and use the GraphTraversal Java API 
> provided by JanusGraph.
>  
> PRO: Lot of unused code can be removed, more expressive Graph 
> querying/traversal.
> CONS: Decommissioning TP2 completely is a major engineering effort



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


  1   2   3   4   5   6   7   >