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

2018-10-19 Thread Ramesh Mani 
+1 Release Apache Atlas v 0.8.3 - rc0 release

- Built successfully from the source tar file
- Verified PGP signature

Thanks
Ramesh

On 10/17/18, 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 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
>
>

[jira] [Commented] (ATLAS-2926) ZipSink: Very Large Entities Cause Out Of Memory Exception

2018-10-19 Thread ASF subversion and git services (JIRA) 


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

ASF subversion and git services commented on ATLAS-2926:


Commit f72183da5970c95245062a03681eba3c71ffe2df in atlas's branch 
refs/heads/branch-1.0 from [~ashutoshm]
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=f72183d ]

ATLAS-2926: ZipSink OOM


> ZipSink: Very Large Entities Cause Out Of Memory Exception
> --
>
> Key: ATLAS-2926
> URL: https://issues.apache.org/jira/browse/ATLAS-2926
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.2, trunk, 0.8.3
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk, 0.8.3
>
> Attachments: ATLAS-2926-ZipSink-OOM.patch
>
>
> *Steps to Duplicate*
>  # Setup Atlas with very large data. Atlas one entity should be about 300 MB 
> in size.
>  # Perform export with parameters that will include the large entity.
> Following error will be encountered:
> {code:java}
> java.lang.OutOfMemoryError: Requested array size exceeds VM limit     at 
> java.lang.StringCoding$StringEncoder.encode(StringCoding.java:300)     at 
> java.lang.StringCoding.encode(StringCoding.java:344)     at 
> java.lang.StringCoding.encode(StringCoding.java:387)     at 
> java.lang.String.getBytes(String.java:958)     at 
> org.apache.atlas.repository.impexp.ZipSink.addToZipStream(ZipSink.java:106)   
>   at org.apache.atlas.repository.impexp.ZipSink.saveToZip(ZipSink.java:95)    
>  at org.apache.atlas.repository.impexp.ZipSink.add(ZipSink.java:55)     at 
> org.apache.atlas.repository.impexp.ExportService.addEntity(ExportService.java:467)
> {code}
> *Additional Information*
> During conversion of entity string to bytes, a known JDK error is encountered.
>  



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

Re: [ANNOUNCE] New Committer: Ramesh Mani

2018-10-19 Thread Ramesh Mani 
Thank you all. Very pleased to be a part of Apache Atlas project and shall
continuity my contributions and support.

Ramesh

On 10/15/18, 7:29 PM, "Sarath Subramanian"  wrote:

>Atlas community,
>
>Apache Atlas PMC has asked Ramesh Mani to become a committer and we are
>pleased to announce that he has accepted.
>
>Welcome Ramesh, great to have you on board.
>
>On behalf of Apache Atlas PMC,
>
>Sarath

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


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,

[jira] [Commented] (ATLAS-2926) ZipSink: Very Large Entities Cause Out Of Memory Exception

2018-10-19 Thread ASF subversion and git services (JIRA) 


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

ASF subversion and git services commented on ATLAS-2926:


Commit 4a3422934a2c44eb0db918304113fdc28aa792d0 in atlas's branch 
refs/heads/branch-0.8 from [~ashutoshm]
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=4a34229 ]

ATLAS-2926: ZipSink OOM


> ZipSink: Very Large Entities Cause Out Of Memory Exception
> --
>
> Key: ATLAS-2926
> URL: https://issues.apache.org/jira/browse/ATLAS-2926
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.2, trunk, 0.8.3
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk, 0.8.3
>
> Attachments: ATLAS-2926-ZipSink-OOM.patch
>
>
> *Steps to Duplicate*
>  # Setup Atlas with very large data. Atlas one entity should be about 300 MB 
> in size.
>  # Perform export with parameters that will include the large entity.
> Following error will be encountered:
> {code:java}
> java.lang.OutOfMemoryError: Requested array size exceeds VM limit     at 
> java.lang.StringCoding$StringEncoder.encode(StringCoding.java:300)     at 
> java.lang.StringCoding.encode(StringCoding.java:344)     at 
> java.lang.StringCoding.encode(StringCoding.java:387)     at 
> java.lang.String.getBytes(String.java:958)     at 
> org.apache.atlas.repository.impexp.ZipSink.addToZipStream(ZipSink.java:106)   
>   at org.apache.atlas.repository.impexp.ZipSink.saveToZip(ZipSink.java:95)    
>  at org.apache.atlas.repository.impexp.ZipSink.add(ZipSink.java:55)     at 
> org.apache.atlas.repository.impexp.ExportService.addEntity(ExportService.java:467)
> {code}
> *Additional Information*
> During conversion of entity string to bytes, a known JDK error is encountered.
>  



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

[jira] [Commented] (ATLAS-2926) ZipSink: Very Large Entities Cause Out Of Memory Exception

2018-10-19 Thread ASF subversion and git services (JIRA) 


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

ASF subversion and git services commented on ATLAS-2926:


Commit 78e41ac25d6dba65a52d61c43f4f98c5956d1e7d in atlas's branch 
refs/heads/master from [~ashutoshm]
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=78e41ac ]

ATLAS-2926: ZipSink OOM


