subject:"building Atlas"

Re: building Atlas

2023-06-13 Thread Pierre Smits

Hi Nixon,

Thank you very much. That did it.

Met vriendelijke groet,

Pierre Smits
*Proud* *contributor** of* Apache OFBiz  since
2008 (without privileges)
Proud contributor to the ASF since 2006
*Apache Directory , PMC Member*

Anyone could have been you, whereas I've always been anyone.


On Fri, Jun 9, 2023 at 10:19 AM Nixon Rodrigues  wrote:

> Pierre,
>
> you can apply this fix and try.
>
> https://github.com/apache/atlas/pull/219/files
>
> On Wed, 7 Jun 2023 at 19:52, Pierre Smits  wrote:
>
> > Hi all,
> >
> > In a goal to implement Atlas in my private dev environment, I downloaded
> > the file re 2.3.0 and started the build with:
> >
> > mvn clean -DskipTests install
> >
> >
> > However, it didn't complete. The error I got was:
> >
> > [*ERROR*] Failed to execute goal on project atlas-testtools: *Could not
> > resolve dependencies for project
> > org.apache.atlas:atlas-testtools:jar:2.3.0: Failed to collect
> dependencies
> > at org.apache.solr:solr-test-framework:jar:8.6.3 ->
> > org.restlet.jee:org.restlet:jar:2.4.3*: Failed to read artifact
> descriptor
> > for org.restlet.jee:org.restlet:jar:2.4.3: Could not transfer artifact
> > org.restlet.jee:org.restlet:pom:2.4.3 from/to maven-restlet (
> > https://maven.restlet.com): Transfer failed for
> >
> >
> https://maven.restlet.com/org/restlet/jee/org.restlet/2.4.3/org.restlet-2.4.3.pom
> > :
> > PKIX path validation failed:
> java.security.cert.CertPathValidatorException:
> > validity check failed: NotAfter: Sun Nov 13 17:05:56 UTC 2022 -> *[Help
> 1]*
> >
> > Is there a way to correct, circumvent this?
> >
> > Any help would be greatly appreciated
> >
> >
> > Met vriendelijke groet,
> >
> > Pierre Smits
> > *Proud* *contributor** of* Apache OFBiz 
> since
> > 2008 (without privileges)
> > Proud contributor to the ASF since 2006
> > *Apache Directory , PMC Member*
> >
> > Anyone could have been you, whereas I've always been anyone.
> >
>

Re: building Atlas

2023-06-09 Thread Nixon Rodrigues

Pierre,

you can apply this fix and try.

https://github.com/apache/atlas/pull/219/files

On Wed, 7 Jun 2023 at 19:52, Pierre Smits  wrote:

> Hi all,
>
> In a goal to implement Atlas in my private dev environment, I downloaded
> the file re 2.3.0 and started the build with:
>
> mvn clean -DskipTests install
>
>
> However, it didn't complete. The error I got was:
>
> [*ERROR*] Failed to execute goal on project atlas-testtools: *Could not
> resolve dependencies for project
> org.apache.atlas:atlas-testtools:jar:2.3.0: Failed to collect dependencies
> at org.apache.solr:solr-test-framework:jar:8.6.3 ->
> org.restlet.jee:org.restlet:jar:2.4.3*: Failed to read artifact descriptor
> for org.restlet.jee:org.restlet:jar:2.4.3: Could not transfer artifact
> org.restlet.jee:org.restlet:pom:2.4.3 from/to maven-restlet (
> https://maven.restlet.com): Transfer failed for
>
> https://maven.restlet.com/org/restlet/jee/org.restlet/2.4.3/org.restlet-2.4.3.pom
> :
> PKIX path validation failed: java.security.cert.CertPathValidatorException:
> validity check failed: NotAfter: Sun Nov 13 17:05:56 UTC 2022 -> *[Help 1]*
>
> Is there a way to correct, circumvent this?
>
> Any help would be greatly appreciated
>
>
> Met vriendelijke groet,
>
> Pierre Smits
> *Proud* *contributor** of* Apache OFBiz  since
> 2008 (without privileges)
> Proud contributor to the ASF since 2006
> *Apache Directory , PMC Member*
>
> Anyone could have been you, whereas I've always been anyone.
>

building Atlas

2023-06-07 Thread Pierre Smits

Hi all,

In a goal to implement Atlas in my private dev environment, I downloaded
the file re 2.3.0 and started the build with:

mvn clean -DskipTests install


However, it didn't complete. The error I got was:

[*ERROR*] Failed to execute goal on project atlas-testtools: *Could not
resolve dependencies for project
org.apache.atlas:atlas-testtools:jar:2.3.0: Failed to collect dependencies
at org.apache.solr:solr-test-framework:jar:8.6.3 ->
org.restlet.jee:org.restlet:jar:2.4.3*: Failed to read artifact descriptor
for org.restlet.jee:org.restlet:jar:2.4.3: Could not transfer artifact
org.restlet.jee:org.restlet:pom:2.4.3 from/to maven-restlet (
https://maven.restlet.com): Transfer failed for
https://maven.restlet.com/org/restlet/jee/org.restlet/2.4.3/org.restlet-2.4.3.pom:
PKIX path validation failed: java.security.cert.CertPathValidatorException:
validity check failed: NotAfter: Sun Nov 13 17:05:56 UTC 2022 -> *[Help 1]*

Is there a way to correct, circumvent this?

Any help would be greatly appreciated


Met vriendelijke groet,

Pierre Smits
*Proud* *contributor** of* Apache OFBiz  since
2008 (without privileges)
Proud contributor to the ASF since 2006
*Apache Directory , PMC Member*

Anyone could have been you, whereas I've always been anyone.

Re: Review Request 74375: ATLAS-4740: enable building Atlas using JDK versions higher than 8

2023-04-05 Thread Sarath Subramanian


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


Ship it!




Ship It!

- Sarath Subramanian


On March 30, 2023, 3:06 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74375/
> ---
> 
> (Updated March 30, 2023, 3:06 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Jayendra Parab, Pinal Shah, Sarath 
> Subramanian, and Sidharth Mishra.
> 
> 
> Bugs: ATLAS-4740
> https://issues.apache.org/jira/browse/ATLAS-4740
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> added build properties to generate binaries for 1.8
> 
> 
> Diffs
> -
> 
>   pom.xml 15aa57bc4 
> 
> 
> Diff: https://reviews.apache.org/r/74375/diff/1/
> 
> 
> Testing
> ---
> 
> pre-commit build and test run: 
> https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1335/
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Review Request 74375: ATLAS-4740: enable building Atlas using JDK versions higher than 8

2023-03-30 Thread Madhan Neethiraj


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

Review request for atlas, Ashutosh Mestry, Jayendra Parab, Pinal Shah, Sarath 
Subramanian, and Sidharth Mishra.


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


Repository: atlas


Description
---

added build properties to generate binaries for 1.8


Diffs
-

  pom.xml 15aa57bc4 


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


Testing
---

pre-commit build and test run: 
https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1335/


Thanks,

Madhan Neethiraj

Building Atlas from source

2019-10-29 Thread Juho Autio

Hello!

I wanted to build the current branch-2.0 of Atlas but it didn't work
simply by following the Build Process of README.txt.

The reason for wanting to build from source is that
spark-atlas-connector recommends using Atlas 2.1.0 (
https://github.com/hortonworks-spark/spark-atlas-connector#create-atlas-models
), but I couldn't find such release. Not released yet?

So, to build Atlas from source I tried:

mvn clean install

..but it failed with errors like:

[ERROR] Failed to execute goal on project atlas-testtools: Could
not resolve dependencies for project
org.apache.atlas:atlas-testtools:jar:2.1.0-SNAPSHOT: The following
artifacts could not be resolved:
org.restlet.jee:org.restlet:jar:2.3.0,
org.restlet.jee:org.restlet.ext.servlet:jar:2.3.0: Could not find
artifact org.restlet.jee:org.restlet:jar:2.3.0 in central
(https://repo1.maven.org/maven2) -> [Help 1]

This way I got a bit further with the build:

mvn -s ~/.m2/settings-apache-atlas.xml clean install -DskipTests=true

This failure I manually mitigated by removing hortonworks-nexus from
the settings as far as it wasn't absolutely required for finding some
dependency (and I had previously fetched that to the local .m2/):

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.7:site (default) on
project atlas-docs: SiteToolException: The site descriptor cannot be
resolved from the repository: ArtifactResolutionException: Unable to
locate site descriptor: Could not transfer artifact
org.apache:apache:xml:site_en:17 from/to hortonworks-nexus
(http://nexus-private.hortonworks.com/nexus/content/groups/public/):
Connect to nexus-private.hortonworks.com:80
[nexus-private.hortonworks.com/54.173.242.72] failed: Operation timed
out (Connection timed out)

I wonder what would be a proper way to manage that ( maybe this:
https://stackoverflow.com/a/41810983/1068385 – but might be not
enough).

Having hortonworks-nexus is slowing down dependency fetching a lot
whenever the dependency is not found in central. Maybe it could be
avoided by adding all of these explicitly before it:

https://repo.hortonworks.com/content/repositories/releases/
https://repository.apache.org/content/groups/snapshots/
https://repository.apache.org/content/groups/staging/
https://repository.apache.org/content/groups/public/
https://maven.java.net/content/groups/public/
https://repository.jboss.org/nexus/content/groups/public/

..I didn't try that though.

Is there some official way configure the maven repos for an Atlas
build? Could the project pom.xml define the required maven repos? If
there's some automated CI builder for Atlas, how does that work?

Also, README.txt instructs to build with 'mvn install' first, and only
then 'package -Pdist'. Is 'install' (to local .m2) really required for
building the packages?

Thanks!


I used the following settings, saved as ~/.m2/settings-apache-atlas.xml:


http://maven.apache.org/SETTINGS/1.1.0
http://maven.apache.org/xsd/settings-1.1.0.xsd;
xmlns="http://maven.apache.org/SETTINGS/1.1.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
  

  atlas
  

  central
  Maven Central
  http://repo1.maven.org/maven2
  
false
  


  oracleReleases
  Oracle Released Java Packages
  http://download.oracle.com/maven
  
true
  
  


  maven.restlet.org
  maven.restlet.org
  http://maven.restlet.org
  
true
  


  
true
  
  
true
  
  clojars
  https://clojars.org/repo/


  

  
  
atlas

Re: Issues building Atlas

2018-04-09 Thread Ashutosh Mestry

You are right. I will commit the fix soon.

~ ashutosh
Ashutosh Mestry  . Staff Software Engineer . 
Hortonworks, Inc. .  +1-310-988 0670 
...
No hurry, no pause. – Tim Ferriss, Life Hacker, Author
 
On 4/9/18, 3:26 AM, "Nixon Rodrigues"  
wrote:

Justin,

Can you over below suggestion from Madhan on this issue?



*Ashutosh – this might require addition of ‘relativePath’ in
tools/atlas-migration-exporter/pom.xml, as shown below. Can you please
review and update?*



**

*org.apache.atlas*

*apache-atlas*

*1.0.0-SNAPSHOT*

*../../*

**





*Thanks,*

*Madhan*


On Mon, Apr 9, 2018 at 3:47 PM, Justin Shen  wrote:

> I am trying to follow the “Build & Install” guide and encountered the
> following error when building the project:
>
> Non-resolvable parent POM for org.apache.atlas:atlas-
> migration-exporter:[unknown-version]: Could not find artifact
> org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM @ line 24, column 13 ->
> [Help 2]
>
> Modify the POM of atlas_:atlas-migration-exporter to add a relativePath
> seems solve the problem:
>
> 
> org.apache.atlas
> apache-atlas
> 1.0.0-SNAPSHOT
> ../../pom.xml
> 
>
> Is this required? Should the code be changed? Or is there any settings.xml
> that I should use?
>
>
> Thx, -Justin
>
>

答复: Issues building Atlas

2018-04-09 Thread Justin Shen

Some further digging into the issue and found that the current code builds 
successfully with maven 3.5.2 without the need to specify the relativePath and 
it breaks on 3.5.3 and requires the relativePath. Seems maven has some changes 
to how it searches parents.

Nixon pointed out that there is another thread in the user mailing list on the 
same topic, which I missed previously. Sorry for the duplication.

Thx, -Justin

发件人: Nixon Rodrigues <nixon.rodrig...@freestoneinfotech.com>
发送时间: Monday, April 9, 2018 6:26:38 PM
收件人: dev@atlas.apache.org
主题: Re: Issues building Atlas

Justin,

Can you over below suggestion from Madhan on this issue?

*Ashutosh �C this might require addition of ‘relativePath’ in
tools/atlas-migration-exporter/pom.xml, as shown below. Can you please
review and update?*

**

*org.apache.atlas*

*apache-atlas*

*1.0.0-SNAPSHOT*

*../../*

**

*Thanks,*

*Madhan*

On Mon, Apr 9, 2018 at 3:47 PM, Justin Shen <justins...@outlook.com> wrote:

> I am trying to follow the “Build & Install” guide and encountered the
> following error when building the project:
>
> Non-resolvable parent POM for org.apache.atlas:atlas-
> migration-exporter:[unknown-version]: Could not find artifact
> org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM @ line 24, column 13 ->
> [Help 2]
>
> Modify the POM of atlas_:atlas-migration-exporter to add a relativePath
> seems solve the problem:
>
> 
> org.apache.atlas
> apache-atlas
> 1.0.0-SNAPSHOT
> ../../pom.xml
> 
>
> Is this required? Should the code be changed? Or is there any settings.xml
> that I should use?
>
>
> Thx, -Justin
>
>

Re: 答复: Issues building Atlas

2018-04-09 Thread Nixon Rodrigues

Justin,

Please find the thread, it's in user mailing list.

http://mail-archives.apache.org/mod_mbox/atlas-user/201804.mbox/browser

Nixon

On Mon, Apr 9, 2018 at 4:05 PM, Justin Shen <justins...@outlook.com> wrote:

> Hi Nixon,
>
>
>
> Thanks for the reply. Yes, setting the relativePath can solve the problem.
> Either set to ../.. or ../../pom.xml will work.
>
>
>
> Can you share with me where did you get this suggestion from Madhan? Is it
> in JIRA or somewhere? I seems to miss it.
>
>
>
> Thx, -Justin
>
>
> --
> *发件人:* Nixon Rodrigues <nixon.rodrig...@freestoneinfotech.com>
> *发送时间:* Monday, April 9, 2018 6:26:38 PM
> *收件人:* dev@atlas.apache.org
> *主题:* Re: Issues building Atlas
>
> Justin,
>
> Can you over below suggestion from Madhan on this issue?
>
>
>
> *Ashutosh – this might require addition of ‘relativePath’ in
> tools/atlas-migration-exporter/pom.xml, as shown below. Can you please
> review and update?*
>
>
>
> **
>
> *org.apache.atlas*
>
> *apache-atlas*
>
> *1.0.0-SNAPSHOT*
>
> *../../*
>
> **
>
>
>
>
>
> *Thanks,*
>
> *Madhan*
>
>
> On Mon, Apr 9, 2018 at 3:47 PM, Justin Shen <justins...@outlook.com>
> wrote:
>
> > I am trying to follow the “Build & Install” guide and encountered the
> > following error when building the project:
> >
> > Non-resolvable parent POM for org.apache.atlas:atlas-
> > migration-exporter:[unknown-version]: Could not find artifact
> > org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT and
> > 'parent.relativePath' points at wrong local POM @ line 24, column 13 ->
> > [Help 2]
> >
> > Modify the POM of atlas_:atlas-migration-exporter to add a relativePath
> > seems solve the problem:
> >
> > 
> > org.apache.atlas
> > apache-atlas
> > 1.0.0-SNAPSHOT
> > ../../pom.xml
> > 
> >
> > Is this required? Should the code be changed? Or is there any
> settings.xml
> > that I should use?
> >
> >
> > Thx, -Justin
> >
> >
>

Re: Issues building Atlas

2018-04-09 Thread Nixon Rodrigues

Justin,

Can you over below suggestion from Madhan on this issue?



*Ashutosh – this might require addition of ‘relativePath’ in
tools/atlas-migration-exporter/pom.xml, as shown below. Can you please
review and update?*



**

*org.apache.atlas*

*apache-atlas*

*1.0.0-SNAPSHOT*

*../../*

**





*Thanks,*

*Madhan*


On Mon, Apr 9, 2018 at 3:47 PM, Justin Shen  wrote:

> I am trying to follow the “Build & Install” guide and encountered the
> following error when building the project:
>
> Non-resolvable parent POM for org.apache.atlas:atlas-
> migration-exporter:[unknown-version]: Could not find artifact
> org.apache.atlas:apache-atlas:pom:1.0.0-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM @ line 24, column 13 ->
> [Help 2]
>
> Modify the POM of atlas_:atlas-migration-exporter to add a relativePath
> seems solve the problem:
>
> 
> org.apache.atlas
> apache-atlas
> 1.0.0-SNAPSHOT
> ../../pom.xml
> 
>
> Is this required? Should the code be changed? Or is there any settings.xml
> that I should use?
>
>
> Thx, -Justin
>
>

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

2017-11-30 Thread Nigel Jones

On 2017-12-01 00:52, "Nigel Jones" wrote: 

> > atlas.server.ha.zookeeper.connect=localhost:2181

Reading the posts from earlier I then added
00:57 $ export MANAGE_LOCAL_SOLR=true
00:57 $ export MANAGE_LOCAL_HBASE=true
00:58 $ echo 
atlas.graphdb.backend=org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase
 >> conf/atlas-application.properties

With these done, Atlas starts up much more cleanly. I hadn't realised we needed 
elements of the prior script alongside the patch. I would expect the patch/fix 
to have add the necessary config so that the build 'would just work'.

The index creation (as noted) is taking a while, and of course when the atlas 
startup complete returns, the initial type setup is still processing. This 
eventually completes. I'm also able to run quick_start (slowly), with just the 
final DSL query failing

So much better. :-)

At the very least we should update the build docs to clarify these required 
steps, but I do think the less manual steps we have the better?

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

2017-11-30 Thread Nigel Jones

On 2017-12-01 00:31, Madhan Neethiraj  wrote: 

> To get rid of âConnection refusedâ WARN logs, please set the following 
> property in conf/atlas-application.properties and start Atlas

> atlas.server.ha.zookeeper.connect=localhost:2181

This line was commented out. I uncommented, but having then restarted atlas, I 
get the same zookeeper errors

> Not sure what causes HBase error âConnectionLoss for 
> /hbase/meta-region-serverâ in your environment though. By any chance, is 
> there another zookeeper running in your env?

No other zookeeper/hadoop components, just 'desktop' apps intellij, gaiandb, 
postgres/mysql etc.

I see from the review board item that David has similar issues?
Note that I did get your prior script to run clean...

I am building on mac? I know you mentioned previously some of the test attempts 
were on linux

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

2017-11-30 Thread Madhan Neethiraj

Nigel,

 

To get rid of “Connection refused” WARN logs, please set the following property 
in conf/atlas-application.properties and start Atlas

 

:

atlas.server.ha.zookeeper.connect=localhost:2181

 

Not sure what causes HBase error “ConnectionLoss for /hbase/meta-region-server” 
in your environment though. By any chance, is there another zookeeper running 
in your env?

 

Thanks,

Madhan

 

From: Nigel Jones <nore...@reviews.apache.org> on behalf of Nigel Jones 
<jon...@uk.ibm.com>
Reply-To: Nigel Jones <jon...@uk.ibm.com>
Date: Thursday, November 30, 2017 at 4:19 PM
To: Apoorv Naik <naik.apo...@gmail.com>, Madhan Neethiraj <mad...@apache.org>, 
Ashutosh Mestry <ames...@hortonworks.com>
Cc: Nigel Jones <jon...@uk.ibm.com>, atlas <d...@atlas.incubator.apache.org>, 
Sarath Subramanian <sar...@apache.org>
Subject: Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when 
building atlas distribution with Janus profile

 

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




I tried the new patch (2287.2) - mvn command as above (janus).

Build is clean, but I still get errors when starting the server in 
application.log, the UI is now giving me error 503. It still looks like 
zookeeper & hbase issues
 
2017-12-01 00:14:58,069 WARN  - [main-SendThread(localhost:2181):] ~ Session 
0x0 for server null, unexpected error, closing socket connecti

on and attempting reconnect (ClientCnxn$SendThread:1102)

java.net.ConnectException: Connection refused

    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)

    at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)

    at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)

    at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
 
Also

2017-12-01 00:12:41,095 WARN  - [main:] ~ Possibly transient ZooKeeper, 
quorum=localhost:2181, 
exception=org.apache.zookeeper.KeeperException$ConnectionLossException: 
KeeperErrorCode = ConnectionLoss for /hbase/meta-region-server 
(RecoverableZooKeeper:275)

2017-12-01 00:12:41,095 ERROR - [main:] ~ ZooKeeper getData failed after 4 
attempts (RecoverableZooKeeper:277)

2017-12-01 00:12:41,096 WARN  - [main:] ~ hconnection-0x23b8d9f30x0, 
quorum=localhost:2181, baseZNode=/hbase Unable to get data of znode 
/hbase/meta-region-server (ZKUtil:753)

org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = 
ConnectionLoss for /hbase/meta-region-server

    at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)

    at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)

    at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1155)

    at 
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.getData(RecoverableZooKeeper.java:359)

    at org.apache.hadoop.hbase.zookeeper.ZKUtil.getData(ZKUtil.java:745)

    at 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionState(MetaTableLocator.java:482)

    at 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionLocation(MetaTableLocator.java:168)

    at 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(MetaTableLocator.java:600)

    at 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(MetaTableLocator.java:580)

    at 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(MetaTableLocator.java:559)

    at 
org.apache.hadoop.hbase.client.ZooKeeperRegistry.getMetaRegionLocation(ZooKeeperRegistry.java:61)

    at 
 
    
    And some of these:
 
    2017-12-01 00:12:41,096 ERROR - [main:] ~ hconnection-0x23b8d9f30x0, 
quorum=localhost:2181, baseZNode=/hbase Received unexpected KeeperExce
 
 
ption, re-throwing exception (ZooKeeperWatcher:648)

org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = 
ConnectionLoss for /hbase/meta-region-server

    at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)

    at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)

    at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1155)

    at 
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.getData(RecoverableZooKeeper.java:359)

    at org.apache.hadoop.hbase.zookeeper.ZKUtil.getData(ZKUtil.java:745)

    at 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionState(MetaTableLocator.java:482)

    at 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionLocation(MetaTableLocator.java:168)

    at 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(MetaTableLocator.java:600)

    at 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(MetaTableLocator.java:580)

    at 
org.apache.hadoop.hbase.zookeeper.Meta

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

2017-11-30 Thread Nigel Jones

:200)

- Nigel Jones


On Nov. 30, 2017, 8:59 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/64141/
> ---
> 
> (Updated Nov. 30, 2017, 8:59 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2287
> https://issues.apache.org/jira/browse/ATLAS-2287
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> When Atlas is build using -Pdist profile, lucene jars are excluded during 
> packaging of the war file. Since we are not shading graphdb module for janus 
> profile, these jars are needed as run time dependency.
> Titan's shaded jar includes the lucene libraries and hence were excluded 
> during packaging of war to avoid duplicate dependencies.
> 
> 
> Diffs
> -
> 
>   distro/pom.xml eea256d8 
>   graphdb/janus/src/test/resources/atlas-application.properties ebc74ff3 
>   intg/src/test/resources/atlas-application.properties ce9351a6 
>   pom.xml 3720c1f5 
>   repository/pom.xml e24122e5 
>   webapp/pom.xml b4a96d36 
> 
> 
> Diff: https://reviews.apache.org/r/64141/diff/2/
> 
> 
> Testing
> ---
> 
> validated building atlas distribution using both janus and titan0 profile. 
> Atlas starts fine and basic functionalities working.
> 
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr 
> -DGRAPH-PROVIDER=titan0
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

2017-11-30 Thread Madhan Neethiraj


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


Ship it!




Ship It!

- Madhan Neethiraj


On Nov. 30, 2017, 8:59 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/64141/
> ---
> 
> (Updated Nov. 30, 2017, 8:59 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2287
> https://issues.apache.org/jira/browse/ATLAS-2287
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> When Atlas is build using -Pdist profile, lucene jars are excluded during 
> packaging of the war file. Since we are not shading graphdb module for janus 
> profile, these jars are needed as run time dependency.
> Titan's shaded jar includes the lucene libraries and hence were excluded 
> during packaging of war to avoid duplicate dependencies.
> 
> 
> Diffs
> -
> 
>   distro/pom.xml eea256d8 
>   graphdb/janus/src/test/resources/atlas-application.properties ebc74ff3 
>   intg/src/test/resources/atlas-application.properties ce9351a6 
>   pom.xml 3720c1f5 
>   repository/pom.xml e24122e5 
>   webapp/pom.xml b4a96d36 
> 
> 
> Diff: https://reviews.apache.org/r/64141/diff/2/
> 
> 
> Testing
> ---
> 
> validated building atlas distribution using both janus and titan0 profile. 
> Atlas starts fine and basic functionalities working.
> 
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr 
> -DGRAPH-PROVIDER=titan0
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

2017-11-30 Thread Sarath Subramanian


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

(Updated Nov. 30, 2017, 12:59 p.m.)


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


Changes
---

addressed review comments


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


Repository: atlas


Description
---

When Atlas is build using -Pdist profile, lucene jars are excluded during 
packaging of the war file. Since we are not shading graphdb module for janus 
profile, these jars are needed as run time dependency.
Titan's shaded jar includes the lucene libraries and hence were excluded during 
packaging of war to avoid duplicate dependencies.


Diffs (updated)
-

  distro/pom.xml eea256d8 
  graphdb/janus/src/test/resources/atlas-application.properties ebc74ff3 
  intg/src/test/resources/atlas-application.properties ce9351a6 
  pom.xml 3720c1f5 
  repository/pom.xml e24122e5 
  webapp/pom.xml b4a96d36 


Diff: https://reviews.apache.org/r/64141/diff/2/

Changes: https://reviews.apache.org/r/64141/diff/1-2/


Testing
---

validated building atlas distribution using both janus and titan0 profile. 
Atlas starts fine and basic functionalities working.

mvn clean install -DskipTests -Pdist,embedded-hbase-solr
mvn clean install -DskipTests -Pdist,embedded-hbase-solr -DGRAPH-PROVIDER=titan0


Thanks,

Sarath Subramanian

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

2017-11-30 Thread Sarath Subramanian



> On Nov. 30, 2017, 6:47 a.m., David Radley wrote:
> > pom.xml
> > Line 673 (original), 674 (patched)
> > <https://reviews.apache.org/r/64141/diff/1/?file=1903423#file1903423line674>
> >
> > The titan0 build failed for me because it was looking for JanusGraph. I 
> > think that this was because the configuration file was not generated for 
> > Titan 0.

the default backend is to use JanusGraph, if titan is needed, add 
atlas.graphdb.backend=org.apache.atlas.repository.graphdb.titan0.Titan0GraphDatabase
 in atlas-application.preoperties


> On Nov. 30, 2017, 6:47 a.m., David Radley wrote:
> > pom.xml
> > Line 676 (original), 677 (patched)
> > <https://reviews.apache.org/r/64141/diff/1/?file=1903423#file1903423line677>
> >
> > It seems odd to have a profile that specifies elastic search and 
> > excludes the elastic search.

we are excluding elastic search jars since we build shaded jar 
atlas-graphdb-titan0.jar which includes dependent ES libraries


> On Nov. 30, 2017, 6:47 a.m., David Radley wrote:
> > pom.xml
> > Lines 679 (patched)
> > <https://reviews.apache.org/r/64141/diff/1/?file=1903423#file1903423line679>
> >
> > why are we excluding titan jar file for a titan profile ?

same as above the shaded jar atlas-graphdb-titan0.jar contains titan libraries 
excluding it to avoid duplicate


> On Nov. 30, 2017, 6:47 a.m., David Radley wrote:
> > pom.xml
> > Lines 700 (patched)
> > <https://reviews.apache.org/r/64141/diff/1/?file=1903423#file1903423line700>
> >
> > I suggest we remove this profile

agreed. will remove it


> On Nov. 30, 2017, 6:47 a.m., David Radley wrote:
> > pom.xml
> > Line 717 (original), 720 (patched)
> > <https://reviews.apache.org/r/64141/diff/1/?file=1903423#file1903423line720>
> >
> > So the default Janus profile have solr.embedded. Does this mean that it 
> > will not work with external solr now?

This is a test only property that tells maven to start/stop solr instances 
during unit tests. There is no hard dependency on Solr during runtime. Will 
rename the property to a more intuitive name.


> On Nov. 30, 2017, 6:47 a.m., David Radley wrote:
> > pom.xml
> > Lines 721 (patched)
> > <https://reviews.apache.org/r/64141/diff/1/?file=1903423#file1903423line721>
> >
> > I wonder why you are excluding je -* files here . Do they cause a 
> > problem?

Due to licensing requirements, Atlas does not bundle the BerkeleyDB Java 
Edition in the tarball.


- Sarath


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


On Nov. 28, 2017, 6:32 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/64141/
> ---
> 
> (Updated Nov. 28, 2017, 6:32 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2287
> https://issues.apache.org/jira/browse/ATLAS-2287
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> When Atlas is build using -Pdist profile, lucene jars are excluded during 
> packaging of the war file. Since we are not shading graphdb module for janus 
> profile, these jars are needed as run time dependency.
> Titan's shaded jar includes the lucene libraries and hence were excluded 
> during packaging of war to avoid duplicate dependencies.
> 
> 
> Diffs
> -
> 
>   distro/pom.xml eea256d8 
>   pom.xml 3720c1f5 
>   webapp/pom.xml b4a96d36 
> 
> 
> Diff: https://reviews.apache.org/r/64141/diff/1/
> 
> 
> Testing
> ---
> 
> validated building atlas distribution using both janus and titan0 profile. 
> Atlas starts fine and basic functionalities working.
> 
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr 
> -DGRAPH-PROVIDER=titan0
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

2017-11-30 Thread Madhan Neethiraj

(Review board wouldn’t post my comments to this review – probably because of 
other updates to the review while I was reviewing. Hence sending my comments by 
email)

>> David: The titan0 build failed for me because it was looking for JanusGraph. 
>> I think that this was because the configuration file was not generated for 
>> Titan 0.
Default configuration is set for Janus graph. If build command specifies a 
graph-provider, make sure to review and update the configurations to match the 
specified flavor. If further auto-magic configuration setup is necessary for 
dev-deployments, I would suggest to take this up in a separate JIRA.
>> David: why are we excluding titan jar file for a titan profile ?
Because titan classes are included in atlas-graphdb-titan0 jar file.

>> David: I suggest we remove this profile
I agree on removing 'atlas-graphdb-titan1'. Sarath - can you please?

I was able to bring up Atlas in a stand-alone dev-deploy, with default 
GRAPH_PROVIDER (janus).

+1 from me for this patch.

Thanks,
Madhan

From: Sarath Subramanian <nore...@reviews.apache.org> on behalf of Sarath 
Subramanian <sar...@apache.org>
Reply-To: Sarath Subramanian <sar...@apache.org>
Date: Thursday, November 30, 2017 at 11:25 AM
To: Apoorv Naik <naik.apo...@gmail.com>, Madhan Neethiraj <mad...@apache.org>, 
Ashutosh Mestry <ames...@hortonworks.com>
Cc: Nigel Jones <jon...@uk.ibm.com>, atlas <d...@atlas.incubator.apache.org>, 
David Radley <david...@apache.org>, Sarath Subramanian <sar...@apache.org>
Subject: Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when 
building atlas distribution with Janus profile

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



On November 30th, 2017, 6:47 a.m. PST, David Radley wrote:
pom.xml<https://reviews.apache.org/r/64141/diff/1/?file=1903423#file1903423line716>
 (Diff revision 1)

713


atlas-graphdb-janus

716


atlas-graphdb-janus


I could start the UI but had lots of Zookeeper exceptions and posts to create 
entities did not work.



I got errors like this :

2017-11-30 12:16:28,975 INFO  - [main:] ~ GraphTransaction intercept for 
org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1.addClassifications
 (GraphTransactionAdvisor$1:41)

2017-11-30 12:16:28,975 INFO  - [main:] ~ GraphTransaction intercept for 
org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1.updateClassifications
 (GraphTransactionAdvisor$1:41)

2017-11-30 12:16:28,976 INFO  - [main:] ~ GraphTransaction intercept for 
org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1.addClassification 
(GraphTransactionAdvisor$1:41)

2017-11-30 12:16:28,976 INFO  - [main:] ~ GraphTransaction intercept for 
org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1.deleteClassifications
 (GraphTransactionAdvisor$1:41)

2017-11-30 12:16:28,976 INFO  - [main:] ~ GraphTransaction intercept for 
org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1.getClassification 
(GraphTransactionAdvisor$1:41)

2017-11-30 12:16:29,021 WARN  - [main-SendThread(localhost:9026):] ~ Session 
0x0 for server null, unexpected error, closing socket connection and attempting 
reconnect (ClientCnxn$SendThread:1102)

java.net.ConnectException: Connection refused

at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)

at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)

at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)

at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)

2017-11-30 12:16:29,029 INFO  - [main:] ~ Starting service 
org.apache.atlas.web.service.ActiveInstanceElectorService (Services:53)

2017-11-30 12:16:29,030 INFO  - [main:] ~ HA is not enabled, no need to start 
leader election service (ActiveInstanceElectorService:96)

2017-11-30 12:16:29,030 INFO  - [main:] ~ Starting service 
org.apache.atlas.kafka.KafkaNotification (Services:53)

2017-11



and

017-11-30 12:16:31,194 INFO  - [main:] ~ Adding cross-site request forgery 
(CSRF) protection (AtlasCSRFPreventionFilter:98)

2017-11-30 12:16:31,646 INFO  - [main:] ~ AuditFilter initialization started 
(AuditFilter:57)

2017-11-30 12:30:47,004 WARN  - 
[NIOServerCxn.Factory:localhost/127.0.0.1:9026:] ~ caught end of stream 
exception (NIOServerCnxn:357)

EndOfStreamException: Unable to read additional data from client sessionid 
0x1600cdb5584, likely client has closed socket

at 
org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)

at 
org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)

at java.lang.Thread.run(Thread.java:748)

2017-11-30 12:30:47,109 WARN  - [zkCallback-3-thread-2:] ~ Watcher 
org.apache.solr.common.cloud.ConnectionManager@5232c71 name: 
ZooKeeper

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

2017-11-30 Thread Sarath Subramanian

at 
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
> at java.lang.Thread.run(Thread.java:748)
> 
> This error was caused by incorrect port number configuration in 
> conf/atlas-application.properties:
>   atlas.kafka.zookeeper.connect=localhost:9026
> 
> The fix is to replace 9026 with 2181 (i.e. use the zookeeper in 
> embedded-hbase).
> 
> However, after this change startup of 
> org.apache.atlas.kafka.KafkaNotification service seems to hang. I will look 
> into this further.
> 
> Madhan Neethiraj wrote:
> Use of port 9026 is indeed correct. No need to update the configuration.
> 
> WARN messagess about "connection refused" are specific to stand-alone 
> dev-env deployment where Atlas uses an embedded Kafka & Zookeeper. Kafka & 
> Zookeeper are started towards the end of initilization but before this is 
> done, an attempt is made to connect to the Zookeeper - resulting in this 
> WARN. This WARNing will be gone later after embedded Kafka and Zookeeper are 
> started. Need to investigate from where the connection attempt is being made. 
> But this issue shouldn't block Atlas being functional.
> 
> Another error, "Unable to read additional data from client sessionid 
> 0x1600cdb55840001, likely client has closed socket" - I think this might be 
> due to low connect/session timeout values in 
> conf/atlas-application.properties:
>   atlas.kafka.zookeeper.session.timeout.ms=400
>   atlas.kafka.zookeeper.connection.timeout.ms=200
> 
> Can you increase both to 6 and try again?

I validated my patch again on a bare CentOS machine and it works, the steps I 
followed:

# Environment
CentOS 6.8
Apache Maven 3.5.2
Java version: 1.8.0_151

1. Clear your m2 cache:  rm -rf ~/.m2/repository
2. Make sure JAVA_HOME is set in your environment, echo $JAVA_HOME to confirm
3. Export the following (or add it to your bashrc and source it)
   export MANAGE_LOCAL_SOLR=true
   export MANAGE_LOCAL_HBASE=true

# Clone and Build Atlas (for Janus profile)

git clone https://github.com/apache/atlas.git -b master

mvn clean install -DskipTests -Pdist,embedded-hbase-solr

# Copy the distribution to atlas binary directory and extract

mkdir /tmp/atlas_binary
cp -r distro/target/apache-atlas-1.0.0-SNAPSHOT-bin.tar.gz /tmp/atlas_binary/

cd /tmp/atlas_binary/
tar -zxvf apache-atlas-1.0.0-SNAPSHOT-bin.tar.gz

cd /tmp/atlas_binary/apache-atlas-1.0.0-SNAPSHOT
echo 
atlas.graphdb.backend=org.apache.atlas.repository.graphdb.janus.AtlasJanusGraphDatabase
 >> conf/atlas-application.properties

# Start Atlas

./bin/atlas_start.py

It's going to take a while for Atlas to startup but it eventually gets there. 
The reason for the slowness is in the indexing stage (which is a different 
issue altogether).
But the basic functionalities work

# Atlas UI
http://localhost:21000/


- Sarath


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


On Nov. 28, 2017, 6:32 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/64141/
> ---
> 
> (Updated Nov. 28, 2017, 6:32 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2287
> https://issues.apache.org/jira/browse/ATLAS-2287
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> When Atlas is build using -Pdist profile, lucene jars are excluded during 
> packaging of the war file. Since we are not shading graphdb module for janus 
> profile, these jars are needed as run time dependency.
> Titan's shaded jar includes the lucene libraries and hence were excluded 
> during packaging of war to avoid duplicate dependencies.
> 
> 
> Diffs
> -
> 
>   distro/pom.xml eea256d8 
>   pom.xml 3720c1f5 
>   webapp/pom.xml b4a96d36 
> 
> 
> Diff: https://reviews.apache.org/r/64141/diff/1/
> 
> 
> Testing
> ---
> 
> validated building atlas distribution using both janus and titan0 profile. 
> Atlas starts fine and basic functionalities working.
> 
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr 
> -DGRAPH-PROVIDER=titan0
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

2017-11-30 Thread Madhan Neethiraj

at 
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
> at java.lang.Thread.run(Thread.java:748)
> 
> This error was caused by incorrect port number configuration in 
> conf/atlas-application.properties:
>   atlas.kafka.zookeeper.connect=localhost:9026
> 
> The fix is to replace 9026 with 2181 (i.e. use the zookeeper in 
> embedded-hbase).
> 
> However, after this change startup of 
> org.apache.atlas.kafka.KafkaNotification service seems to hang. I will look 
> into this further.

Use of port 9026 is indeed correct. No need to update the configuration.

WARN messagess about "connection refused" are specific to stand-alone dev-env 
deployment where Atlas uses an embedded Kafka & Zookeeper. Kafka & Zookeeper 
are started towards the end of initilization but before this is done, an 
attempt is made to connect to the Zookeeper - resulting in this WARN. This 
WARNing will be gone later after embedded Kafka and Zookeeper are started. Need 
to investigate from where the connection attempt is being made. But this issue 
shouldn't block Atlas being functional.

Another error, "Unable to read additional data from client sessionid 
0x1600cdb55840001, likely client has closed socket" - I think this might be due 
to low connect/session timeout values in conf/atlas-application.properties:
  atlas.kafka.zookeeper.session.timeout.ms=400
  atlas.kafka.zookeeper.connection.timeout.ms=200

Can you increase both to 6 and try again?


- Madhan


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


On Nov. 29, 2017, 2:32 a.m., Sarath Subramanian wrote:
> 
> -------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/64141/
> ---
> 
> (Updated Nov. 29, 2017, 2:32 a.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2287
> https://issues.apache.org/jira/browse/ATLAS-2287
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> When Atlas is build using -Pdist profile, lucene jars are excluded during 
> packaging of the war file. Since we are not shading graphdb module for janus 
> profile, these jars are needed as run time dependency.
> Titan's shaded jar includes the lucene libraries and hence were excluded 
> during packaging of war to avoid duplicate dependencies.
> 
> 
> Diffs
> -
> 
>   distro/pom.xml eea256d8 
>   pom.xml 3720c1f5 
>   webapp/pom.xml b4a96d36 
> 
> 
> Diff: https://reviews.apache.org/r/64141/diff/1/
> 
> 
> Testing
> ---
> 
> validated building atlas distribution using both janus and titan0 profile. 
> Atlas starts fine and basic functionalities working.
> 
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr 
> -DGRAPH-PROVIDER=titan0
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

2017-11-30 Thread Madhan Neethiraj

verCnxnFactory.java:208)
at java.lang.Thread.run(Thread.java:748)

This error was caused by incorrect port number configuration in 
conf/atlas-application.properties:
  atlas.kafka.zookeeper.connect=localhost:9026

The fix is to replace 9026 with 2181 (i.e. use the zookeeper in embedded-hbase).

However, after this change startup of org.apache.atlas.kafka.KafkaNotification 
service seems to hang. I will look into this further.


- Madhan


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


On Nov. 29, 2017, 2:32 a.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/64141/
> ---
> 
> (Updated Nov. 29, 2017, 2:32 a.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2287
> https://issues.apache.org/jira/browse/ATLAS-2287
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> When Atlas is build using -Pdist profile, lucene jars are excluded during 
> packaging of the war file. Since we are not shading graphdb module for janus 
> profile, these jars are needed as run time dependency.
> Titan's shaded jar includes the lucene libraries and hence were excluded 
> during packaging of war to avoid duplicate dependencies.
> 
> 
> Diffs
> -
> 
>   distro/pom.xml eea256d8 
>   pom.xml 3720c1f5 
>   webapp/pom.xml b4a96d36 
> 
> 
> Diff: https://reviews.apache.org/r/64141/diff/1/
> 
> 
> Testing
> ---
> 
> validated building atlas distribution using both janus and titan0 profile. 
> Atlas starts fine and basic functionalities working.
> 
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr 
> -DGRAPH-PROVIDER=titan0
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

2017-11-30 Thread Nigel Jones


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



I tried this patch on atlas-master (0900 UTC 20171130), maven 3.5.0, java 8 
(b152), macOS. 
Only built for janus
Built clean.  
Server started, but seemed very slow to do so 
application.log showing many errors - including zookeeper every 1s 
quick_start failed (503/service unavailable) 
UI fails (503/service unavailable) 
script for titan054 etc on mail list did pass the above (some errors, but many 
less) 
Conclusion: patch doesn't work for me  - Nigel Jones

- Nigel Jones


On Nov. 29, 2017, 2:32 a.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/64141/
> ---
> 
> (Updated Nov. 29, 2017, 2:32 a.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2287
> https://issues.apache.org/jira/browse/ATLAS-2287
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> When Atlas is build using -Pdist profile, lucene jars are excluded during 
> packaging of the war file. Since we are not shading graphdb module for janus 
> profile, these jars are needed as run time dependency.
> Titan's shaded jar includes the lucene libraries and hence were excluded 
> during packaging of war to avoid duplicate dependencies.
> 
> 
> Diffs
> -
> 
>   distro/pom.xml eea256d8 
>   pom.xml 3720c1f5 
>   webapp/pom.xml b4a96d36 
> 
> 
> Diff: https://reviews.apache.org/r/64141/diff/1/
> 
> 
> Testing
> ---
> 
> validated building atlas distribution using both janus and titan0 profile. 
> Atlas starts fine and basic functionalities working.
> 
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr 
> -DGRAPH-PROVIDER=titan0
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

2017-11-30 Thread David Radley

S-2287
> https://issues.apache.org/jira/browse/ATLAS-2287
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> When Atlas is build using -Pdist profile, lucene jars are excluded during 
> packaging of the war file. Since we are not shading graphdb module for janus 
> profile, these jars are needed as run time dependency.
> Titan's shaded jar includes the lucene libraries and hence were excluded 
> during packaging of war to avoid duplicate dependencies.
> 
> 
> Diffs
> -
> 
>   distro/pom.xml eea256d8 
>   pom.xml 3720c1f5 
>   webapp/pom.xml b4a96d36 
> 
> 
> Diff: https://reviews.apache.org/r/64141/diff/1/
> 
> 
> Testing
> ---
> 
> validated building atlas distribution using both janus and titan0 profile. 
> Atlas starts fine and basic functionalities working.
> 
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr
> mvn clean install -DskipTests -Pdist,embedded-hbase-solr 
> -DGRAPH-PROVIDER=titan0
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>

[jira] [Updated] (ATLAS-2287) Include lucene libraries when building atlas distribution with Janus profile

2017-11-28 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian updated ATLAS-2287:
--
Description: 
When Atlas is build using -Pdist profile, lucene jars are excluded during 
packaging of the war file. Since we are not shading graphdb module for janus 
profile, these jars are needed as run time dependency.

Titan's shaded jar includes the lucene libraries and hence were excluded during 
packaging of war to avoid duplicate dependencies.

  was:
When Atlas is build using -Pdist profile, lucene jars are excluded during 
packaging of the war file. Since we are not shading graphdb module for janus 
profile, these jars need to be included as run time dependency.

Titan's shaded jar already included the lucene libraries and hence were 
excluded during packaging of war to avoid duplicate dependencies.


> Include lucene libraries when building atlas distribution with Janus profile
> 
>
> Key: ATLAS-2287
> URL: https://issues.apache.org/jira/browse/ATLAS-2287
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 1.0.0
>
> Attachments: ATLAS-2287.1.patch
>
>
> When Atlas is build using -Pdist profile, lucene jars are excluded during 
> packaging of the war file. Since we are not shading graphdb module for janus 
> profile, these jars are needed as run time dependency.
> Titan's shaded jar includes the lucene libraries and hence were excluded 
> during packaging of war to avoid duplicate dependencies.



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

[jira] [Commented] (ATLAS-2287) Include lucene libraries when building atlas distribution with Janus profile

2017-11-28 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian commented on ATLAS-2287:
---

Code Review: https://reviews.apache.org/r/64141/

> Include lucene libraries when building atlas distribution with Janus profile
> 
>
> Key: ATLAS-2287
> URL: https://issues.apache.org/jira/browse/ATLAS-2287
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 1.0.0
>
> Attachments: ATLAS-2287.1.patch
>
>
> When Atlas is build using -Pdist profile, lucene jars are excluded during 
> packaging of the war file. Since we are not shading graphdb module for janus 
> profile, these jars are needed as run time dependency.
> Titan's shaded jar includes the lucene libraries and hence were excluded 
> during packaging of war to avoid duplicate dependencies.



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

Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

2017-11-28 Thread Sarath Subramanian


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

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


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


Repository: atlas


Description
---

When Atlas is build using -Pdist profile, lucene jars are excluded during 
packaging of the war file. Since we are not shading graphdb module for janus 
profile, these jars are needed as run time dependency.
Titan's shaded jar includes the lucene libraries and hence were excluded during 
packaging of war to avoid duplicate dependencies.


Diffs
-

  distro/pom.xml eea256d8 
  pom.xml 3720c1f5 
  webapp/pom.xml b4a96d36 


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


Testing
---

validated building atlas distribution using both janus and titan0 profile. 
Atlas starts fine and basic functionalities working.

mvn clean install -DskipTests -Pdist,embedded-hbase-solr
mvn clean install -DskipTests -Pdist,embedded-hbase-solr -DGRAPH-PROVIDER=titan0


Thanks,

Sarath Subramanian

[jira] [Created] (ATLAS-2287) Include lucene libraries when building atlas distribution with Janus profile

2017-11-28 Thread Sarath Subramanian (JIRA)

Sarath Subramanian created ATLAS-2287:
-

 Summary: Include lucene libraries when building atlas distribution 
with Janus profile
 Key: ATLAS-2287
 URL: https://issues.apache.org/jira/browse/ATLAS-2287
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.0.0
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
 Fix For: 1.0.0


When Atlas is build using -Pdist profile, lucene jars are excluded during 
packaging of the war file. Since we are not shading graphdb module for janus 
profile, these jars need to be included as run time dependency.

Titan's shaded jar already included the lucene libraries and hence were 
excluded during packaging of war to avoid duplicate dependencies.



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

[jira] [Updated] (ATLAS-2287) Include lucene libraries when building atlas distribution with Janus profile

2017-11-28 Thread Sarath Subramanian (JIRA)


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

Sarath Subramanian updated ATLAS-2287:
--
Attachment: ATLAS-2287.1.patch

> Include lucene libraries when building atlas distribution with Janus profile
> 
>
> Key: ATLAS-2287
> URL: https://issues.apache.org/jira/browse/ATLAS-2287
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 1.0.0
>
> Attachments: ATLAS-2287.1.patch
>
>
> When Atlas is build using -Pdist profile, lucene jars are excluded during 
> packaging of the war file. Since we are not shading graphdb module for janus 
> profile, these jars need to be included as run time dependency.
> Titan's shaded jar already included the lucene libraries and hence were 
> excluded during packaging of war to avoid duplicate dependencies.



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

Re: building Atlas

Re: building Atlas

building Atlas

Re: Review Request 74375: ATLAS-4740: enable building Atlas using JDK versions higher than 8

Review Request 74375: ATLAS-4740: enable building Atlas using JDK versions higher than 8

Building Atlas from source

Re: Issues building Atlas

答复: Issues building Atlas

Re: 答复: Issues building Atlas

Re: Issues building Atlas

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

Re: Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

[jira] [Updated] (ATLAS-2287) Include lucene libraries when building atlas distribution with Janus profile

[jira] [Commented] (ATLAS-2287) Include lucene libraries when building atlas distribution with Janus profile

Review Request 64141: [ATLAS-2287]: Include lucene libraries when building atlas distribution with Janus profile

[jira] [Created] (ATLAS-2287) Include lucene libraries when building atlas distribution with Janus profile

[jira] [Updated] (ATLAS-2287) Include lucene libraries when building atlas distribution with Janus profile

28 matches

Site Navigation

Mail list logo

Footer information