Re: Review Request 36359: Create configuration properties for HTTP and HTTPS server ports

[Jonathan Maron]

> On July 13, 2015, 10:48 a.m., Shwetha GS wrote:
> > For hive hook, there is a config:
> > 
> >   atlas.rest.address
> >   http://localhost:21000/
> > 
> > 
> > 
> > Can we use the same config to check if its ssl or not, get the port and 
> > also bind to an address?
> 
> Jonathan Maron wrote:
> We might be able to do that, but from a management interface it may not 
> be ideal and would probably run contrary to the way in which users expect to 
> manage the assignment of ports (see yarn and hdfs as examples).  I think it 
> is preferable to have persisted values for each transport type since that is 
> a familiar and well-understood mechanism for configuration in a Hadoop 
> cluster.
> 
> Shwetha GS wrote:
> Even hdfs and yarn use the full endpoint configuration to bind the port
>  
> The address of the applications manager interface in the 
> RM.
> yarn.resourcemanager.address
> ${yarn.resourcemanager.hostname}:8032
>   
>   
> The hostname of the RM.
> yarn.resourcemanager.hostname
> 0.0.0.0
>   

I was talking specifically about the pattern of enabling SSL via a flag (which 
we do), and defining an associated port, much like HDFS, for example:


  dfs.http.policy
  HTTPS_ONLY



  dfs.https.port
  50470


Given the time differences and its effect on reviews (this simple change has 
now been in review for 6 days) I think that:

1)  This is probably not a valid issue to prolong this review
2)  If users complain we can certainly address a change of the approach with a 
subsequent JIRA.

I will therefore proceed with a commit.


- Jonathan


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


On July 9, 2015, 6:06 p.m., Jonathan Maron wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/36359/
> ---
> 
> (Updated July 9, 2015, 6:06 p.m.)
> 
> 
> Review request for atlas, Arpit Gupta and Seetharam Venkatesh.
> 
> 
> Bugs: ATLAS-36
> https://issues.apache.org/jira/browse/ATLAS-36
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Distinct HTTP and HTTPS persisted port properties will make the configuration 
> clearer and allow for a better experience from management interfaces such as 
> Ambari.
> 
> 
> Diffs
> -
> 
>   src/conf/application.properties 6c4c7d2 
>   webapp/src/main/java/org/apache/atlas/Main.java 1dd17b4 
>   webapp/src/test/java/org/apache/atlas/MainIT.java PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/36359/diff/
> 
> 
> Testing
> ---
> 
> Installed a local server and observed the configuration properties working.
> Added a unit test for port selection logic (MainIT).
> 
> 
> Thanks,
> 
> Jonathan Maron
> 
>

Re: Review Request 36359: Create configuration properties for HTTP and HTTPS server ports

[Shwetha GS]

> On July 13, 2015, 10:48 a.m., Shwetha GS wrote:
> > For hive hook, there is a config:
> > 
> >   atlas.rest.address
> >   http://localhost:21000/
> > 
> > 
> > 
> > Can we use the same config to check if its ssl or not, get the port and 
> > also bind to an address?
> 
> Jonathan Maron wrote:
> We might be able to do that, but from a management interface it may not 
> be ideal and would probably run contrary to the way in which users expect to 
> manage the assignment of ports (see yarn and hdfs as examples).  I think it 
> is preferable to have persisted values for each transport type since that is 
> a familiar and well-understood mechanism for configuration in a Hadoop 
> cluster.
> 
> Shwetha GS wrote:
> Even hdfs and yarn use the full endpoint configuration to bind the port
>  
> The address of the applications manager interface in the 
> RM.
> yarn.resourcemanager.address
> ${yarn.resourcemanager.hostname}:8032
>   
>   
> The hostname of the RM.
> yarn.resourcemanager.hostname
> 0.0.0.0
>   
> 
> Jonathan Maron wrote:
> I was talking specifically about the pattern of enabling SSL via a flag 
> (which we do), and defining an associated port, much like HDFS, for example:
> 
> 
>   dfs.http.policy
>   HTTPS_ONLY
> 
> 
> 
>   dfs.https.port
>   50470
> 
> 
> Given the time differences and its effect on reviews (this simple change 
> has now been in review for 6 days) I think that:
> 
> 1)  This is probably not a valid issue to prolong this review
> 2)  If users complain we can certainly address a change of the approach 
> with a subsequent JIRA.
> 
> I will therefore proceed with a commit.