> ZipSink: Very Large Entities Cause Out Of Memory Exception
> --
>
> Key: ATLAS-2926
> URL: https://issues.apache.org/jira/browse/ATLAS-2926
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.2, trunk, 0.8.3
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk, 0.8.3
>
> Attachments: ATLAS-2926-ZipSink-OOM.patch
>
>
> *Steps to Duplicate*
>  # Setup Atlas with very large data. Atlas one entity should be about 300 MB 
> in size.
>  # Perform export with parameters that will include the large entity.
> Following error will be encountered:
> {code:java}
> java.lang.OutOfMemoryError: Requested array size exceeds VM limit     at 
> java.lang.StringCoding$StringEncoder.encode(StringCoding.java:300)     at 
> java.lang.StringCoding.encode(StringCoding.java:344)     at 
> java.lang.StringCoding.encode(StringCoding.java:387)     at 
> java.lang.String.getBytes(String.java:958)     at 
> org.apache.atlas.repository.impexp.ZipSink.addToZipStream(ZipSink.java:106)   
>   at org.apache.atlas.repository.impexp.ZipSink.saveToZip(ZipSink.java:95)    
>  at org.apache.atlas.repository.impexp.ZipSink.add(ZipSink.java:55)     at 
> org.apache.atlas.repository.impexp.ExportService.addEntity(ExportService.java:467)
> {code}
> *Additional Information*
> During conversion of entity string to bytes, a known JDK error is encountered.
>  



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

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
> 
>
> 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

[jira] [Commented] (ATLAS-2926) ZipSink: Very Large Entities Cause Out Of Memory Exception

2018-10-19 Thread Ashutosh Mestry (JIRA) 


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

Ashutosh Mestry commented on ATLAS-2926:


[~nikhilbonte] Thanks for verifying!

> ZipSink: Very Large Entities Cause Out Of Memory Exception
> --
>
> Key: ATLAS-2926
> URL: https://issues.apache.org/jira/browse/ATLAS-2926
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.2, trunk, 0.8.3
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk, 0.8.3
>
> Attachments: ATLAS-2926-ZipSink-OOM.patch
>
>
> *Steps to Duplicate*
>  # Setup Atlas with very large data. Atlas one entity should be about 300 MB 
> in size.
>  # Perform export with parameters that will include the large entity.
> Following error will be encountered:
> {code:java}
> java.lang.OutOfMemoryError: Requested array size exceeds VM limit     at 
> java.lang.StringCoding$StringEncoder.encode(StringCoding.java:300)     at 
> java.lang.StringCoding.encode(StringCoding.java:344)     at 
> java.lang.StringCoding.encode(StringCoding.java:387)     at 
> java.lang.String.getBytes(String.java:958)     at 
> org.apache.atlas.repository.impexp.ZipSink.addToZipStream(ZipSink.java:106)   
>   at org.apache.atlas.repository.impexp.ZipSink.saveToZip(ZipSink.java:95)    
>  at org.apache.atlas.repository.impexp.ZipSink.add(ZipSink.java:55)     at 
> org.apache.atlas.repository.impexp.ExportService.addEntity(ExportService.java:467)
> {code}
> *Additional Information*
> During conversion of entity string to bytes, a known JDK error is encountered.
>  



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

Add me as a contributor for Atlas

2018-10-19 Thread Nikhil Bonte 
Hi,

Please add me as a contributor for Atlas.
My jira id is nikhilbonte.
-- 
Regards
Nikhil P. Bonte

[jira] [Commented] (ATLAS-2926) ZipSink: Very Large Entities Cause Out Of Memory Exception

2018-10-19 Thread Nikhil Bonte (JIRA) 


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

Nikhil Bonte commented on ATLAS-2926:
-

[~ashutoshm],
I tried export/import with patch (ATLAS-2926-ZipSink-OOM.patch) with various 
scenarios.
Seems that it is working fine.
 
+1 for the [^ATLAS-2926-ZipSink-OOM.patch]
Thanks!

> ZipSink: Very Large Entities Cause Out Of Memory Exception
> --
>
> Key: ATLAS-2926
> URL: https://issues.apache.org/jira/browse/ATLAS-2926
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.2, trunk, 0.8.3
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk, 0.8.3
>
> Attachments: ATLAS-2926-ZipSink-OOM.patch
>
>
> *Steps to Duplicate*
>  # Setup Atlas with very large data. Atlas one entity should be about 300 MB 
> in size.
>  # Perform export with parameters that will include the large entity.
> Following error will be encountered:
> {code:java}
> java.lang.OutOfMemoryError: Requested array size exceeds VM limit     at 
> java.lang.StringCoding$StringEncoder.encode(StringCoding.java:300)     at 
> java.lang.StringCoding.encode(StringCoding.java:344)     at 
> java.lang.StringCoding.encode(StringCoding.java:387)     at 
> java.lang.String.getBytes(String.java:958)     at 
> org.apache.atlas.repository.impexp.ZipSink.addToZipStream(ZipSink.java:106)   
>   at org.apache.atlas.repository.impexp.ZipSink.saveToZip(ZipSink.java:95)    
>  at org.apache.atlas.repository.impexp.ZipSink.add(ZipSink.java:55)     at 
> org.apache.atlas.repository.impexp.ExportService.addEntity(ExportService.java:467)
> {code}
> *Additional Information*
> During conversion of entity string to bytes, a known JDK error is encountered.
>  



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