Re: [VOTE] Release Apache Atlas v 0.8.3 - RC0
Ashutosh - thanks for putting this release together. This release has 100+ fixes/enhancements - including major updates to import/export, a number of performance improvements. Performed the following: - verified the signature - built & installed embedded-hbase-solr profile - successfully brought up Apache Atlas 0.8.3 - ran quick_start - performed few basic searches and DSL searches - verified saved search functionality +1 for Apache Atlas 0.8.3-rc0 Thanks, Madhan 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-2908) Restrict search based on authorization
[ https://issues.apache.org/jira/browse/ATLAS-2908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16655801#comment-16655801 ] Saravanan Elumalai commented on ATLAS-2908: --- [~nixonrodrigues] Thanks for your response but still it doesn't address the issue. Let me explain the issue better. We are using KnoxSSO for authentication with Google OAuth (restricted to a particular domain) and we have an Active Directory setup for authorization and group mapping. Atlas is configured to allow only users in a particular group. When a user logins through OAuth and if the user is available in Active Directory, access is restricted based on the policy in conf/atlas-simple-authz-policy.json. When a user logins through OAuth and if the user is not available in Active Directory, he is not part of any group so ideally, he should not be able to perform any operation in Atlas. In Atlas 1.0 the user is not able to view classification or glossary but he is able to perform search. When the user clicks the link in search result 'Access Denied' error message is shown. is this expected behavior? > Restrict search based on authorization > -- > > Key: ATLAS-2908 > URL: https://issues.apache.org/jira/browse/ATLAS-2908 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Saravanan Elumalai >Priority: Major > > We are using KnoxSSO for login and *Simple-Authoriser* to restrict access > based on *groupRoles* mapping. When an user is not part of any group he is > not able to view the entities or classifications but he is able to perform > search. > How to restrict search if the user is not part of any group? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2926) ZipSink: Very Large Entities Cause Out Of Memory Exception
Ashutosh Mestry created ATLAS-2926:
--
Summary: 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
Fix For: trunk, 0.8.3
*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] [Updated] (ATLAS-2926) ZipSink: Very Large Entities Cause Out Of Memory Exception
[
https://issues.apache.org/jira/browse/ATLAS-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Mestry updated ATLAS-2926:
---
Attachment: ATLAS-2926-ZipSink-OOM.patch
> 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-2925) Better logging for graph database initialization error
[ https://issues.apache.org/jira/browse/ATLAS-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16655024#comment-16655024 ] Fabiano V. Santos commented on ATLAS-2925: -- Linked as external issue URL the pull request that solves this issue: https://github.com/apache/atlas/pull/12 > Better logging for graph database initialization error > -- > > Key: ATLAS-2925 > URL: https://issues.apache.org/jira/browse/ATLAS-2925 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.0.0, 1.1.0 >Reporter: Fabiano V. Santos >Priority: Minor > Fix For: trunk > > > Any exception thrown during the graph database initialization only logs its > message, without the stack trace, so the real reason of a failure is not > logged. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