I guess the reason it has this config is because it hosts server on both http 
and https at the same time. For our case, we enabled either http or https, it 
makes sense to read from url. Will create another bug


- Shwetha


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


On July 9, 2015, 6:06 p.m., Jonathan Maron wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/36359/
> ---
> 
> (Updated July 9, 2015, 6:06 p.m.)
> 
> 
> Review request for atlas, Arpit Gupta and Seetharam Venkatesh.
> 
> 
> Bugs: ATLAS-36
> https://issues.apache.org/jira/browse/ATLAS-36
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Distinct HTTP and HTTPS persisted port properties will make the configuration 
> clearer and allow for a better experience from management interfaces such as 
> Ambari.
> 
> 
> Diffs
> -
> 
>   src/conf/application.properties 6c4c7d2 
>   webapp/src/main/java/org/apache/atlas/Main.java 1dd17b4 
>   webapp/src/test/java/org/apache/atlas/MainIT.java PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/36359/diff/
> 
> 
> Testing
> ---
> 
> Installed a local server and observed the configuration properties working.
> Added a unit test for port selection logic (MainIT).
> 
> 
> Thanks,
> 
> Jonathan Maron
> 
>

Re: Review Request 36359: Create configuration properties for HTTP and HTTPS server ports

[Suma Shivaprasad]

> On July 10, 2015, 5:05 p.m., Suma Shivaprasad wrote:
> > webapp/src/main/java/org/apache/atlas/Main.java, line 103
> > 
> >
> > Could remove protected to make it package private. Dont get what a 
> > protected static method means.
> 
> Jonathan Maron wrote:
> I'm not sure about the qualifier either, but making it protected enabled 
> a better testing approach and didn't seem to expose the internals in a 
> detrimental way.
> 
> Jonathan Maron wrote:
> Actually, I imagine "protected" means that the method can be statically 
> invoked from child classes or from within the same package.

Since we need the method only in MainIT, the test which is in same package, we 
can drop the protected and make it 
static int getApplicationPort(CommandLine cmd, IMO. No need to have 
protected.


- Suma


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


On July 9, 2015, 6:06 p.m., Jonathan Maron wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/36359/
> ---
> 
> (Updated July 9, 2015, 6:06 p.m.)
> 
> 
> Review request for atlas, Arpit Gupta and Seetharam Venkatesh.
> 
> 
> Bugs: ATLAS-36
> https://issues.apache.org/jira/browse/ATLAS-36
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Distinct HTTP and HTTPS persisted port properties will make the configuration 
> clearer and allow for a better experience from management interfaces such as 
> Ambari.
> 
> 
> Diffs
> -
> 
>   src/conf/application.properties 6c4c7d2 
>   webapp/src/main/java/org/apache/atlas/Main.java 1dd17b4 
>   webapp/src/test/java/org/apache/atlas/MainIT.java PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/36359/diff/
> 
> 
> Testing
> ---
> 
> Installed a local server and observed the configuration properties working.
> Added a unit test for port selection logic (MainIT).
> 
> 
> Thanks,
> 
> Jonathan Maron
> 
>

Re: Review Request 36359: Create configuration properties for HTTP and HTTPS server ports

[Jonathan Maron]

> On July 10, 2015, 5:05 p.m., Suma Shivaprasad wrote:
> > webapp/src/main/java/org/apache/atlas/Main.java, line 103
> > 
> >
> > Could remove protected to make it package private. Dont get what a 
> > protected static method means.
> 
> Jonathan Maron wrote:
> I'm not sure about the qualifier either, but making it protected enabled 
> a better testing approach and didn't seem to expose the internals in a 
> detrimental way.
> 
> Jonathan Maron wrote:
> Actually, I imagine "protected" means that the method can be statically 
> invoked from child classes or from within the same package.
> 
> Suma Shivaprasad wrote:
> Since we need the method only in MainIT, the test which is in same 
> package, we can drop the protected and make it 
> static int getApplicationPort(CommandLine cmd, IMO. No need to have 
> protected.

Fine.


- Jonathan


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


On July 9, 2015, 6:06 p.m., Jonathan Maron wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/36359/
> ---
> 
> (Updated July 9, 2015, 6:06 p.m.)
> 
> 
> Review request for atlas, Arpit Gupta and Seetharam Venkatesh.
> 
> 
> Bugs: ATLAS-36
> https://issues.apache.org/jira/browse/ATLAS-36
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Distinct HTTP and HTTPS persisted port properties will make the configuration 
> clearer and allow for a better experience from management interfaces such as 
> Ambari.
> 
> 
> Diffs
> -
> 
>   src/conf/application.properties 6c4c7d2 
>   webapp/src/main/java/org/apache/atlas/Main.java 1dd17b4 
>   webapp/src/test/java/org/apache/atlas/MainIT.java PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/36359/diff/
> 
> 
> Testing
> ---
> 
> Installed a local server and observed the configuration properties working.
> Added a unit test for port selection logic (MainIT).
> 
> 
> Thanks,
> 
> Jonathan Maron
> 
>

Jenkins build is back to stable : apache-atlas-nightly #27

[Apache Jenkins Server]

See 

Jenkins build is still unstable: apache-atlas-nightly #26

[Apache Jenkins Server]

See 

[jira] [Created] (ATLAS-72) Use atlas.rest.address on server

[Shwetha G S (JIRA)]

Shwetha G S created ATLAS-72:


 Summary: Use atlas.rest.address on server
 Key: ATLAS-72
 URL: https://issues.apache.org/jira/browse/ATLAS-72
 Project: Atlas
  Issue Type: Improvement
Reporter: Shwetha G S


On server, there are separate configs for should enable ssl, and port. Instead, 
it can use the client side config atlas.rest.address to derive ssl, port and 
host to bind to



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

[jira] [Created] (ATLAS-71) define an API for allowing the registration of a metrics handler (sink)

[Jonathan Maron (JIRA)]

Jonathan Maron created ATLAS-71:
---

 Summary: define an API for allowing the registration of a metrics 
handler (sink)
 Key: ATLAS-71
 URL: https://issues.apache.org/jira/browse/ATLAS-71
 Project: Atlas
  Issue Type: Task
Reporter: Jonathan Maron


A mechanism is required to be defined for registration of a metrics handler 
that can be leveraged by metrics collection systems such as AMS.



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

[jira] [Created] (ATLAS-70) Metrics need to be defined and published to enhance atlas service management

[Jonathan Maron (JIRA)]

Jonathan Maron created ATLAS-70:
---

 Summary: Metrics need to be defined and published to enhance atlas 
service management
 Key: ATLAS-70
 URL: https://issues.apache.org/jira/browse/ATLAS-70
 Project: Atlas
  Issue Type: Improvement
Reporter: Jonathan Maron


The metrics that make sense for understanding the operational health and status 
of the atlas server need to be defined and published using appropriate APIs etc.



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

Re: Falcon

[Suma Shivaprasad]

Hi Nigel,

Yes the Falcon plugin was removed since it was not yet mature. Only HIve
plugin is available as of now.There is work in progress to make these
plugins reliable - https://issues.apache.org/jira/browse/ATLAS-58
The plan is to work on Storm and Kafka plugins next. Falcon is not yet
planned for the near term.

Have raised an  issue for Falcon plugin -
https://issues.apache.org/jira/browse/ATLAS-69. You are welcome to take up
if you are interested.

Thanks
Suma


On Tue, Jul 14, 2015 at 8:53 PM, Nigel Jones  wrote:

> In the current atlas code I see Hive plugins, but the Falcon plugin that
> was present in the 0.1 code preview is no longer present.
>
> Is only Hive available for now?
> Is there an expectation that Falcon will reappear in the near term?
> Are any further plugins being tracked in Jira (I couldn't see any)?
>
> Many thanks
> Nigel.
>
>

[jira] [Created] (ATLAS-69) Falcon Plugin for Atlas

[Suma Shivaprasad (JIRA)]

Suma Shivaprasad created ATLAS-69:
-

 Summary: Falcon Plugin for Atlas
 Key: ATLAS-69
 URL: https://issues.apache.org/jira/browse/ATLAS-69
 Project: Atlas
  Issue Type: New Feature
Reporter: Suma Shivaprasad


Add a falcon plugin to consume falcon entities like cluster, feed, process into 
ATLAS.



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

Falcon

[Nigel Jones]

In the current atlas code I see Hive plugins, but the Falcon plugin that 
was present in the 0.1 code preview is no longer present.


Is only Hive available for now?
Is there an expectation that Falcon will reappear in the near term?
Are any further plugins being tracked in Jira (I couldn't see any)?

Many thanks
Nigel.

[jira] [Commented] (ATLAS-46) Different data directory with restart

[Shwetha G S (JIRA)]

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

Shwetha G S commented on ATLAS-46:
--

commons-configuration doesn't support variables in property files yet. Hence 
setting user.dir to the atlas package directory

> Different data directory with restart
> -
>
> Key: ATLAS-46
> URL: https://issues.apache.org/jira/browse/ATLAS-46
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Critical
> Fix For: trunk
>
> Attachments: ATLAS-46.patch, application.log
>
>
> Atlas start picks up different data directories - initially 
> ./server/webapp/atlas/data and after restart ./data. This must be because of 
> relative path in the configuration
> {noformat}
> apache-atlas-0.6-incubating-SNAPSHOT$ ps -ef | grep -i atlas
>   504  6437 1   0 11:51AM ttys0000:07.66 
> /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin/java 
> -Datlas.log.dir=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/logs
>  -Datlas.log.file=application.log 
> -Datlas.home=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT
>  
> -Datlas.conf=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf
>  -Xmx1024m -classpath 
> /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/classes:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/lib/*:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/libext/*
>  org.apache.atlas.Main -app 
> /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas
> apache-atlas-0.6-incubating-SNAPSHOT$ find . -name data
> ./server/webapp/atlas/data
> ./server/webapp/atlas/data/es/data
> ./server/webapp/atlas/lib/jquery/src/data
> apache-atlas-0.6-incubating-SNAPSHOT$ ./bin/atlas_stop.py
> apache-atlas-0.6-incubating-SNAPSHOT$ ps -ef | grep atlas
>   504  6457 1   0 11:54AM ttys0000:07.50 
> /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin/java 
> -Datlas.log.dir=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/logs
>  -Datlas.log.file=application.log 
> -Datlas.home=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT
>  
> -Datlas.conf=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf
>  -Xmx1024m -classpath 
> /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/classes:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/lib/*:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/libext/*
>  org.apache.atlas.Main -app 
> /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas
> apache-atlas-0.6-incubating-SNAPSHOT$ find . -name data
> ./data
> ./data/es/data
> ./server/webapp/atlas/data
> ./server/webapp/atlas/data/es/data
> ./server/webapp/atlas/lib/jquery/src/data
> {noformat}



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

[jira] [Updated] (ATLAS-46) Different data directory with restart

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-46:
-
Attachment: ATLAS-46.patch

> Different data directory with restart
> -
>
> Key: ATLAS-46
> URL: https://issues.apache.org/jira/browse/ATLAS-46
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Critical
> Fix For: trunk
>
> Attachments: ATLAS-46.patch, application.log
>
>
> Atlas start picks up different data directories - initially 
> ./server/webapp/atlas/data and after restart ./data. This must be because of 
> relative path in the configuration
> {noformat}
> apache-atlas-0.6-incubating-SNAPSHOT$ ps -ef | grep -i atlas
>   504  6437 1   0 11:51AM ttys0000:07.66 
> /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin/java 
> -Datlas.log.dir=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/logs
>  -Datlas.log.file=application.log 
> -Datlas.home=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT
>  
> -Datlas.conf=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf
>  -Xmx1024m -classpath 
> /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/classes:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/lib/*:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/libext/*
>  org.apache.atlas.Main -app 
> /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas
> apache-atlas-0.6-incubating-SNAPSHOT$ find . -name data
> ./server/webapp/atlas/data
> ./server/webapp/atlas/data/es/data
> ./server/webapp/atlas/lib/jquery/src/data
> apache-atlas-0.6-incubating-SNAPSHOT$ ./bin/atlas_stop.py
> apache-atlas-0.6-incubating-SNAPSHOT$ ps -ef | grep atlas
>   504  6457 1   0 11:54AM ttys0000:07.50 
> /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin/java 
> -Datlas.log.dir=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/logs
>  -Datlas.log.file=application.log 
> -Datlas.home=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT
>  
> -Datlas.conf=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf
>  -Xmx1024m -classpath 
> /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/classes:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/lib/*:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/libext/*
>  org.apache.atlas.Main -app 
> /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas
> apache-atlas-0.6-incubating-SNAPSHOT$ find . -name data
> ./data
> ./data/es/data
> ./server/webapp/atlas/data
> ./server/webapp/atlas/data/es/data
> ./server/webapp/atlas/lib/jquery/src/data
> {noformat}



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

[jira] [Assigned] (ATLAS-46) Different data directory with restart

[Shwetha G S (JIRA)]

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

Shwetha G S reassigned ATLAS-46:


Assignee: Shwetha G S

> Different data directory with restart
> -
>
> Key: ATLAS-46
> URL: https://issues.apache.org/jira/browse/ATLAS-46
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>Priority: Critical
> Fix For: trunk
>
> Attachments: ATLAS-46.patch, application.log
>
>
> Atlas start picks up different data directories - initially 
> ./server/webapp/atlas/data and after restart ./data. This must be because of 
> relative path in the configuration
> {noformat}
> apache-atlas-0.6-incubating-SNAPSHOT$ ps -ef | grep -i atlas
>   504  6437 1   0 11:51AM ttys0000:07.66 
> /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin/java 
> -Datlas.log.dir=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/logs
>  -Datlas.log.file=application.log 
> -Datlas.home=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT
>  
> -Datlas.conf=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf
>  -Xmx1024m -classpath 
> /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/classes:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/lib/*:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/libext/*
>  org.apache.atlas.Main -app 
> /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas
> apache-atlas-0.6-incubating-SNAPSHOT$ find . -name data
> ./server/webapp/atlas/data
> ./server/webapp/atlas/data/es/data
> ./server/webapp/atlas/lib/jquery/src/data
> apache-atlas-0.6-incubating-SNAPSHOT$ ./bin/atlas_stop.py
> apache-atlas-0.6-incubating-SNAPSHOT$ ps -ef | grep atlas
>   504  6457 1   0 11:54AM ttys0000:07.50 
> /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin/java 
> -Datlas.log.dir=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/logs
>  -Datlas.log.file=application.log 
> -Datlas.home=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT
>  
> -Datlas.conf=/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf
>  -Xmx1024m -classpath 
> /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/conf:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/classes:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas/WEB-INF/lib/*:/Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/libext/*
>  org.apache.atlas.Main -app 
> /Users/sshivalingamurthy/git/atlas-clone/target/apache-atlas-0.6-incubating-SNAPSHOT/server/webapp/atlas
> apache-atlas-0.6-incubating-SNAPSHOT$ find . -name data
> ./data
> ./data/es/data
> ./server/webapp/atlas/data
> ./server/webapp/atlas/data/es/data
> ./server/webapp/atlas/lib/jquery/src/data
> {noformat}



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

[jira] [Commented] (ATLAS-61) Inconsistent metadata content

[Shwetha G S (JIRA)]

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

Shwetha G S commented on ATLAS-61:
--

Atlas uses different data directories with restart. More details at ATLAS-46. 
That might be the reason for getting more types

> Inconsistent metadata content
> -
>
> Key: ATLAS-61
> URL: https://issues.apache.org/jira/browse/ATLAS-61
> Project: Atlas
>  Issue Type: Bug
>Reporter: David Kaspar
> Attachments: application.log
>
>
> Steps to reproduce:
> build Atlas binaries and install it to a fresh directory (aka in untar the 
> binary artifact to new/empty directory) and run:
> {code}
> apache-atlas-0.6-incubating-SNAPSHOT/bin/atlas_start.sh
> sleep 30
> curl http://127.0.0.1:21000/api/atlas/types
> # it prints: 
> {"results":["Process","Infrastructure","DataSet"],"count":3,"requestId":"1244107514@qtp-1475081618-0
>  - 4ced54d8-a726-4384-8e97-3f3d5535d307"}
> apache-atlas-0.6-incubating-SNAPSHOT/bin/atlas_stop.sh
> apache-atlas-0.6-incubating-SNAPSHOT/bin/atlas_start.sh
> sleep 30
> curl http://127.0.0.1:21000/api/atlas/types
> # it prints: 
> {"results":["hive_function_type","hive_index","Process","hive_column","hive_serde","hive_function","hive_resourceuri","hive_table","hive_storagedesc","hive_principal_type","hive_process","hive_resource_type","hive_type","hive_object_type","Infrastructure","hive_order","hive_role","DataSet","hive_partition","hive_db"],"count":20,"requestId":"500065027@qtp-1586292005-0
>  - 22906b64-8c9e-4f1d-97b6-6eadf2a71bbf"}
> {code}
> Note that I have not been load any types - I just started, stopped and then 
> started the atlas again and it printed inconsistent types.



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