[jira] [Updated] (ATLAS-4259) Swagger: Improve Header validation
[ https://issues.apache.org/jira/browse/ATLAS-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4259: Fix Version/s: 2.2.0 3.0.0 > Swagger: Improve Header validation > --- > > Key: ATLAS-4259 > URL: https://issues.apache.org/jira/browse/ATLAS-4259 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.1.0 >Reporter: Nikhil Bonte >Assignee: Nikhil P Bonte >Priority: Major > Labels: REST_API, swagger > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-4259-Swagger-Improve-Header-validation_v2.patch > > > This will add support for ATLAS-4064 in swagger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4259) Swagger: Improve Header validation
[ https://issues.apache.org/jira/browse/ATLAS-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4259: Affects Version/s: 2.1.0 > Swagger: Improve Header validation > --- > > Key: ATLAS-4259 > URL: https://issues.apache.org/jira/browse/ATLAS-4259 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.1.0 >Reporter: Nikhil Bonte >Assignee: Nikhil P Bonte >Priority: Major > Labels: REST_API, swagger > Attachments: ATLAS-4259-Swagger-Improve-Header-validation_v2.patch > > > This will add support for ATLAS-4064 in swagger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4259) Swagger: Improve Header validation
[ https://issues.apache.org/jira/browse/ATLAS-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4259: Attachment: (was: ATLAS-4259-Swagger-Improve-Header-validation-v1.patch) > Swagger: Improve Header validation > --- > > Key: ATLAS-4259 > URL: https://issues.apache.org/jira/browse/ATLAS-4259 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Nikhil Bonte >Assignee: Nikhil P Bonte >Priority: Major > Labels: REST_API, swagger > Attachments: ATLAS-4259-Swagger-Improve-Header-validation_v2.patch > > > This will add support for ATLAS-4064 in swagger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4259) Swagger: Improve Header validation
[ https://issues.apache.org/jira/browse/ATLAS-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4259: Attachment: ATLAS-4259-Swagger-Improve-Header-validation_v2.patch > Swagger: Improve Header validation > --- > > Key: ATLAS-4259 > URL: https://issues.apache.org/jira/browse/ATLAS-4259 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Nikhil Bonte >Assignee: Nikhil P Bonte >Priority: Major > Labels: REST_API, swagger > Attachments: ATLAS-4259-Swagger-Improve-Header-validation-v1.patch, > ATLAS-4259-Swagger-Improve-Header-validation_v2.patch > > > This will add support for ATLAS-4064 in swagger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4260) Swagger: click to expand API does not work properly in some cases
[ https://issues.apache.org/jira/browse/ATLAS-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17330480#comment-17330480 ] Nikhil Bonte commented on ATLAS-4260: - Known issue from original library - https://github.com/stoicflame/enunciate/issues/1081 > Swagger: click to expand API does not work properly in some cases > - > > Key: ATLAS-4260 > URL: https://issues.apache.org/jira/browse/ATLAS-4260 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nikhil Bonte >Assignee: Nikhil P Bonte >Priority: Major > Labels: rest_api, swagger > > Click on API POST /v2/entity also expands API POST /v2/entity/bulk & vice > versa > > Root Cause: > This is due to the same id of div element of both APIs. > The swagger spec has "operationId" same for both API. > > Need to check if any other API has the same issue. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4259) Swagger: Improve Header validation
[ https://issues.apache.org/jira/browse/ATLAS-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4259: Attachment: (was: ATLAS-4259-Swagger-Improve-Header-validation-v0.patch) > Swagger: Improve Header validation > --- > > Key: ATLAS-4259 > URL: https://issues.apache.org/jira/browse/ATLAS-4259 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Nikhil Bonte >Assignee: Nikhil P Bonte >Priority: Major > Labels: REST_API, swagger > Attachments: ATLAS-4259-Swagger-Improve-Header-validation-v1.patch > > > This will add support for ATLAS-4064 in swagger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4260) Swagger: click to expand API does not work properly in some cases
[ https://issues.apache.org/jira/browse/ATLAS-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4260: Description: Click on API POST /v2/entity also expands API POST /v2/entity/bulk & vice versa Root Cause: This is due to the same id of div element of both APIs. The swagger spec has "operationId" same for both API. Need to check if any other API has the same issue. > Swagger: click to expand API does not work properly in some cases > - > > Key: ATLAS-4260 > URL: https://issues.apache.org/jira/browse/ATLAS-4260 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nikhil Bonte >Priority: Major > Labels: rest_api, swagger > > Click on API POST /v2/entity also expands API POST /v2/entity/bulk & vice > versa > > Root Cause: > This is due to the same id of div element of both APIs. > The swagger spec has "operationId" same for both API. > > Need to check if any other API has the same issue. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4260) Swagger: click to expand API does not work properly in some cases
Nikhil Bonte created ATLAS-4260: --- Summary: Swagger: click to expand API does not work properly in some cases Key: ATLAS-4260 URL: https://issues.apache.org/jira/browse/ATLAS-4260 Project: Atlas Issue Type: Bug Reporter: Nikhil Bonte -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4260) Swagger: click to expand API does not work properly in some cases
[ https://issues.apache.org/jira/browse/ATLAS-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4260: Labels: rest_api swagger (was: ) > Swagger: click to expand API does not work properly in some cases > - > > Key: ATLAS-4260 > URL: https://issues.apache.org/jira/browse/ATLAS-4260 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nikhil Bonte >Priority: Major > Labels: rest_api, swagger > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4260) Swagger: click to expand API does not work properly in some cases
[ https://issues.apache.org/jira/browse/ATLAS-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4260: Component/s: atlas-core > Swagger: click to expand API does not work properly in some cases > - > > Key: ATLAS-4260 > URL: https://issues.apache.org/jira/browse/ATLAS-4260 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nikhil Bonte >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4259) Swagger: Improve Header validation
[ https://issues.apache.org/jira/browse/ATLAS-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17330428#comment-17330428 ] Nikhil Bonte commented on ATLAS-4259: - Tested manually, working fine. > Swagger: Improve Header validation > --- > > Key: ATLAS-4259 > URL: https://issues.apache.org/jira/browse/ATLAS-4259 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Nikhil Bonte >Priority: Major > Labels: REST_API, swagger > Attachments: ATLAS-4259-Swagger-Improve-Header-validation-v0.patch > > > This will add support for ATLAS-4064 in swagger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4259) Swagger: Improve Header validation
[ https://issues.apache.org/jira/browse/ATLAS-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4259: Attachment: ATLAS-4259-Swagger-Improve-Header-validation-v0.patch > Swagger: Improve Header validation > --- > > Key: ATLAS-4259 > URL: https://issues.apache.org/jira/browse/ATLAS-4259 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Nikhil Bonte >Priority: Major > Labels: REST_API, swagger > Attachments: ATLAS-4259-Swagger-Improve-Header-validation-v0.patch > > > This will add support for ATLAS-4064 in swagger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4259) Swagger: Improve Header validation
[ https://issues.apache.org/jira/browse/ATLAS-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4259: Description: This will add support for ATLAS-4064 in swagger. > Swagger: Improve Header validation > --- > > Key: ATLAS-4259 > URL: https://issues.apache.org/jira/browse/ATLAS-4259 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Nikhil Bonte >Priority: Major > Labels: REST_API, swagger > > This will add support for ATLAS-4064 in swagger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4259) Swagger: Improve Header validation
[ https://issues.apache.org/jira/browse/ATLAS-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4259: Component/s: atlas-core > Swagger: Improve Header validation > --- > > Key: ATLAS-4259 > URL: https://issues.apache.org/jira/browse/ATLAS-4259 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Nikhil Bonte >Priority: Major > Labels: REST_API, swagger > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4259) Swagger: Improve Header validation
[ https://issues.apache.org/jira/browse/ATLAS-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4259: Labels: REST_API swagger (was: ) > Swagger: Improve Header validation > --- > > Key: ATLAS-4259 > URL: https://issues.apache.org/jira/browse/ATLAS-4259 > Project: Atlas > Issue Type: Improvement >Reporter: Nikhil Bonte >Priority: Major > Labels: REST_API, swagger > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4259) Swagger: Improve Header validation
Nikhil Bonte created ATLAS-4259: --- Summary: Swagger: Improve Header validation Key: ATLAS-4259 URL: https://issues.apache.org/jira/browse/ATLAS-4259 Project: Atlas Issue Type: Improvement Reporter: Nikhil Bonte -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4251) Upgrade luceneMatchVersion in Solr configs
Nikhil Bonte created ATLAS-4251: --- Summary: Upgrade luceneMatchVersion in Solr configs Key: ATLAS-4251 URL: https://issues.apache.org/jira/browse/ATLAS-4251 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Nikhil Bonte Altas' Solr config currently has luceneMatchVersion as 5.0.0 This improvement will upgrade it to 8.4.1 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4214) UI: expand/collapse Technical properies of entity audits' tab not working properly
[ https://issues.apache.org/jira/browse/ATLAS-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4214: Description: An entity that has at least 2 audit entries has the following issues with expanding/collapsing Technical properties- Expand both audit entries, Technical properties are expanded by default, # Clicking on 1st audit record's Technical properties will collapse it(expected) along with changing the icon for 2nd audit record's Technical properties (it will be still in an expanded state but icon gives feel that it is collapsed) # Clicking on the 2nd audit record's Technical properties will expand/collapse the 1st audit record's Technical properties while it itself remains expanded. > UI: expand/collapse Technical properies of entity audits' tab not working > properly > -- > > Key: ATLAS-4214 > URL: https://issues.apache.org/jira/browse/ATLAS-4214 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Nikhil Bonte >Priority: Major > > An entity that has at least 2 audit entries has the following issues with > expanding/collapsing Technical properties- > Expand both audit entries, Technical properties are expanded by default, > # Clicking on 1st audit record's Technical properties will collapse > it(expected) along with changing the icon for 2nd audit record's Technical > properties (it will be still in an expanded state but icon gives feel that it > is collapsed) > # Clicking on the 2nd audit record's Technical properties will > expand/collapse the 1st audit record's Technical properties while it itself > remains expanded. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4214) UI: expand/collapse Technical properies of entity audits' tab not working properly
Nikhil Bonte created ATLAS-4214: --- Summary: UI: expand/collapse Technical properies of entity audits' tab not working properly Key: ATLAS-4214 URL: https://issues.apache.org/jira/browse/ATLAS-4214 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Nikhil Bonte -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4206) Swagger: Upload APIs does not work
Nikhil Bonte created ATLAS-4206: --- Summary: Swagger: Upload APIs does not work Key: ATLAS-4206 URL: https://issues.apache.org/jira/browse/ATLAS-4206 Project: Atlas Issue Type: Improvement Components: atlas-core Affects Versions: 2.1.0 Reporter: Nikhil Bonte APIs affected: POST /v2/glossary/import POST /v2/entity/businessmetadata/import # Swagger UI for the above APIs shows two params _fileDetail_ & _inputStream_ both of type _file_, the expectation is to have the only _inputStream_ to upload a file. # Param _inputStream_ have name as "_inputStream_", expected name is "_file_". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4206) Swagger: File upload APIs does not work
[ https://issues.apache.org/jira/browse/ATLAS-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4206: Summary: Swagger: File upload APIs does not work (was: Swagger: Upload APIs does not work) > Swagger: File upload APIs does not work > --- > > Key: ATLAS-4206 > URL: https://issues.apache.org/jira/browse/ATLAS-4206 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.1.0 >Reporter: Nikhil Bonte >Priority: Major > Labels: REST_API, swagger > > APIs affected: > POST /v2/glossary/import > POST /v2/entity/businessmetadata/import > > # Swagger UI for the above APIs shows two params _fileDetail_ & > _inputStream_ both of type _file_, the expectation is to have the only > _inputStream_ to upload a file. > # Param _inputStream_ have name as "_inputStream_", expected name is > "_file_". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4100) Recent datamodel changes (Jan 2021) broke our installation
[
https://issues.apache.org/jira/browse/ATLAS-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17264633#comment-17264633
]
Nikhil Bonte commented on ATLAS-4100:
-
[~nevi_me]
{quote}I can see the entity count on the sidebar
{quote}
Based on this I assume that typeDefs API returns type definitions (GET
/v2/types/typedefs)
{quote}and inspecting the API shows that it retrieves information, but that
information can't be shown.
{quote}
Not clear which API, but I guess you are referring to search API & it returns
search results but results are not being rendered on UI.
If that is the case, there might some issue with UI, please check the console
tab from the browser's developer tools if it has any clue.
{quote}The export API isn't working,...
{quote}
Could you please tell us more about what is the issue with export API?
> Recent datamodel changes (Jan 2021) broke our installation
> --
>
> Key: ATLAS-4100
> URL: https://issues.apache.org/jira/browse/ATLAS-4100
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Neville Dipale
>Priority: Critical
>
> Hi Atlas developers
> We run an Atlas installation (with external Cassandra & ElasticSearch) where
> we build Atlas via a Docker script, pointing to specific git commits.
> The last update we have was from early December 2020. Yesterday I updated to
> the latest git tree, but after the update, the Atlas UI doesn't show
> entities. I can see the entity count on the sidebar, and inspecting the API
> shows that it retrieves information, but that information can't be shown.
> I suspect that the changes to the cloud datamodel could be the cause (or at
> least one of the causes). ATLAS-4082 created patches to the Azure entity
> definitions, but ATLAS-4083 directly modified the entity definitions. I can't
> definitively pinpoint the issue, but I noticed the issue with no longer being
> able to view data, after trying to apply the changes to ATLAS-4083 to our
> installation.
> The export API isn't working, so we have no viable alternative but to try
> extract the data manually from Cassandra, or worse, to destroy our data &
> start from scratch.
> Further, I unfortunately don't have any logs to attach, because in order for
> us to run Atlas with LDAP integration + a keystore file, the way we run Atlas
> (going in the container to manually start each time) doesn't output logs,
> even though we have configured the log4j.xml file propertly.
> I suppose I'm opening this in case other people come across this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3913) Swagger documentation for APIs
[ https://issues.apache.org/jira/browse/ATLAS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3913: Attachment: how_to_navigate.png swagger_rest_api_doc_page.png > Swagger documentation for APIs > -- > > Key: ATLAS-3913 > URL: https://issues.apache.org/jira/browse/ATLAS-3913 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 2.1.0 >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > Labels: REST_API, swagger > Fix For: 3.0.0, 2.2.0 > > Attachments: how_to_navigate.png, swagger_rest_api_doc_page.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Current packaging does not package swagger ui into Atlas war. > This change will pack swagger ui into the war file. > Also update enunciate version from 2.11.1 to 2.13.2 > h3. Approach: > * Update enuntiate plugin version from 2.11.1 to 2.13.2 > * Download latest swagger-ui from > [https://github.com/swagger-api/swagger-ui/archive/v3.36.2.zip] & extract. > * Move swagger-ui-3.36.2/dist/ to > build-tools/src/main/resources/ui-dist > * Update swagger tag in enuntiate.xml > * Inside build-tools/src/main/resources/ui-dist : > * Create index.js > * Modify SwaggerUIBundle object in ui-dist/index.html to load index.js along > with following: > 1. Modify url to load swagger.json > 2. Add requestInterceptor > * Updated Header.js, UrlLinks.js, Header.html to add API documentation menu. > > h3. How to navigate to the documentation page? > -> Once Atlas UI is loaded, goto Logged-in-User -> Help -> API Documentation > (see attached screenshot for reference) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3913) Swagger documentation for APIs
[ https://issues.apache.org/jira/browse/ATLAS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3913: Description: Current packaging does not package swagger ui into Atlas war. This change will pack swagger ui into the war file. Also update enunciate version from 2.11.1 to 2.13.2 h3. Approach: * Update enuntiate plugin version from 2.11.1 to 2.13.2 * Download latest swagger-ui from [https://github.com/swagger-api/swagger-ui/archive/v3.36.2.zip] & extract. * Move swagger-ui-3.36.2/dist/ to build-tools/src/main/resources/ui-dist * Update swagger tag in enuntiate.xml * Inside build-tools/src/main/resources/ui-dist : * Create index.js * Modify SwaggerUIBundle object in ui-dist/index.html to load index.js along with following: 1. Modify url to load swagger.json 2. Add requestInterceptor * Updated Header.js, UrlLinks.js, Header.html to add API documentation menu. h3. How to navigate to the documentation page? -> Once Atlas UI is loaded, goto Logged-in-User -> Help -> API Documentation (see attached screenshot for reference) was: Current packaging does not package swagger ui into Atlas war. This change will pack swagger ui into the war file. Also update enunciate version from 2.11.1 to 2.13.2 h2. Approach: * Update enuntiate plugin version from 2.11.1 to 2.13.2 * Download latest swagger-ui from [https://github.com/swagger-api/swagger-ui/archive/v3.36.2.zip] & extract. * Move swagger-ui-3.36.2/dist/ to build-tools/src/main/resources/ui-dist * Update swagger tag in enuntiate.xml * Inside build-tools/src/main/resources/ui-dist : * Create index.js * Modify SwaggerUIBundle object in ui-dist/index.html to load index.js along with following: 1 modify url to load swagger.json 2 Add requestInterceptor * Updated Header.js, UrlLinks.js, Header.html to add API documentation menu. h2. How to navigate to the documentation page? -> Once Atlas UI is loaded, goto Logged-in-User -> Help -> API Documentation (see attached screenshot for reference) > Swagger documentation for APIs > -- > > Key: ATLAS-3913 > URL: https://issues.apache.org/jira/browse/ATLAS-3913 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 2.1.0 >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > Labels: REST_API, swagger > Fix For: 3.0.0, 2.2.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Current packaging does not package swagger ui into Atlas war. > This change will pack swagger ui into the war file. > Also update enunciate version from 2.11.1 to 2.13.2 > h3. Approach: > * Update enuntiate plugin version from 2.11.1 to 2.13.2 > * Download latest swagger-ui from > [https://github.com/swagger-api/swagger-ui/archive/v3.36.2.zip] & extract. > * Move swagger-ui-3.36.2/dist/ to > build-tools/src/main/resources/ui-dist > * Update swagger tag in enuntiate.xml > * Inside build-tools/src/main/resources/ui-dist : > * Create index.js > * Modify SwaggerUIBundle object in ui-dist/index.html to load index.js along > with following: > 1. Modify url to load swagger.json > 2. Add requestInterceptor > * Updated Header.js, UrlLinks.js, Header.html to add API documentation menu. > > h3. How to navigate to the documentation page? > -> Once Atlas UI is loaded, goto Logged-in-User -> Help -> API Documentation > (see attached screenshot for reference) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3913) Swagger documentation for APIs
[ https://issues.apache.org/jira/browse/ATLAS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3913: Description: Current packaging does not package swagger ui into Atlas war. This change will pack swagger ui into the war file. Also update enunciate version from 2.11.1 to 2.13.2 h2. Approach: * Update enuntiate plugin version from 2.11.1 to 2.13.2 * Download latest swagger-ui from [https://github.com/swagger-api/swagger-ui/archive/v3.36.2.zip] & extract. * Move swagger-ui-3.36.2/dist/ to build-tools/src/main/resources/ui-dist * Update swagger tag in enuntiate.xml * Inside build-tools/src/main/resources/ui-dist : * Create index.js * Modify SwaggerUIBundle object in ui-dist/index.html to load index.js along with following: 1 modify url to load swagger.json 2 Add requestInterceptor * Updated Header.js, UrlLinks.js, Header.html to add API documentation menu. h2. How to navigate to the documentation page? -> Once Atlas UI is loaded, goto Logged-in-User -> Help -> API Documentation (see attached screenshot for reference) was: Current packaging does not package swagger ui into Atlas war. This change will pack swagger ui into the war file. Also update enunciate version from 2.11.1 to 2.13.2 > Swagger documentation for APIs > -- > > Key: ATLAS-3913 > URL: https://issues.apache.org/jira/browse/ATLAS-3913 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 2.1.0 >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > Labels: REST_API, swagger > Fix For: 3.0.0, 2.2.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Current packaging does not package swagger ui into Atlas war. > This change will pack swagger ui into the war file. > Also update enunciate version from 2.11.1 to 2.13.2 > > h2. Approach: > * Update enuntiate plugin version from 2.11.1 to 2.13.2 > * Download latest swagger-ui from > [https://github.com/swagger-api/swagger-ui/archive/v3.36.2.zip] & extract. > * Move swagger-ui-3.36.2/dist/ to > build-tools/src/main/resources/ui-dist > * Update swagger tag in enuntiate.xml > * Inside build-tools/src/main/resources/ui-dist : > * Create index.js > * Modify SwaggerUIBundle object in ui-dist/index.html to load index.js along > with following: > 1 modify url to load swagger.json > 2 Add requestInterceptor > * Updated Header.js, UrlLinks.js, Header.html to add API documentation menu. > > h2. How to navigate to the documentation page? > -> Once Atlas UI is loaded, goto Logged-in-User -> Help -> API Documentation > (see attached screenshot for reference) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3913) Swagger documentation for APIs
[ https://issues.apache.org/jira/browse/ATLAS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3913: Description: Current packaging does not package swagger ui into Atlas war. This change will pack swagger ui into the war file. Also update enunciate version from 2.11.1 to 2.13.2 was: Current packaging does not package swagger ui into Atlas war. This change will pack swagger ui into the war file. Also update enunciate version from 2.11.1 to 2.13.1 > Swagger documentation for APIs > -- > > Key: ATLAS-3913 > URL: https://issues.apache.org/jira/browse/ATLAS-3913 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 2.1.0 >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > Labels: REST_API, swagger > Fix For: 3.0.0, 2.2.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Current packaging does not package swagger ui into Atlas war. > This change will pack swagger ui into the war file. > Also update enunciate version from 2.11.1 to 2.13.2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3913) Swagger documentation for APIs
[ https://issues.apache.org/jira/browse/ATLAS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte resolved ATLAS-3913. - Resolution: Fixed > Swagger documentation for APIs > -- > > Key: ATLAS-3913 > URL: https://issues.apache.org/jira/browse/ATLAS-3913 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 2.1.0 >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > Labels: REST_API, swagger > Fix For: 3.0.0, 2.2.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Current packaging does not package swagger ui into Atlas war. > This change will pack swagger ui into the war file. > Also update enunciate version from 2.11.1 to 2.13.1 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3816) Backport: Basic search issue with IndexSerializer
[
https://issues.apache.org/jira/browse/ATLAS-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224521#comment-17224521
]
Nikhil Bonte commented on ATLAS-3816:
-
committed to branch-0.8 - 63e3d5c9e5e74f1110d80c7bcfce970725504888
[https://github.com/apache/atlas/commit/63e3d5c9e5e74f1110d80c7bcfce970725504888]
> Backport: Basic search issue with IndexSerializer
> -
>
> Key: ATLAS-3816
> URL: https://issues.apache.org/jira/browse/ATLAS-3816
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8.4
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: 0.8.4
>
> Attachments:
> ATLAS-3816-Backport-Basic-search-issue-with-IndexSer-v2.patch
>
>
> *Background:*
> Atlas instance with property
> _"atlas.use.index.query.to.find.entity.by.unique.attributes=true"_
> Direct index query which has pattern *"v."* throws exception, e.g.
>
> v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
>
> This will throw
> {code:java}
> java.lang.IllegalArgumentException: Found reference to non-existant property
> key in query at position...{code}
>
> *Solution:*
> Backporting ATLAS-2371.
> It is resolved with janusgraph, for titan implementation backporting required.
> Query will be :
> *$v$*"Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
>
> Default value for index search prefix is _"$v$"_
> Can be changed using the property _"atlas.graph.index.search.vertex.prefix"_
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3816) Backport: Basic search issue with IndexSerializer
[
https://issues.apache.org/jira/browse/ATLAS-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3816:
Fix Version/s: 0.8.4
> Backport: Basic search issue with IndexSerializer
> -
>
> Key: ATLAS-3816
> URL: https://issues.apache.org/jira/browse/ATLAS-3816
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8.4
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: 0.8.4
>
> Attachments:
> ATLAS-3816-Backport-Basic-search-issue-with-IndexSer-v2.patch
>
>
> *Background:*
> Atlas instance with property
> _"atlas.use.index.query.to.find.entity.by.unique.attributes=true"_
> Direct index query which has pattern *"v."* throws exception, e.g.
>
> v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
>
> This will throw
> {code:java}
> java.lang.IllegalArgumentException: Found reference to non-existant property
> key in query at position...{code}
>
> *Solution:*
> Backporting ATLAS-2371.
> It is resolved with janusgraph, for titan implementation backporting required.
> Query will be :
> *$v$*"Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
>
> Default value for index search prefix is _"$v$"_
> Can be changed using the property _"atlas.graph.index.search.vertex.prefix"_
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4008) Cache getGuid and getStatus in GraphTransactionInterceptor
[ https://issues.apache.org/jira/browse/ATLAS-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte resolved ATLAS-4008. - Fix Version/s: 2.2.0 3.0.0 Resolution: Done > Cache getGuid and getStatus in GraphTransactionInterceptor > -- > > Key: ATLAS-4008 > URL: https://issues.apache.org/jira/browse/ATLAS-4008 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: > ATLAS-4008-Cache-getGuid-and-getStatus-in-GraphTrans-v1.patch > > > *Problem Statement:* > GraphHelper.getGuid() & GraphHelper.getStatus() causes overhead when called > multiple times in a same request. > > *Approach:* > Implement a caching mechanism in GraphTransactionInterceptor to cache the > following mappings: > *vertexID -> guid* > *vertexID -> entityStatus* > *edgeId -> status* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4008) Cache getGuid and getStatus in GraphTransactionInterceptor
[ https://issues.apache.org/jira/browse/ATLAS-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4008: Attachment: ATLAS-4008-Cache-getGuid-and-getStatus-in-GraphTrans-v1.patch > Cache getGuid and getStatus in GraphTransactionInterceptor > -- > > Key: ATLAS-4008 > URL: https://issues.apache.org/jira/browse/ATLAS-4008 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > Attachments: > ATLAS-4008-Cache-getGuid-and-getStatus-in-GraphTrans-v1.patch > > > *Problem Statement:* > GraphHelper.getGuid() & GraphHelper.getStatus() causes overhead when called > multiple times in a same request. > > *Approach:* > Implement a caching mechanism in GraphTransactionInterceptor to cache the > following mappings: > *vertexID -> guid* > *vertexID -> entityStatus* > *edgeId -> status* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4008) Cache getGuid and getStatus in GraphTransactionInterceptor
[ https://issues.apache.org/jira/browse/ATLAS-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-4008: Description: *Problem Statement:* GraphHelper.getGuid() & GraphHelper.getStatus() causes overhead when called multiple times in a same request. *Approach:* Implement a caching mechanism in GraphTransactionInterceptor to cache the following mappings: *vertexID -> guid* *vertexID -> entityStatus* *edgeId -> status* was: *Problem Statement:* GraphHelper.getGuid() & GraphHelper.getStatus() causes overhead when called multiple times in a same request. *Approach:* Implement a caching mechanism in GraphTransactionInterceptor to cache the following mappings: *vertexID -> guid* *vertexID -> entityStatus* > Cache getGuid and getStatus in GraphTransactionInterceptor > -- > > Key: ATLAS-4008 > URL: https://issues.apache.org/jira/browse/ATLAS-4008 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > > *Problem Statement:* > GraphHelper.getGuid() & GraphHelper.getStatus() causes overhead when called > multiple times in a same request. > > *Approach:* > Implement a caching mechanism in GraphTransactionInterceptor to cache the > following mappings: > *vertexID -> guid* > *vertexID -> entityStatus* > *edgeId -> status* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4008) Cache getGuid and getStatus in GraphTransactionInterceptor
Nikhil Bonte created ATLAS-4008: --- Summary: Cache getGuid and getStatus in GraphTransactionInterceptor Key: ATLAS-4008 URL: https://issues.apache.org/jira/browse/ATLAS-4008 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Nikhil Bonte Assignee: Nikhil Bonte *Problem Statement:* GraphHelper.getGuid() & GraphHelper.getStatus() causes overhead when called multiple times in a same request. *Approach:* Implement a caching mechanism in GraphTransactionInterceptor to cache the following mappings: *vertexID -> guid* *vertexID -> entityStatus* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3953) JSON Files from Export API with "?" char for string with special chars
[ https://issues.apache.org/jira/browse/ATLAS-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17205237#comment-17205237 ] Nikhil Bonte commented on ATLAS-3953: - +1 for the patch. Thanks [~amestry]. > JSON Files from Export API with "?" char for string with special chars > --- > > Key: ATLAS-3953 > URL: https://issues.apache.org/jira/browse/ATLAS-3953 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.1.0 > Environment: Apache Atlas 2.1.0 embedded HBASE and SOLR >Reporter: Carlos Alberto Rocha Cardoso >Assignee: Ashutosh Mestry >Priority: Major > Attachments: 9fdc3ad0-46c2-430a-89c4-4a751d31c064.json, > ATLAS-3953-Export-ZipSink-Specify-character-endcodin.patch, > Asset_Imported.PNG, AtlasServer.PNG, > a5c148bf-5ab6-4c49-853e-855842102128.json, atlas_export.zip, path.zip > > > The Export API returns a ZIP file with some JSON files describing Atlas > Entities and TypeDefs. > I am having an issue where some special chars in JSON are being replaced by > "?" chars. > An Entity name like "Distribuição" was exported in JSON file like > "Distribui??o". The special chars "çã" was replaced for the "??" chars. > I tried to change the exported JSON file encoding and the request header for > Export API but without success. > After analyzing the Atlas source code, especially the *splitAndWriteBytes* > method of the > *[ZipSink|https://github.com/apache/atlas/blob/cc601d7371fae1dbc16b55d1ca84f06b745700dc/repository/src/main/java/org/apache/atlas/repository/impexp/ZipSink.java] > class*, I thought if maybe the problem is because the *s.getBytes()* is > returning the JSON string to be written to ZIP with another encoding than > *UTF-8*, and maybe set the encode like *s.getBytes(StandardCharsets.UTF_8)* > could be a solution. > It's my first contact with the Atlas source code, and I'm not a JAVA > programmer, so it's only a guess. > I saw that it's possible to set the default to encode to the platform or JVM, > but how they said in this below discussion, perhaps this doesn't work > properly in all situations. > [https://stackoverflow.com/questions/361975/setting-the-default-java-character-encoding] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3827) UI: Use moment date format instead of default date format.
[
https://issues.apache.org/jira/browse/ATLAS-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17197438#comment-17197438
]
Nikhil Bonte commented on ATLAS-3827:
-
+1 for the patch, thanks [~kevalbhatt].
> UI: Use moment date format instead of default date format.
> --
>
> Key: ATLAS-3827
> URL: https://issues.apache.org/jira/browse/ATLAS-3827
> Project: Atlas
> Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: ATLAS-3827-1.patch, ATLAS-3827.patch,
> image-2020-09-16-17-11-33-386.png, image-2020-09-16-17-12-04-512.png,
> new_date_format.png
>
>
>
> UI configured to use the following date formats:
> {code:java}
> /MM/DD
> /MM/DD HH:mm:ss
> MM/DD/ h:mm A z
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3945) UI: Entity details page, Show N/A for date if date value is 0 or null
[ https://issues.apache.org/jira/browse/ATLAS-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17197436#comment-17197436 ] Nikhil Bonte commented on ATLAS-3945: - +1 for the patch, thanks [~kevalbhatt]. > UI: Entity details page, Show N/A for date if date value is 0 or null > -- > > Key: ATLAS-3945 > URL: https://issues.apache.org/jira/browse/ATLAS-3945 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3945.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3932) Upgrade Spring security , libpam4j and jna lib version
[ https://issues.apache.org/jira/browse/ATLAS-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190094#comment-17190094 ] Nikhil Bonte commented on ATLAS-3932: - +1 for the patch. Thanks [~nixon]. > Upgrade Spring security , libpam4j and jna lib version > -- > > Key: ATLAS-3932 > URL: https://issues.apache.org/jira/browse/ATLAS-3932 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.1.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: > 0001-ATLAS-3932-Upgrade-jna-spring.security-and-libpam4j-.patch > > > Upgrade jna lib version from 4.1.0 to 5.2.0 > Upgrade libpam4j lib version from 1.8 to 1.11 > and Upgrade Spring security version from 4.2.16.RELEASE to 4.2.17.RELEASE -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3913) Swagger documentation for APIs
[ https://issues.apache.org/jira/browse/ATLAS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3913: Description: Current packaging does not package swagger ui into Atlas war. This change will pack swagger ui into the war file. Also update enunciate version from 2.11.1 to 2.13.1 was: Current packaging does not package swagger ui into Atlas war. This change will pack swagger ui into war. Also update enunciate version from 2.11.1 to 2.13.1 > Swagger documentation for APIs > -- > > Key: ATLAS-3913 > URL: https://issues.apache.org/jira/browse/ATLAS-3913 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > > Current packaging does not package swagger ui into Atlas war. > This change will pack swagger ui into the war file. > Also update enunciate version from 2.11.1 to 2.13.1 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3913) Swagger documentation for APIs
Nikhil Bonte created ATLAS-3913: --- Summary: Swagger documentation for APIs Key: ATLAS-3913 URL: https://issues.apache.org/jira/browse/ATLAS-3913 Project: Atlas Issue Type: Bug Components: atlas-core, atlas-webui Reporter: Nikhil Bonte Assignee: Nikhil Bonte Enunciate does not package swagger ui into Atlas war. This change will pack swagger ui into war. Also update enunciate version from 2.11.1 to 2.13.1 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3913) Swagger documentation for APIs
[ https://issues.apache.org/jira/browse/ATLAS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3913: Description: Current packaging does not package swagger ui into Atlas war. This change will pack swagger ui into war. Also update enunciate version from 2.11.1 to 2.13.1 was: Enunciate does not package swagger ui into Atlas war. This change will pack swagger ui into war. Also update enunciate version from 2.11.1 to 2.13.1 > Swagger documentation for APIs > -- > > Key: ATLAS-3913 > URL: https://issues.apache.org/jira/browse/ATLAS-3913 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > > Current packaging does not package swagger ui into Atlas war. > This change will pack swagger ui into war. > Also update enunciate version from 2.11.1 to 2.13.1 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3909) UI: Improve readability for the table view in the entity detail page
[ https://issues.apache.org/jira/browse/ATLAS-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17169969#comment-17169969 ] Nikhil Bonte commented on ATLAS-3909: - +1 for the patch, thanks [~kevalbhatt]. > UI: Improve readability for the table view in the entity detail page > - > > Key: ATLAS-3909 > URL: https://issues.apache.org/jira/browse/ATLAS-3909 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3909.patch, image-2020-08-03-12-48-10-984.png, > image-2020-08-03-12-48-28-192.png > > > Change the key style to bold for table view in the entity details page. > > !image-2020-08-03-12-48-10-984.png|width=508,height=311! > *Expected:* > !image-2020-08-03-12-48-28-192.png|width=541,height=341! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (ATLAS-3909) UI: Improve readability for the table view in the entity detail page
[ https://issues.apache.org/jira/browse/ATLAS-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3909: Comment: was deleted (was: +1 for the patch, thanks [~kevalbhatt] .) > UI: Improve readability for the table view in the entity detail page > - > > Key: ATLAS-3909 > URL: https://issues.apache.org/jira/browse/ATLAS-3909 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: image-2020-08-03-12-48-10-984.png, > image-2020-08-03-12-48-28-192.png > > > Change the key style to bold for table view in the entity details page. > > !image-2020-08-03-12-48-10-984.png|width=508,height=311! > *Expected:* > !image-2020-08-03-12-48-28-192.png|width=541,height=341! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3909) UI: Improve readability for the table view in the entity detail page
[ https://issues.apache.org/jira/browse/ATLAS-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17169961#comment-17169961 ] Nikhil Bonte commented on ATLAS-3909: - +1 for the patch, thanks [~kevalbhatt] . > UI: Improve readability for the table view in the entity detail page > - > > Key: ATLAS-3909 > URL: https://issues.apache.org/jira/browse/ATLAS-3909 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: ATLAS-3909.patch, image-2020-08-03-12-48-10-984.png, > image-2020-08-03-12-48-28-192.png > > > Change the key style to bold for table view in the entity details page. > > !image-2020-08-03-12-48-10-984.png|width=508,height=311! > *Expected:* > !image-2020-08-03-12-48-28-192.png|width=541,height=341! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3879) Ozone: ozone_key entity is directly created under ozone_bucket
[
https://issues.apache.org/jira/browse/ATLAS-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3879:
Description:
The support for Apache Ozone was added in ATLAS-3836. Currently, ozone_key
entity is getting created under ozone_bucket, but there is no support to create
a hierarchy of parent ozone_key and child ozone_key.
e.g.
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
This query will create only 1 ozone_key directly under bucket "bucket1".
Created entities :
* o3fs://volume1@cm (ozone_volume)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm (ozone_key)
This Jira will improve implementation to support creating the hierarchy of
ozone_keys.
With this, above query will result into following entites
* o3fs://volume1@cm (ozone_volume)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/@cm (ozone_key) *child of ozone_bucket*
* o3fs://bucket1.volume1.ozone1/sale1/q1/@cm (ozone_key) *child of ozone_key*
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales/@cm (ozone_key) *child of
ozone_key*
This will bring Ozone model to be consistent with AWS S3 v2 and ADLS-Gen2
models.
was:
The support for Apache Ozone was added in ATLAS-3836. Currently, ozone_key
entity is getting created under ozone_bucket, but there is no support to create
a hierarchy of parent ozone_key and child ozone_key.
e.g.
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
This query will create only 1 ozone_key directly under bucket "bucket1".
Created entities :
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm (ozone_key)
This Jira will improve implementation to support creating the hierarchy of
ozone_keys.
With this, above query will result into following entites
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/@cm (ozone_key) *child of ozone_bucket*
* o3fs://bucket1.volume1.ozone1/sale1/q1/@cm (ozone_key) *child of ozone_key*
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales/@cm (ozone_key) *child of
ozone_key*
This will bring Ozone model to be consistent with AWS S3 v2 and ADLS-Gen2
models.
> Ozone: ozone_key entity is directly created under ozone_bucket
> --
>
> Key: ATLAS-3879
> URL: https://issues.apache.org/jira/browse/ATLAS-3879
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: 2.1.0, 3.0.0
>
>
> The support for Apache Ozone was added in ATLAS-3836. Currently, ozone_key
> entity is getting created under ozone_bucket, but there is no support to
> create a hierarchy of parent ozone_key and child ozone_key.
>
> e.g.
> {code:java}
> -> CREATE EXTERNAL TABLE sales (id int) row format delimited fields
> terminated by ' ' stored as textfile location
> 'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
> This query will create only 1 ozone_key directly under bucket "bucket1".
> Created entities :
> * o3fs://volume1@cm (ozone_volume)
> * o3fs://volume1.bucket1@cm (ozone_bucket)
> * o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm (ozone_key)
>
> This Jira will improve implementation to support creating the hierarchy of
> ozone_keys.
> With this, above query will result into following entites
> * o3fs://volume1@cm (ozone_volume)
> * o3fs://volume1.bucket1@cm (ozone_bucket)
> * o3fs://bucket1.volume1.ozone1/sale1/@cm (ozone_key) *child of ozone_bucket*
> * o3fs://bucket1.volume1.ozone1/sale1/q1/@cm (ozone_key) *child of ozone_key*
> * o3fs://bucket1.volume1.ozone1/sale1/q1/sales/@cm (ozone_key) *child of
> ozone_key*
>
> This will bring Ozone model to be consistent with AWS S3 v2 and ADLS-Gen2
> models.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3885) import-hive.sh: Hive entities with Ozone location created by import-hive.sh creates hdfs_path entity instead of ozone in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3885: Description: import-hive.sh when attempts to import hive entities with Ozone location expected is that ozone_key should get created as path entity, but script creates hdfs_path entity instead of ozone_key in Atlas. Steps to reproduce # Disable HMS Hook and Hive Hook # Create external table with ozone location # Run import-hive.sh The location entity is created as an hdfs_path entity instead of ozone_key. was: import-hive.sh when attempts to import hive entities with Ozone location expected is that ozone_key should get created as path entity, but script creates hdfs_path entity instead of ozone_key in Atlas. Steps to reproduce # Disable HMS Hook and Hive Hook # Create external table with ozone location # Run import-hive.sh The location entity is created as an hdfs_path entity instead of ozone_key. > import-hive.sh: Hive entities with Ozone location created by import-hive.sh > creates hdfs_path entity instead of ozone in Atlas > -- > > Key: ATLAS-3885 > URL: https://issues.apache.org/jira/browse/ATLAS-3885 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > Labels: ozone > > import-hive.sh when attempts to import hive entities with Ozone location > expected is that ozone_key should get created as path entity, but script > creates hdfs_path entity instead of ozone_key in Atlas. > > Steps to reproduce > # Disable HMS Hook and Hive Hook > # Create external table with ozone location > # Run import-hive.sh > The location entity is created as an hdfs_path entity instead of ozone_key. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3885) import-hive.sh: Hive entities with Ozone location created by import-hive.sh creates hdfs_path entity instead of ozone in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3885: Description: import-hive.sh when attempts to import hive entities with Ozone location expected is that ozone_key should get created as path entity, but script creates hdfs_path entity instead of ozone_key in Atlas. Steps to reproduce # Disable HMS Hook and Hive Hook # Create external table with ozone location # Run import-hive.sh The location entity is created as an hdfs_path entity instead of ozone_key. was: import-hive.sh when attempts to import hive entities with Ozone location expected is that ozone_key will get created as path entity, but script creates hdfs_path entity instead of ozone_key in Atlas. Steps to reproduce # Disable HMS Hook and Hive Hook # Create external table with ozone location # Run import-hive.sh The location entity is created as an hdfs_path entity instead of ozone_key. > import-hive.sh: Hive entities with Ozone location created by import-hive.sh > creates hdfs_path entity instead of ozone in Atlas > -- > > Key: ATLAS-3885 > URL: https://issues.apache.org/jira/browse/ATLAS-3885 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > Labels: ozone > > import-hive.sh when attempts to import hive entities with Ozone location > expected is that ozone_key should get created as path entity, but script > creates hdfs_path entity instead of ozone_key in Atlas. > > Steps to reproduce > # Disable HMS Hook and Hive Hook > # Create external table with ozone location > # Run import-hive.sh > > The location entity is created as an hdfs_path entity instead of ozone_key. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3885) import-hive.sh: Hive entities with Ozone location created by import-hive.sh creates hdfs_path entity instead of ozone in Atlas
Nikhil Bonte created ATLAS-3885: --- Summary: import-hive.sh: Hive entities with Ozone location created by import-hive.sh creates hdfs_path entity instead of ozone in Atlas Key: ATLAS-3885 URL: https://issues.apache.org/jira/browse/ATLAS-3885 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 2.0.0 Reporter: Nikhil Bonte Assignee: Nikhil Bonte import-hive.sh when attempts to import hive entities with Ozone location expected is that ozone_key will get created as path entity, but script creates hdfs_path entity instead of ozone_key in Atlas. Steps to reproduce # Disable HMS Hook and Hive Hook # Create external table with ozone location # Run import-hive.sh The location entity is created as an hdfs_path entity instead of ozone_key. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3836) Add Apache Ozone support in hive hook
[
https://issues.apache.org/jira/browse/ATLAS-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3836:
Description:
Apache Ozone is the new object store for Hadoop -
[https://hadoop.apache.org/ozone/]
Apache Atlas needs to add entity types to support creation of Ozone entities.
Hive hook should also be updated to create lineage between ozone entities and
hive tables (for EXTERNAL TABLE)
+*Approach :*+
# Refactored BaseHiveEvent.getPathEntity() -> moved to
AtlasPathExtractorUtil.java
# Created PathExtractorContext.java to wrap most arguments.
# AtlasPathExtractorUtil.getPathEntity() -> accept Path, PathExtractorContext
-> return AtlasEntityWithExtInfo
# Added specific condition in AtlasPathExtractorUtil.getPathEntity() to handle
Ozone path
-> path starts with "ofs://" or "o3fs://"
# Added UT around AtlasPathExtractorUtil.getPathEntity() ->
AtlasPathExtractorUtilTest.java
+*Examples :*+
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
|| ||Name||Qualified Name||
|ozone_key|/sale1/q1/sales|o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks (id int) row format delimited fields terminated
by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket1.volume1.ozone1/stocks.txt' into table
stocks;
{code}
|| ||Name||Qualified Name||
|ozone_key|/stocks.txt|o3fs://bucket1.volume1.ozone1/stocks.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks_q1 (id int) row format delimited fields
terminated by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket1.volume1.ozone1/quarter1/stocks_q1.txt' into
table stocks_q1;{code}
|| ||Name||Qualified Name||
|ozone_key|/quarter1/stocks_q1.txt|o3fs://bucket1.volume1.ozone1/quarter1/stocks_q1.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
*Note:* The approach has been updated in ATLAS-3879
was:
Apache Ozone is the new object store for Hadoop -
[https://hadoop.apache.org/ozone/]
Apache Atlas needs to add entity types to support creation of Ozone entities.
Hive hook should also be updated to create lineage between ozone entities and
hive tables (for EXTERNAL TABLE)
+*Approach :*+
# Refactored BaseHiveEvent.getPathEntity() -> moved to
AtlasPathExtractorUtil.java
# Created PathExtractorContext.java to wrap most arguments.
# AtlasPathExtractorUtil.getPathEntity() -> accept Path, PathExtractorContext
-> return AtlasEntityWithExtInfo
# Added specific condition in AtlasPathExtractorUtil.getPathEntity() to handle
Ozone path
-> path starts with "ofs://" or "o3fs://"
# Added UT around AtlasPathExtractorUtil.getPathEntity() ->
AtlasPathExtractorUtilTest.java
+*Examples :*+
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
|| ||Name||Qualified Name||
|ozone_key|/sale1/q1/sales|o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks (id int) row format delimited fields terminated
by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket1.volume1.ozone1/stocks.txt' into table
stocks;
{code}
|| ||Name||Qualified Name||
|ozone_key|/stocks.txt|o3fs://bucket1.volume1.ozone1/stocks.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks_q1 (id int) row format delimited fields
terminated by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket1.volume1.ozone1/quarter1/stocks_q1.txt' into
table stocks_q1;{code}
|| ||Name||Qualified Name||
|ozone_key|/quarter1/stocks_q1.txt|o3fs://bucket1.volume1.ozone1/quarter1/stocks_q1.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
> Add Apache Ozone support in hive hook
> -
>
> Key: ATLAS-3836
> URL: https://issues.apache.org/jira/browse/ATLAS-3836
> Project: Atlas
> Issue Type: New Feature
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Nikhil Bonte
>Priority: Major
> Labels: hive-hooks, ozone
> Fix For: 2.1.0
>
> Attachments: Hive_table_lineage.png,
> Hive_table_lineage_load_in_path.png, Ozone_bucket.png, Ozone_key.png,
> Ozone_volume.png
>
>
> Apache Ozone is the new
[jira] [Updated] (ATLAS-3879) Ozone: ozone_key entity is directly created under ozone_bucket
[
https://issues.apache.org/jira/browse/ATLAS-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3879:
Description:
The support for Apache Ozone was added in ATLAS-3836. Currently, ozone_key
entity is getting created under ozone_bucket, but there is no support to create
a hierarchy of parent ozone_key and child ozone_key.
e.g.
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
This query will create only 1 ozone_key directly under bucket "bucket1".
Created entities :
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm (ozone_key)
This Jira will improve implementation to support creating the hierarchy of
ozone_keys.
With this, above query will result into following entites
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/@cm (ozone_key) *child of ozone_bucket*
* o3fs://bucket1.volume1.ozone1/sale1/q1/@cm (ozone_key) *child of ozone_key*
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales/@cm (ozone_key) *child of
ozone_key*
This will bring Ozone model to be consistent with AWS S3 v2 and ADLS-Gen2
models.
was:
Apache ozone support addded in ATLAS-3836
Currently ozone_key entity is getting created under ozone_bucket.
No support to create ozone_key under ozone_key.
e.g.
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
This query will create only 1 ozone_key directly under bucket "bucket1".
Created entities :
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm (ozone_key)
This Jira will improve implementation to support add ozone_key under ozone_key.
With this, above query will result into following entites
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/@cm (ozone_key) *child of ozone_bucket*
* o3fs://bucket1.volume1.ozone1/sale1/q1/@cm (ozone_key) *child of ozone_key*
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales/@cm (ozone_key) *child of
ozone_key*
This will bring Ozone model to be consistent with AWS S3 v2 and ADLS-Gen2
models.
> Ozone: ozone_key entity is directly created under ozone_bucket
> --
>
> Key: ATLAS-3879
> URL: https://issues.apache.org/jira/browse/ATLAS-3879
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
>
> The support for Apache Ozone was added in ATLAS-3836. Currently, ozone_key
> entity is getting created under ozone_bucket, but there is no support to
> create a hierarchy of parent ozone_key and child ozone_key.
>
> e.g.
> {code:java}
> -> CREATE EXTERNAL TABLE sales (id int) row format delimited fields
> terminated by ' ' stored as textfile location
> 'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
> This query will create only 1 ozone_key directly under bucket "bucket1".
> Created entities :
> * o3fs://volume1@cm (ozone_key)
> * o3fs://volume1.bucket1@cm (ozone_bucket)
> * o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm (ozone_key)
>
> This Jira will improve implementation to support creating the hierarchy of
> ozone_keys.
> With this, above query will result into following entites
> * o3fs://volume1@cm (ozone_key)
> * o3fs://volume1.bucket1@cm (ozone_bucket)
> * o3fs://bucket1.volume1.ozone1/sale1/@cm (ozone_key) *child of ozone_bucket*
> * o3fs://bucket1.volume1.ozone1/sale1/q1/@cm (ozone_key) *child of ozone_key*
> * o3fs://bucket1.volume1.ozone1/sale1/q1/sales/@cm (ozone_key) *child of
> ozone_key*
>
> This will bring Ozone model to be consistent with AWS S3 v2 and ADLS-Gen2
> models.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3879) Ozone: ozone_key entity is directly created under ozone_bucket
[
https://issues.apache.org/jira/browse/ATLAS-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3879:
Description:
Apache ozone support addded in ATLAS-3836
Currently ozone_key entity is getting created under ozone_bucket.
No support to create ozone_key under ozone_key.
e.g.
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
This query will create only 1 ozone_key directly under bucket "bucket1".
Created entities :
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm (ozone_key)
This Jira will improve implementation to support add ozone_key under ozone_key.
With this, above query will result into following entites
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/@cm (ozone_key) *child of ozone_bucket*
* o3fs://bucket1.volume1.ozone1/sale1/q1/@cm (ozone_key) *child of ozone_key*
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales/@cm (ozone_key) *child of
ozone_key*
This will bring Ozone model to be consistent with AWS S3 v2 and ADLS-Gen2
models.
was:
Apache ozone support addded in ATLAS-3836
Currently ozone_key entity is getting created under ozone_bucket.
e.g.
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
This query will create only 1 ozone_key directly under bucket "bucket1".
Created entities :
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm (ozone_key)
This Jira will improve implementation to support add ozone_key under ozone_key.
With this, above query will result into following entites
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/@cm (ozone_key) *child of ozone_bucket*
* o3fs://bucket1.volume1.ozone1/sale1/q1/@cm (ozone_key) *child of ozone_key*
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales/@cm (ozone_key) *child of
ozone_key*
This will bring Ozone model to be consistent with AWS S3 v2 and ADLS-Gen2
models.
> Ozone: ozone_key entity is directly created under ozone_bucket
> --
>
> Key: ATLAS-3879
> URL: https://issues.apache.org/jira/browse/ATLAS-3879
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
>
> Apache ozone support addded in ATLAS-3836
> Currently ozone_key entity is getting created under ozone_bucket.
> No support to create ozone_key under ozone_key.
> e.g.
> {code:java}
> -> CREATE EXTERNAL TABLE sales (id int) row format delimited fields
> terminated by ' ' stored as textfile location
> 'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
> This query will create only 1 ozone_key directly under bucket "bucket1".
> Created entities :
> * o3fs://volume1@cm (ozone_key)
> * o3fs://volume1.bucket1@cm (ozone_bucket)
> * o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm (ozone_key)
>
> This Jira will improve implementation to support add ozone_key under
> ozone_key.
> With this, above query will result into following entites
> * o3fs://volume1@cm (ozone_key)
> * o3fs://volume1.bucket1@cm (ozone_bucket)
> * o3fs://bucket1.volume1.ozone1/sale1/@cm (ozone_key) *child of ozone_bucket*
> * o3fs://bucket1.volume1.ozone1/sale1/q1/@cm (ozone_key) *child of ozone_key*
> * o3fs://bucket1.volume1.ozone1/sale1/q1/sales/@cm (ozone_key) *child of
> ozone_key*
>
> This will bring Ozone model to be consistent with AWS S3 v2 and ADLS-Gen2
> models.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3879) Ozone: ozone_key entity is directly created under ozone_bucket
[
https://issues.apache.org/jira/browse/ATLAS-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3879:
Description:
Apache ozone support addded in ATLAS-3836
Currently ozone_key entity is getting created under ozone_bucket.
e.g.
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
This query will create only 1 ozone_key directly under bucket "bucket1".
Created entities :
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm (ozone_key)
This Jira will improve implementation to support add ozone_key under ozone_key.
With this, above query will result into following entites
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/@cm (ozone_key) *child of ozone_bucket*
* o3fs://bucket1.volume1.ozone1/sale1/q1/@cm (ozone_key) *child of ozone_key*
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales/@cm (ozone_key) *child of
ozone_key*
This will bring Ozone model to be consistent with AWS S3 v2 and ADLS-Gen2
models.
was:
Apache ozone support addded in ATLAS-3836
Currently ozone_key entity is getting created under ozone_bucket.
e.g.
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
This query will create only 1 ozone_key directly under bucket "bucket1".
Entities will be
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm (ozone_key)
This Jira will improve implementation to support add ozone_key under ozone_key.
With this above query will create following entites
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/@cm (ozone_key) *child of ozone_bucket*
* o3fs://bucket1.volume1.ozone1/sale1/q1/@cm (ozone_key) *child of ozone_key*
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales/@cm (ozone_key) *child of
ozone_key*
This will bring Ozone model to be consistent with AWS S3 v2 and ADLS-Gen2
models.
> Ozone: ozone_key entity is directly created under ozone_bucket
> --
>
> Key: ATLAS-3879
> URL: https://issues.apache.org/jira/browse/ATLAS-3879
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
>
> Apache ozone support addded in ATLAS-3836
> Currently ozone_key entity is getting created under ozone_bucket.
> e.g.
> {code:java}
> -> CREATE EXTERNAL TABLE sales (id int) row format delimited fields
> terminated by ' ' stored as textfile location
> 'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
> This query will create only 1 ozone_key directly under bucket "bucket1".
> Created entities :
> * o3fs://volume1@cm (ozone_key)
> * o3fs://volume1.bucket1@cm (ozone_bucket)
> * o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm (ozone_key)
>
> This Jira will improve implementation to support add ozone_key under
> ozone_key.
> With this, above query will result into following entites
> * o3fs://volume1@cm (ozone_key)
> * o3fs://volume1.bucket1@cm (ozone_bucket)
> * o3fs://bucket1.volume1.ozone1/sale1/@cm (ozone_key) *child of ozone_bucket*
> * o3fs://bucket1.volume1.ozone1/sale1/q1/@cm (ozone_key) *child of ozone_key*
> * o3fs://bucket1.volume1.ozone1/sale1/q1/sales/@cm (ozone_key) *child of
> ozone_key*
>
> This will bring Ozone model to be consistent with AWS S3 v2 and ADLS-Gen2
> models.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-3879) Ozone: ozone_key entity is directly created under ozone_bucket
Nikhil Bonte created ATLAS-3879:
---
Summary: Ozone: ozone_key entity is directly created under
ozone_bucket
Key: ATLAS-3879
URL: https://issues.apache.org/jira/browse/ATLAS-3879
Project: Atlas
Issue Type: Bug
Components: atlas-core
Affects Versions: 2.0.0
Reporter: Nikhil Bonte
Assignee: Nikhil Bonte
Apache ozone support addded in ATLAS-3836
Currently ozone_key entity is getting created under ozone_bucket.
e.g.
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
This query will create only 1 ozone_key directly under bucket "bucket1".
Entities will be
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm (ozone_key)
This Jira will improve implementation to support add ozone_key under ozone_key.
With this above query will create following entites
* o3fs://volume1@cm (ozone_key)
* o3fs://volume1.bucket1@cm (ozone_bucket)
* o3fs://bucket1.volume1.ozone1/sale1/@cm (ozone_key) *child of ozone_bucket*
* o3fs://bucket1.volume1.ozone1/sale1/q1/@cm (ozone_key) *child of ozone_key*
* o3fs://bucket1.volume1.ozone1/sale1/q1/sales/@cm (ozone_key) *child of
ozone_key*
This will bring Ozone model to be consistent with AWS S3 v2 and ADLS-Gen2
models.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3869) Upgrade httpclient from 4.5.3 to 4.5.4
[
https://issues.apache.org/jira/browse/ATLAS-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149096#comment-17149096
]
Nikhil Bonte commented on ATLAS-3869:
-
+1 for the patch.
Thanks [~nixon] .
> Upgrade httpclient from 4.5.3 to 4.5.4
> --
>
> Key: ATLAS-3869
> URL: https://issues.apache.org/jira/browse/ATLAS-3869
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Attachments: ATLAS-3869-Upgrade-httpclient-from-4.5.3-to-4.5.4.patch
>
>
> Found below exception where data was not getting added in SOLR from
> janusgraph.
>
> {noformat}
> Caused by: java.lang.ClassCastException: [B cannot be cast to java.lang.String
> at
> org.apache.http.conn.ssl.DefaultHostnameVerifier.getSubjectAltNames(DefaultHostnameVerifier.java:309)
> at
> org.apache.http.conn.ssl.DefaultHostnameVerifier.verify(DefaultHostnameVerifier.java:112)
> at
> org.apache.http.conn.ssl.DefaultHostnameVerifier.verify(DefaultHostnameVerifier.java:99)
> at
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:463)
> at
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:397)
> at
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:355)
> at
> org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
> at
> org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:359)
> at
> org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381)
> at
> org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)
> at
> org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
> at
> org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)
> at
> org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
> at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
> at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:526)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:253)
> at
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:242)
> at
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:483)
> ... 7 more
> 2020-06-29 07:31:25,893 WARN - [SIGTERM handler:] ~ Unable to close
> transaction standardjanusgraphtx[0x18d7a16a] (StandardJanusGraph:230)
> java.lang.IllegalArgumentException: The transaction has already been closed
> at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:142)
> at
> org.janusgraph.graphdb.transaction.StandardJanusGraphTx.rollback(StandardJanusGraphTx.java:1401)
> at
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsTransaction$1.doRollback(JanusGraphBlueprintsTransaction.java:190)
> at
> org.apache.tinkerpop.gremlin.structure.util.AbstractTransaction.rollback(AbstractTransaction.java:114)
> at
> org.apache.tinkerpop.gremlin.structure.Transaction$CLOSE_BEHAVIOR$2.accept(Transaction.java:182)
> at
> org.apache.tinkerpop.gremlin.structure.Transaction$CLOSE_BEHAVIOR$2.accept(Transaction.java:179)
> at
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsGraph$GraphTransaction.close(JanusGraphBlueprintsGraph.java:327)
> at
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsTransaction$1.doClose(JanusGraphBlueprintsTransaction.java:205)
> at
> org.apache.tinkerpop.gremlin.structure.util.AbstractTransaction.close(AbstractTransaction.java:139)
> at
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsTransaction.close(JanusGraphBlueprintsTransaction.java:215)
> at
> org.janusgraph.graphdb.database.StandardJanusGraph.closeInternal(StandardJanusGraph.java:226)
> at
> org.janusgraph.graphdb.database.StandardJanusGraph.access$500(StandardJanusGraph.java:91)
> at
> org.janusgraph.graphdb.database.StandardJanusGraph$ShutdownThread.start(StandardJanusGraph.java:818)
> at
> java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:102)
> at
> java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:46)
> at java.lang.Shutdown.runHooks(Shutdown.java:123)
>
[jira] [Updated] (ATLAS-3871) Add unit tests to path extractor utility for s3, s3 v2, adls path entities
[ https://issues.apache.org/jira/browse/ATLAS-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3871: Description: AtlasPathExtractorUtilTest added in ATLAS-3836 which covers unit tests for ozone & hdfs path entites. This Jira will improve AtlasPathExtractorUtilTest.java to cover s3, s3v2 & adls path entities. Would add more tests for ozone as well. was: AtlasPathExtractorUtilTest added in ATLAS-3836 which covers ozone & hdfs path entites unit tests. This Jira will improve AtlasPathExtractorUtilTest.java to cover s3, s3v2 & adls path entities. Also will add more tests for ozone path. > Add unit tests to path extractor utility for s3, s3 v2, adls path entities > -- > > Key: ATLAS-3871 > URL: https://issues.apache.org/jira/browse/ATLAS-3871 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > > AtlasPathExtractorUtilTest added in ATLAS-3836 which covers unit tests for > ozone & hdfs path entites. > > This Jira will improve AtlasPathExtractorUtilTest.java to cover s3, s3v2 & > adls path entities. > Would add more tests for ozone as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3871) Add unit tests to path extractor utility for s3, s3 v2, adls path entities
[ https://issues.apache.org/jira/browse/ATLAS-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3871: Description: AtlasPathExtractorUtilTest added in ATLAS-3836 which covers ozone & hdfs path entites unit tests. This Jira will improve AtlasPathExtractorUtilTest.java to cover s3, s3v2 & adls path entities. Also will add more tests for ozone path. was: AtlasPathExtractorUtilTest is added in ATLAS-3836 which covers ozone & hdfs path entites unit tests. This Jira will improve AtlasPathExtractorUtilTest.java to cover s3, s3v2 & adls path entities. Also will add more tests for ozone path. > Add unit tests to path extractor utility for s3, s3 v2, adls path entities > -- > > Key: ATLAS-3871 > URL: https://issues.apache.org/jira/browse/ATLAS-3871 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > > AtlasPathExtractorUtilTest added in ATLAS-3836 which covers ozone & hdfs path > entites unit tests. > This Jira will improve AtlasPathExtractorUtilTest.java to cover s3, s3v2 & > adls path entities. > Also will add more tests for ozone path. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3871) Add unit tests to path extractor utility for s3, s3 v2, adls path entities
[ https://issues.apache.org/jira/browse/ATLAS-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3871: Summary: Add unit tests to path extractor utility for s3, s3 v2, adls path entities (was: Add unit tests for s3, s3 v2, adls path entities in path extractor utility) > Add unit tests to path extractor utility for s3, s3 v2, adls path entities > -- > > Key: ATLAS-3871 > URL: https://issues.apache.org/jira/browse/ATLAS-3871 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > > AtlasPathExtractorUtilTest is added in ATLAS-3836 which covers ozone & hdfs > path entites unit tests. > This Jira will improve AtlasPathExtractorUtilTest.java to cover s3, s3v2 & > adls path entities. > Also will add more tests for ozone path. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3871) Add unit tests for s3, s3 v2, adls path entities in path extractor utility
Nikhil Bonte created ATLAS-3871: --- Summary: Add unit tests for s3, s3 v2, adls path entities in path extractor utility Key: ATLAS-3871 URL: https://issues.apache.org/jira/browse/ATLAS-3871 Project: Atlas Issue Type: Improvement Components: atlas-core Affects Versions: 2.0.0 Reporter: Nikhil Bonte Assignee: Nikhil Bonte AtlasPathExtractorUtilTest is added in ATLAS-3836 which covers ozone & hdfs path entites unit tests. This Jira will improve AtlasPathExtractorUtilTest.java to cover s3, s3v2 & adls path entities. Also will add more tests for ozone path. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3836) Add Apache Ozone support in hive hook
[
https://issues.apache.org/jira/browse/ATLAS-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3836:
Description:
Apache Ozone is the new object store for Hadoop -
[https://hadoop.apache.org/ozone/]
Apache Atlas needs to add entity types to support creation of Ozone entities.
Hive hook should also be updated to create lineage between ozone entities and
hive tables (for EXTERNAL TABLE)
+*Approach :*+
# Refactored BaseHiveEvent.getPathEntity() -> moved to
AtlasPathExtractorUtil.java
# Created PathExtractorContext.java to wrap most arguments.
# AtlasPathExtractorUtil.getPathEntity() -> accept Path, PathExtractorContext
-> return AtlasEntityWithExtInfo
# Added specific condition in AtlasPathExtractorUtil.getPathEntity() to handle
Ozone path
-> path starts with "ofs://" or "o3fs://"
# Added UT around AtlasPathExtractorUtil.getPathEntity() ->
AtlasPathExtractorUtilTest.java
+*Examples :*+
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
|| ||Name||Qualified Name||
|ozone_key|/sale1/q1/sales|o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks (id int) row format delimited fields terminated
by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket1.volume1.ozone1/stocks.txt' into table
stocks;
{code}
|| ||Name||Qualified Name||
|ozone_key|/stocks.txt|o3fs://bucket1.volume1.ozone1/stocks.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks_q1 (id int) row format delimited fields
terminated by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket15.volume15.ozone1/quarter1/stocks_q1.txt'
into table stocks_q1;{code}
|| ||Name||Qualified Name||
|ozone_key|/quarter1/stocks_q1.txt|o3fs://bucket1.volume1.ozone1/quarter1/stocks_q1.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
was:
Apache Ozone is the new object store for Hadoop -
[https://hadoop.apache.org/ozone/]
Apache Atlas needs to add entity types to support creation of Ozone entities.
Hive hook should also be updated to create lineage between ozone entities and
hive tables (for EXTERNAL TABLE)
+*Approach :*+
# Refactored BaseHiveEvent.getPathEntity() -> moved to
AtlasPathExtractorUtil.java
# Created PathExtractorContext.java to wrap most arguments.
# AtlasPathExtractorUtil.getPathEntity() -> accept Path, PathExtractorContext
-> return AtlasEntityWithExtInfo
# Added specific condition in AtlasPathExtractorUtil.getPathEntity() to handle
Ozone path
-> path starts with "ofs://" or "o3fs://"
# Added UT around AtlasPathExtractorUtil.getPathEntity() ->
AtlasPathExtractorUtilTest.java
+*Examples :*+
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
|| ||Name||Qualified Name||
|ozone_key|/sale1/q1/sales|o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks (id int) row format delimited fields terminated
by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket1.volume1.ozone1/stocks.txt' into table
stocks;
{code}
|| ||Name||Qualified Name||
|ozone_key|/stocks.txt|o3fs://bucket1.volume1.ozone1/stocks.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks_q1 (id int) row format delimited fields
terminated by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket15.volume15.ozone1/quarter1/stocks_q1.txt'
into table stocks_q1;{code}
|| ||Name||Qualified Name||
|ozone_key|/quarter1/stocks_q1.txt|o3fs://bucket1.volume1.ozone1/quarter1/stocks_q1.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
> Add Apache Ozone support in hive hook
> -
>
> Key: ATLAS-3836
> URL: https://issues.apache.org/jira/browse/ATLAS-3836
> Project: Atlas
> Issue Type: New Feature
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Nikhil Bonte
>Priority: Major
> Labels: hive-hooks, ozone
> Fix For: 2.1.0
>
> Attachments: Hive_table_lineage.png,
> Hive_table_lineage_load_in_path.png, Ozone_bucket.png, Ozone_key.png,
> Ozone_volume.png
>
>
> Apache Ozone is the new object store for Hadoop -
>
[jira] [Updated] (ATLAS-3836) Add Apache Ozone support in hive hook
[
https://issues.apache.org/jira/browse/ATLAS-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3836:
Description:
Apache Ozone is the new object store for Hadoop -
[https://hadoop.apache.org/ozone/]
Apache Atlas needs to add entity types to support creation of Ozone entities.
Hive hook should also be updated to create lineage between ozone entities and
hive tables (for EXTERNAL TABLE)
+*Approach :*+
# Refactored BaseHiveEvent.getPathEntity() -> moved to
AtlasPathExtractorUtil.java
# Created PathExtractorContext.java to wrap most arguments.
# AtlasPathExtractorUtil.getPathEntity() -> accept Path, PathExtractorContext
-> return AtlasEntityWithExtInfo
# Added specific condition in AtlasPathExtractorUtil.getPathEntity() to handle
Ozone path
-> path starts with "ofs://" or "o3fs://"
# Added UT around AtlasPathExtractorUtil.getPathEntity() ->
AtlasPathExtractorUtilTest.java
+*Examples :*+
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
|| ||Name||Qualified Name||
|ozone_key|/sale1/q1/sales|o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks (id int) row format delimited fields terminated
by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket1.volume1.ozone1/stocks.txt' into table
stocks;
{code}
|| ||Name||Qualified Name||
|ozone_key|/stocks.txt|o3fs://bucket1.volume1.ozone1/stocks.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks_q1 (id int) row format delimited fields
terminated by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket1.volume1.ozone1/quarter1/stocks_q1.txt' into
table stocks_q1;{code}
|| ||Name||Qualified Name||
|ozone_key|/quarter1/stocks_q1.txt|o3fs://bucket1.volume1.ozone1/quarter1/stocks_q1.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
was:
Apache Ozone is the new object store for Hadoop -
[https://hadoop.apache.org/ozone/]
Apache Atlas needs to add entity types to support creation of Ozone entities.
Hive hook should also be updated to create lineage between ozone entities and
hive tables (for EXTERNAL TABLE)
+*Approach :*+
# Refactored BaseHiveEvent.getPathEntity() -> moved to
AtlasPathExtractorUtil.java
# Created PathExtractorContext.java to wrap most arguments.
# AtlasPathExtractorUtil.getPathEntity() -> accept Path, PathExtractorContext
-> return AtlasEntityWithExtInfo
# Added specific condition in AtlasPathExtractorUtil.getPathEntity() to handle
Ozone path
-> path starts with "ofs://" or "o3fs://"
# Added UT around AtlasPathExtractorUtil.getPathEntity() ->
AtlasPathExtractorUtilTest.java
+*Examples :*+
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
|| ||Name||Qualified Name||
|ozone_key|/sale1/q1/sales|o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks (id int) row format delimited fields terminated
by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket1.volume1.ozone1/stocks.txt' into table
stocks;
{code}
|| ||Name||Qualified Name||
|ozone_key|/stocks.txt|o3fs://bucket1.volume1.ozone1/stocks.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks_q1 (id int) row format delimited fields
terminated by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket15.volume15.ozone1/quarter1/stocks_q1.txt'
into table stocks_q1;{code}
|| ||Name||Qualified Name||
|ozone_key|/quarter1/stocks_q1.txt|o3fs://bucket1.volume1.ozone1/quarter1/stocks_q1.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
> Add Apache Ozone support in hive hook
> -
>
> Key: ATLAS-3836
> URL: https://issues.apache.org/jira/browse/ATLAS-3836
> Project: Atlas
> Issue Type: New Feature
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Nikhil Bonte
>Priority: Major
> Labels: hive-hooks, ozone
> Fix For: 2.1.0
>
> Attachments: Hive_table_lineage.png,
> Hive_table_lineage_load_in_path.png, Ozone_bucket.png, Ozone_key.png,
> Ozone_volume.png
>
>
> Apache Ozone is the new object store for Hadoop -
>
[jira] [Updated] (ATLAS-3836) Add Apache Ozone support in hive hook
[
https://issues.apache.org/jira/browse/ATLAS-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3836:
Description:
Apache Ozone is the new object store for Hadoop -
[https://hadoop.apache.org/ozone/]
Apache Atlas needs to add entity types to support creation of Ozone entities.
Hive hook should also be updated to create lineage between ozone entities and
hive tables (for EXTERNAL TABLE)
+*Approach :*+
# Refactored BaseHiveEvent.getPathEntity() -> moved to
AtlasPathExtractorUtil.java
# Created PathExtractorContext.java to wrap most arguments.
# AtlasPathExtractorUtil.getPathEntity() -> accept Path, PathExtractorContext
-> return AtlasEntityWithExtInfo
# Added specific condition in AtlasPathExtractorUtil.getPathEntity() to handle
Ozone path
-> path starts with "ofs://" or "o3fs://"
# Added UT around AtlasPathExtractorUtil.getPathEntity() ->
AtlasPathExtractorUtilTest.java
+*Examples :*+
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
|| ||Name||Qualified Name||
|ozone_key|/sale1/q1/sales|o3fs://bucket1.volume1.ozone1/sale1/q1/sales@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks (id int) row format delimited fields terminated
by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket1.volume1.ozone1/stocks.txt' into table
stocks;
{code}
|| ||Name||Qualified Name||
|ozone_key|/stocks.txt|o3fs://bucket1.volume1.ozone1/stocks.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks_q1 (id int) row format delimited fields
terminated by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket15.volume15.ozone1/quarter1/stocks_q1.txt'
into table stocks_q1;{code}
|| ||Name||Qualified Name||
|ozone_key|/quarter1/stocks_q1.txt|o3fs://bucket1.volume1.ozone1/quarter1/stocks_q1.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
was:
Apache Ozone is the new object store for Hadoop -
[https://hadoop.apache.org/ozone/]
Apache Atlas needs to add entity types to support creation of Ozone entities.
Hive hook should also be updated to create lineage between ozone entities and
hive tables (for EXTERNAL TABLE)
+*Approach :*+
# Refactored BaseHiveEvent.getPathEntity() -> moved to
AtlasPathExtractorUtil.java
# Created PathExtractorContext.java to wrap most arguments.
# AtlasPathExtractorUtil.getPathEntity() -> accept Path, PathExtractorContext
-> return AtlasEntityWithExtInfo
# Added specific condition in AtlasPathExtractorUtil.getPathEntity() to handle
Ozone path
-> path starts with "ofs://" or "o3fs://"
# Added UT around AtlasPathExtractorUtil.getPathEntity() ->
AtlasPathExtractorUtilTest.java
+*Examples :*+
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
|| ||Name||Qualified Name||
|ozone_key|/sale1/q1/sales2|o3fs://bucket1.volume1.ozone1/sale1/q1/sales2@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks (id int) row format delimited fields terminated
by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket1.volume1.ozone1/stocks.txt' into table
stocks;
{code}
|| ||Name||Qualified Name||
|ozone_key|/stocks.txt|o3fs://bucket1.volume1.ozone1/stocks.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks_q1 (id int) row format delimited fields
terminated by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket15.volume15.ozone1/quarter1/stocks_q1.txt'
into table stocks_q1;{code}
|| ||Name||Qualified Name||
|ozone_key|/quarter1/stocks_q1.txt|o3fs://bucket1.volume1.ozone1/quarter1/stocks_q1.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
> Add Apache Ozone support in hive hook
> -
>
> Key: ATLAS-3836
> URL: https://issues.apache.org/jira/browse/ATLAS-3836
> Project: Atlas
> Issue Type: New Feature
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Nikhil Bonte
>Priority: Major
> Labels: hive-hooks, ozone
> Fix For: 2.1.0
>
> Attachments: Hive_table_lineage.png,
> Hive_table_lineage_load_in_path.png, Ozone_bucket.png, Ozone_key.png,
> Ozone_volume.png
>
>
> Apache Ozone is the new object store for Hadoop -
>
[jira] [Updated] (ATLAS-3836) Add Apache Ozone support in hive hook
[
https://issues.apache.org/jira/browse/ATLAS-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3836:
Description:
Apache Ozone is the new object store for Hadoop -
[https://hadoop.apache.org/ozone/]
Apache Atlas needs to add entity types to support creation of Ozone entities.
Hive hook should also be updated to create lineage between ozone entities and
hive tables (for EXTERNAL TABLE)
+*Approach :*+
# Refactored BaseHiveEvent.getPathEntity() -> moved to
AtlasPathExtractorUtil.java
# Created PathExtractorContext.java to wrap most arguments.
# AtlasPathExtractorUtil.getPathEntity() -> accept Path, PathExtractorContext
-> return AtlasEntityWithExtInfo
# Added specific condition in AtlasPathExtractorUtil.getPathEntity() to handle
Ozone path
-> path starts with "ofs://" or "o3fs://"
# Added UT around AtlasPathExtractorUtil.getPathEntity() ->
AtlasPathExtractorUtilTest.java
+*Examples :*+
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
|| ||Name||Qualified Name||
|ozone_key|/sale1/q1/sales2|o3fs://bucket1.volume1.ozone1/sale1/q1/sales2@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks (id int) row format delimited fields terminated
by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket1.volume1.ozone1/stocks.txt' into table
stocks;
{code}
|| ||Name||Qualified Name||
|ozone_key|/stocks.txt|o3fs://bucket1.volume1.ozone1/stocks.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks_q1 (id int) row format delimited fields
terminated by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket15.volume15.ozone1/quarter1/stocks_q1.txt'
into table stocks_q1;{code}
|| ||Name||Qualified Name||
|ozone_key|/quarter1/stocks_q1.txt|o3fs://bucket1.volume1.ozone1/quarter1/stocks_q1.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
was:
Apache Ozone is the new object store for Hadoop -
[https://hadoop.apache.org/ozone/]
Apache Atlas needs to add entity types to support creation of Ozone entities.
Hive hook should also be updated to create lineage between ozone entities and
hive tables (for EXTERNAL TABLE)
+*Approach :*+
# Refactored BaseHiveEvent.getPathEntity() -> moved to
AtlasPathExtractorUtil.java
# Created PathExtractorContext.java to wrap most arguments.
# AtlasPathExtractorUtil.getPathEntity() -> accept Path, PathExtractorContext
-> return AtlasEntityWithExtInfo
# Added specific condition in AtlasPathExtractorUtil.getPathEntity() to handle
Ozone path
-> path starts with "ofs://" or "o3fs://"
# Added UT around AtlasPathExtractorUtil.getPathEntity() ->
AtlasPathExtractorUtilTest.java
> Add Apache Ozone support in hive hook
> -
>
> Key: ATLAS-3836
> URL: https://issues.apache.org/jira/browse/ATLAS-3836
> Project: Atlas
> Issue Type: New Feature
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Nikhil Bonte
>Priority: Major
> Labels: hive-hooks, ozone
> Fix For: 2.1.0
>
> Attachments: Hive_table_lineage.png,
> Hive_table_lineage_load_in_path.png, Ozone_bucket.png, Ozone_key.png,
> Ozone_volume.png
>
>
> Apache Ozone is the new object store for Hadoop -
> [https://hadoop.apache.org/ozone/]
> Apache Atlas needs to add entity types to support creation of Ozone entities.
> Hive hook should also be updated to create lineage between ozone entities and
> hive tables (for EXTERNAL TABLE)
> +*Approach :*+
> # Refactored BaseHiveEvent.getPathEntity() -> moved to
> AtlasPathExtractorUtil.java
> # Created PathExtractorContext.java to wrap most arguments.
> # AtlasPathExtractorUtil.getPathEntity() -> accept Path,
> PathExtractorContext -> return AtlasEntityWithExtInfo
> # Added specific condition in AtlasPathExtractorUtil.getPathEntity() to
> handle Ozone path
> -> path starts with "ofs://" or "o3fs://"
> # Added UT around AtlasPathExtractorUtil.getPathEntity() ->
> AtlasPathExtractorUtilTest.java
>
> +*Examples :*+
> {code:java}
> -> CREATE EXTERNAL TABLE sales (id int) row format delimited fields
> terminated by ' ' stored as textfile location
> 'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
>
>
> || ||Name||Qualified Name||
> |ozone_key|/sale1/q1/sales2|o3fs://bucket1.volume1.ozone1/sale1/q1/sales2@cm|
> |ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
> |ozone_volume|volume1|o3fs://volume1@cm|
>
>
> {code:java}
> -> create EXTERNAL table stocks (id int) row
[jira] [Updated] (ATLAS-3836) Add Apache Ozone support in hive hook
[
https://issues.apache.org/jira/browse/ATLAS-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3836:
Description:
Apache Ozone is the new object store for Hadoop -
[https://hadoop.apache.org/ozone/]
Apache Atlas needs to add entity types to support creation of Ozone entities.
Hive hook should also be updated to create lineage between ozone entities and
hive tables (for EXTERNAL TABLE)
+*Approach :*+
# Refactored BaseHiveEvent.getPathEntity() -> moved to
AtlasPathExtractorUtil.java
# Created PathExtractorContext.java to wrap most arguments.
# AtlasPathExtractorUtil.getPathEntity() -> accept Path, PathExtractorContext
-> return AtlasEntityWithExtInfo
# Added specific condition in AtlasPathExtractorUtil.getPathEntity() to handle
Ozone path
-> path starts with "ofs://" or "o3fs://"
# Added UT around AtlasPathExtractorUtil.getPathEntity() ->
AtlasPathExtractorUtilTest.java
+*Examples :*+
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
|| ||Name||Qualified Name||
|ozone_key|/sale1/q1/sales2|o3fs://bucket1.volume1.ozone1/sale1/q1/sales2@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks (id int) row format delimited fields terminated
by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket1.volume1.ozone1/stocks.txt' into table
stocks;
{code}
|| ||Name||Qualified Name||
|ozone_key|/stocks.txt|o3fs://bucket1.volume1.ozone1/stocks.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks_q1 (id int) row format delimited fields
terminated by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket15.volume15.ozone1/quarter1/stocks_q1.txt'
into table stocks_q1;{code}
|| ||Name||Qualified Name||
|ozone_key|/quarter1/stocks_q1.txt|o3fs://bucket1.volume1.ozone1/quarter1/stocks_q1.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
was:
Apache Ozone is the new object store for Hadoop -
[https://hadoop.apache.org/ozone/]
Apache Atlas needs to add entity types to support creation of Ozone entities.
Hive hook should also be updated to create lineage between ozone entities and
hive tables (for EXTERNAL TABLE)
+*Approach :*+
# Refactored BaseHiveEvent.getPathEntity() -> moved to
AtlasPathExtractorUtil.java
# Created PathExtractorContext.java to wrap most arguments.
# AtlasPathExtractorUtil.getPathEntity() -> accept Path, PathExtractorContext
-> return AtlasEntityWithExtInfo
# Added specific condition in AtlasPathExtractorUtil.getPathEntity() to handle
Ozone path
-> path starts with "ofs://" or "o3fs://"
# Added UT around AtlasPathExtractorUtil.getPathEntity() ->
AtlasPathExtractorUtilTest.java
+*Examples :*+
{code:java}
-> CREATE EXTERNAL TABLE sales (id int) row format delimited fields terminated
by ' ' stored as textfile location
'o3fs://bucket1.volume1.ozone1/sale1/q1/sales';{code}
|| ||Name||Qualified Name||
|ozone_key|/sale1/q1/sales2|o3fs://bucket1.volume1.ozone1/sale1/q1/sales2@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks (id int) row format delimited fields terminated
by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket1.volume1.ozone1/stocks.txt' into table
stocks;
{code}
|| ||Name||Qualified Name||
|ozone_key|/stocks.txt|o3fs://bucket1.volume1.ozone1/stocks.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
{code:java}
-> create EXTERNAL table stocks_q1 (id int) row format delimited fields
terminated by ' ' stored as textfile;
-> load data inpath 'o3fs://bucket15.volume15.ozone1/quarter1/stocks_q1.txt'
into table stocks_q1;{code}
|| ||Name||Qualified Name||
|ozone_key|/quarter1/stocks_q1.txt|o3fs://bucket1.volume1.ozone1/quarter1/stocks_q1.txt@cm|
|ozone_bucket|bucket1|o3fs://volume1.bucket1@cm|
|ozone_volume|volume1|o3fs://volume1@cm|
> Add Apache Ozone support in hive hook
> -
>
> Key: ATLAS-3836
> URL: https://issues.apache.org/jira/browse/ATLAS-3836
> Project: Atlas
> Issue Type: New Feature
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Sarath Subramanian
>Assignee: Nikhil Bonte
>Priority: Major
> Labels: hive-hooks, ozone
> Fix For: 2.1.0
>
> Attachments: Hive_table_lineage.png,
> Hive_table_lineage_load_in_path.png, Ozone_bucket.png, Ozone_key.png,
> Ozone_volume.png
>
>
> Apache Ozone is the new object store for Hadoop -
>
[jira] [Updated] (ATLAS-3836) Add Apache Ozone support in hive hook
[ https://issues.apache.org/jira/browse/ATLAS-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3836: Description: Apache Ozone is the new object store for Hadoop - [https://hadoop.apache.org/ozone/] Apache Atlas needs to add entity types to support creation of Ozone entities. Hive hook should also be updated to create lineage between ozone entities and hive tables (for EXTERNAL TABLE) +*Approach :*+ # Refactored BaseHiveEvent.getPathEntity() -> moved to AtlasPathExtractorUtil.java # Created PathExtractorContext.java to wrap most arguments. # AtlasPathExtractorUtil.getPathEntity() -> accept Path, PathExtractorContext -> return AtlasEntityWithExtInfo # Added specific condition in AtlasPathExtractorUtil.getPathEntity() to handle Ozone path -> path starts with "ofs://" or "o3fs://" # Added UT around AtlasPathExtractorUtil.getPathEntity() -> AtlasPathExtractorUtilTest.java was: Apache Ozone is the new object store for Hadoop - [https://hadoop.apache.org/ozone/] Apache Atlas needs to add entity types to support creation of Ozone entities. Hive hook should also be updated to create lineage between ozone entities and hive tables (for EXTERNAL TABLE) > Add Apache Ozone support in hive hook > - > > Key: ATLAS-3836 > URL: https://issues.apache.org/jira/browse/ATLAS-3836 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Sarath Subramanian >Assignee: Nikhil Bonte >Priority: Major > Labels: hive-hooks, ozone > Fix For: 2.1.0 > > Attachments: Hive_table_lineage.png, > Hive_table_lineage_load_in_path.png, Ozone_bucket.png, Ozone_key.png, > Ozone_volume.png > > > Apache Ozone is the new object store for Hadoop - > [https://hadoop.apache.org/ozone/] > Apache Atlas needs to add entity types to support creation of Ozone entities. > Hive hook should also be updated to create lineage between ozone entities and > hive tables (for EXTERNAL TABLE) > +*Approach :*+ > # Refactored BaseHiveEvent.getPathEntity() -> moved to > AtlasPathExtractorUtil.java > # Created PathExtractorContext.java to wrap most arguments. > # AtlasPathExtractorUtil.getPathEntity() -> accept Path, > PathExtractorContext -> return AtlasEntityWithExtInfo > # Added specific condition in AtlasPathExtractorUtil.getPathEntity() to > handle Ozone path > -> path starts with "ofs://" or "o3fs://" > # Added UT around AtlasPathExtractorUtil.getPathEntity() -> > AtlasPathExtractorUtilTest.java > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3856) Create new entity typeDefs for Apache Ozone
[ https://issues.apache.org/jira/browse/ATLAS-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3856: Description: Add following ozone typeDefs to Atlas models * entityDefs: ** ozone_volume ** ozone_bucket ** ozone_key * enumDefs: ** ozone_storage_type ** ozone_replication_type * structDefs: ** ozone_key_location * relationshipDefs: ** ozone_volume_buckets ** ozone_bucket_keys was: Add following ozone typeDefs to Atlas models * entityDefs: ** ozone_volume ** ozone_bucket ** ozone_key * enumDefs: ** ozone_storage_type ** ozone_replication_type * structDefs: ** ozone_key_location * relationshipDefs: ** ozone_volume_buckets ** ozone_bucket_keys > Create new entity typeDefs for Apache Ozone > --- > > Key: ATLAS-3856 > URL: https://issues.apache.org/jira/browse/ATLAS-3856 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > Fix For: 2.1.0 > > Attachments: > ATLAS-3856-Create-new-entity-typeDefs-for-Apache-Ozone-v0.patch > > > Add following ozone typeDefs to Atlas models > * entityDefs: > ** ozone_volume > ** ozone_bucket > ** ozone_key > * enumDefs: > ** ozone_storage_type > ** ozone_replication_type > * structDefs: > ** ozone_key_location > * relationshipDefs: > ** ozone_volume_buckets > ** ozone_bucket_keys -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3856) Create new entity typeDefs for Apache Ozone
[ https://issues.apache.org/jira/browse/ATLAS-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3856: Description: Add following ozone typeDefs to Atlas models * entityDefs: ** ozone_volume ** ozone_bucket ** ozone_key * enumDefs: ** ozone_storage_type ** ozone_replication_type * structDefs: ** ozone_key_location * relationshipDefs: ** ozone_volume_buckets ** ozone_bucket_keys was: Add following ozone typeDefs to Atlas models * Ozone volume * Ozone bucket * Ozone key > Create new entity typeDefs for Apache Ozone > --- > > Key: ATLAS-3856 > URL: https://issues.apache.org/jira/browse/ATLAS-3856 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > Fix For: 2.1.0 > > Attachments: > ATLAS-3856-Create-new-entity-typeDefs-for-Apache-Ozone-v0.patch > > > Add following ozone typeDefs to Atlas models > * entityDefs: > ** ozone_volume > ** ozone_bucket > ** ozone_key > * enumDefs: > ** ozone_storage_type > ** ozone_replication_type > * structDefs: > ** ozone_key_location > * relationshipDefs: > ** ozone_volume_buckets > ** ozone_bucket_keys -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3836) Add Apache Ozone support in hive hook
[ https://issues.apache.org/jira/browse/ATLAS-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3836: Attachment: Ozone_key.png Ozone_bucket.png Ozone_volume.png Hive_table_lineage.png Hive_table_lineage_load_in_path.png > Add Apache Ozone support in hive hook > - > > Key: ATLAS-3836 > URL: https://issues.apache.org/jira/browse/ATLAS-3836 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Sarath Subramanian >Assignee: Nikhil Bonte >Priority: Major > Fix For: 2.1.0 > > Attachments: Hive_table_lineage.png, > Hive_table_lineage_load_in_path.png, Ozone_bucket.png, Ozone_key.png, > Ozone_volume.png > > > Apache Ozone is the new object store for Hadoop - > [https://hadoop.apache.org/ozone/] > Apache Atlas needs to add entity types to support creation of Ozone entities. > Hive hook should also be updated to create lineage between ozone entities and > hive tables (for EXTERNAL TABLE) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-3852) Entity Bulk Create with unique reference
[ https://issues.apache.org/jira/browse/ATLAS-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144830#comment-17144830 ] Nikhil Bonte edited comment on ATLAS-3852 at 6/25/20, 10:51 AM: [~vasanthkumar] - Currently Atlas does support creating entities which are referenced in same bulk request using negative guid approach. [^BulkPostCreate.json] I have attached sample payload which will create new a hive_db, a hive_table & a hive_column in single request. Hope this would help. was (Author: nikhilbonte): [~vasanthkumar] - Currently Atlas does support creating entities with referenced in same bulk request using negative guid approach. [^BulkPostCreate.json] I have attached sample payload which will create new a hive_db, a hive_table & a hive_column in single request. Hope this would help. > Entity Bulk Create with unique reference > > > Key: ATLAS-3852 > URL: https://issues.apache.org/jira/browse/ATLAS-3852 > Project: Atlas > Issue Type: Improvement >Reporter: Vasanth kumar RJ >Priority: Major > Fix For: 2.1.0 > > Attachments: ATLAS-3852.patch, BulkPostCreate.json > > > Entities created in bulk and unique referenced in same request. Bulk create > DB, Table and Column referenced in a request itself. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3852) Entity Bulk Create with unique reference
[ https://issues.apache.org/jira/browse/ATLAS-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144830#comment-17144830 ] Nikhil Bonte commented on ATLAS-3852: - [~vasanthkumar] - Currently Atlas does support creating entities with referenced in same bulk request using negative guid approach. [^BulkPostCreate.json] I have attached sample payload which will create new a hive_db, a hive_table & a hive_column in single request. Hope this would help. > Entity Bulk Create with unique reference > > > Key: ATLAS-3852 > URL: https://issues.apache.org/jira/browse/ATLAS-3852 > Project: Atlas > Issue Type: Improvement >Reporter: Vasanth kumar RJ >Priority: Major > Fix For: 2.1.0 > > Attachments: ATLAS-3852.patch, BulkPostCreate.json > > > Entities created in bulk and unique referenced in same request. Bulk create > DB, Table and Column referenced in a request itself. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3852) Entity Bulk Create with unique reference
[ https://issues.apache.org/jira/browse/ATLAS-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3852: Attachment: BulkPostCreate.json > Entity Bulk Create with unique reference > > > Key: ATLAS-3852 > URL: https://issues.apache.org/jira/browse/ATLAS-3852 > Project: Atlas > Issue Type: Improvement >Reporter: Vasanth kumar RJ >Priority: Major > Fix For: 2.1.0 > > Attachments: ATLAS-3852.patch, BulkPostCreate.json > > > Entities created in bulk and unique referenced in same request. Bulk create > DB, Table and Column referenced in a request itself. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3856) Create new entity typeDefs for Apache Ozone
[ https://issues.apache.org/jira/browse/ATLAS-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3856: Attachment: ATLAS-3856-Create-new-entity-typeDefs-for-Apache-Ozone-v0.patch > Create new entity typeDefs for Apache Ozone > --- > > Key: ATLAS-3856 > URL: https://issues.apache.org/jira/browse/ATLAS-3856 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > Attachments: > ATLAS-3856-Create-new-entity-typeDefs-for-Apache-Ozone-v0.patch > > > Add following ozone typeDefs to Atlas models > * Ozone volume > * Ozone bucket > * Ozone key -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3856) Create new entity typeDefs for Apache Ozone
[ https://issues.apache.org/jira/browse/ATLAS-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3856: Summary: Create new entity typeDefs for Apache Ozone (was: Create new entity types for Apache Ozone) > Create new entity typeDefs for Apache Ozone > --- > > Key: ATLAS-3856 > URL: https://issues.apache.org/jira/browse/ATLAS-3856 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > > Add following ozone typeDefs to Atlas models > * Ozone volume > * Ozone bucket > * Ozone key -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3836) Add Apache Ozone support in hive hook
[ https://issues.apache.org/jira/browse/ATLAS-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3836: Summary: Add Apache Ozone support in hive hook (was: Create new entity types for Apache Ozone and update hive hook to handle reference to Ozone path) > Add Apache Ozone support in hive hook > - > > Key: ATLAS-3836 > URL: https://issues.apache.org/jira/browse/ATLAS-3836 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Sarath Subramanian >Assignee: Nikhil Bonte >Priority: Major > Fix For: 2.1.0 > > > Apache Ozone is the new object store for Hadoop - > [https://hadoop.apache.org/ozone/] > Apache Atlas needs to add entity types to support creation of Ozone entities. > Hive hook should also be updated to create lineage between ozone entities and > hive tables (for EXTERNAL TABLE) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3856) Create new entity types for Apache Ozone
Nikhil Bonte created ATLAS-3856: --- Summary: Create new entity types for Apache Ozone Key: ATLAS-3856 URL: https://issues.apache.org/jira/browse/ATLAS-3856 Project: Atlas Issue Type: New Feature Components: atlas-core Affects Versions: 2.0.0 Reporter: Nikhil Bonte Assignee: Nikhil Bonte Add following ozone typeDefs to Atlas models * Ozone volume * Ozone bucket * Ozone key -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3849) UI: Create icons for new entity types for Apache ozone
[ https://issues.apache.org/jira/browse/ATLAS-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3849: Description: New typeDefs: * ozone_volume * ozone_bucket * ozone_key > UI: Create icons for new entity types for Apache ozone > -- > > Key: ATLAS-3849 > URL: https://issues.apache.org/jira/browse/ATLAS-3849 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Affects Versions: 2.0.0 >Reporter: Nikhil Bonte >Assignee: Keval Bhatt >Priority: Major > > New typeDefs: > * ozone_volume > * ozone_bucket > * ozone_key -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3849) UI: Create icons for new entity types for Apache ozone
[ https://issues.apache.org/jira/browse/ATLAS-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3849: Affects Version/s: (was: 2.1.0) 2.0.0 > UI: Create icons for new entity types for Apache ozone > -- > > Key: ATLAS-3849 > URL: https://issues.apache.org/jira/browse/ATLAS-3849 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Affects Versions: 2.0.0 >Reporter: Nikhil Bonte >Assignee: Keval Bhatt >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3849) UI: Create icons for new entity types for Apache ozone
Nikhil Bonte created ATLAS-3849: --- Summary: UI: Create icons for new entity types for Apache ozone Key: ATLAS-3849 URL: https://issues.apache.org/jira/browse/ATLAS-3849 Project: Atlas Issue Type: New Feature Components: atlas-webui Affects Versions: 2.1.0 Reporter: Nikhil Bonte Assignee: Keval Bhatt -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3836) Create new entity types for Apache Ozone and update hive hook to handle reference to Ozone path
[ https://issues.apache.org/jira/browse/ATLAS-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte reassigned ATLAS-3836: --- Assignee: Nikhil Bonte (was: Sarath Subramanian) > Create new entity types for Apache Ozone and update hive hook to handle > reference to Ozone path > --- > > Key: ATLAS-3836 > URL: https://issues.apache.org/jira/browse/ATLAS-3836 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Sarath Subramanian >Assignee: Nikhil Bonte >Priority: Major > Fix For: 2.1.0 > > > Apache Ozone is the new object store for Hadoop - > [https://hadoop.apache.org/ozone/] > Apache Atlas needs to add entity types to support creation of Ozone entities. > Hive hook should also be updated to create lineage between ozone entities and > hive tables (for EXTERNAL TABLE) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3831) UI: Add entity icon for spark
[ https://issues.apache.org/jira/browse/ATLAS-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130523#comment-17130523 ] Nikhil Bonte commented on ATLAS-3831: - +1 for the patch, thanks [~kevalbhatt] for the patch. > UI: Add entity icon for spark > - > > Key: ATLAS-3831 > URL: https://issues.apache.org/jira/browse/ATLAS-3831 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3831.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3769) UI: Changing page limit in Admin audits resets any filters applied on that page
[ https://issues.apache.org/jira/browse/ATLAS-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130522#comment-17130522 ] Nikhil Bonte commented on ATLAS-3769: - +1 for the patch, thanks [~kevalbhatt] for the patch. > UI: Changing page limit in Admin audits resets any filters applied on that > page > --- > > Key: ATLAS-3769 > URL: https://issues.apache.org/jira/browse/ATLAS-3769 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Keval Bhatt >Priority: Minor > Attachments: ATLAS-3769.patch > > > If any filters are set in the Audits Page in the Administration menu, > changing the page limit in Admin audits resets the filters applied on that > page. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3829) UI: Clicking on meanings from relationship tab should redirect to terms details page.
[ https://issues.apache.org/jira/browse/ATLAS-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130519#comment-17130519 ] Nikhil Bonte commented on ATLAS-3829: - +1 for the patch, thanks [~kevalbhatt] for the patch. > UI: Clicking on meanings from relationship tab should redirect to terms > details page. > - > > Key: ATLAS-3829 > URL: https://issues.apache.org/jira/browse/ATLAS-3829 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3829.patch, image-2020-06-09-17-14-17-856.png, > image-2020-06-09-17-14-17-989.png > > > * Assign term to Entity > * Go to relationship tab click on meanings link > * It should redirect to term detail page not entity detail page. > > !image-2020-06-09-17-14-17-989.png|width=564,height=343!!image-2020-06-09-17-14-17-856.png|width=555,height=334! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3816) Backport: Basic search issue with IndexSerializer
[
https://issues.apache.org/jira/browse/ATLAS-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3816:
Description:
*Background:*
Atlas instance with property
_"atlas.use.index.query.to.find.entity.by.unique.attributes=true"_
Direct index query which has pattern *"v."* throws exception, e.g.
v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
This will throw
{code:java}
java.lang.IllegalArgumentException: Found reference to non-existant property
key in query at position...{code}
*Solution:*
Backporting ATLAS-2371.
It is resolved with janusgraph, for titan implementation backporting required.
Query will be :
*$v$*"Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
Default value for index search prefix is _"$v$"_
Can be changed using the property _"atlas.graph.index.search.vertex.prefix"_
was:
*Background:*
Atlas with property
_"atlas.use.index.query.to.find.entity.by.unique.attributes=true"_
Direct index query which has pattern *"v."* throws exception, e.g.
v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
This will throw
{code:java}
java.lang.IllegalArgumentException: Found reference to non-existant property
key in query at position...{code}
*Solution:*
Backporting ATLAS-2371.
It is resolved with janusgraph, for titan implementation backporting required.
Query will be :
*$v$*"Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
Default value for index search prefix is "$v$"
Can be changed using the property "atlas.graph.index.search.vertex.prefix"
> Backport: Basic search issue with IndexSerializer
> -
>
> Key: ATLAS-3816
> URL: https://issues.apache.org/jira/browse/ATLAS-3816
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8.4
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Attachments:
> ATLAS-3816-Backport-Basic-search-issue-with-IndexSer-v2.patch
>
>
> *Background:*
> Atlas instance with property
> _"atlas.use.index.query.to.find.entity.by.unique.attributes=true"_
> Direct index query which has pattern *"v."* throws exception, e.g.
>
> v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
>
> This will throw
> {code:java}
> java.lang.IllegalArgumentException: Found reference to non-existant property
> key in query at position...{code}
>
> *Solution:*
> Backporting ATLAS-2371.
> It is resolved with janusgraph, for titan implementation backporting required.
> Query will be :
> *$v$*"Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
>
> Default value for index search prefix is _"$v$"_
> Can be changed using the property _"atlas.graph.index.search.vertex.prefix"_
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3816) Backport: Basic search issue with IndexSerializer
[
https://issues.apache.org/jira/browse/ATLAS-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3816:
Description:
*Background:*
Atlas with property
_"atlas.use.index.query.to.find.entity.by.unique.attributes=true"_
Direct index query which has pattern *"v."* throws exception, e.g.
v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
This will throw
{code:java}
java.lang.IllegalArgumentException: Found reference to non-existant property
key in query at position...{code}
*Solution:*
Backporting ATLAS-2371.
It is resolved with janusgraph, for titan implementation backporting required.
Query will be :
*$v$*"Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
Default value for index search prefix is "$v$"
Can be changed using the property "atlas.graph.index.search.vertex.prefix"
was:
*Background:*
Atlas with property
_"atlas.use.index.query.to.find.entity.by.unique.attributes=true"_
Direct index query which has pattern *"v."* throws exception, e.g.
v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
This will throw
{code:java}
java.lang.IllegalArgumentException: Found reference to non-existant property
key in query at position...{code}
*Solution:*
Backporting ATLAS-2371.
It is resolved with janusgraph, for titan implementation backporting required.
> Backport: Basic search issue with IndexSerializer
> -
>
> Key: ATLAS-3816
> URL: https://issues.apache.org/jira/browse/ATLAS-3816
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8.4
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Attachments:
> ATLAS-3816-Backport-Basic-search-issue-with-IndexSer-v2.patch
>
>
> *Background:*
> Atlas with property
> _"atlas.use.index.query.to.find.entity.by.unique.attributes=true"_
> Direct index query which has pattern *"v."* throws exception, e.g.
>
> v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
>
> This will throw
> {code:java}
> java.lang.IllegalArgumentException: Found reference to non-existant property
> key in query at position...{code}
>
> *Solution:*
> Backporting ATLAS-2371.
> It is resolved with janusgraph, for titan implementation backporting required.
> Query will be :
> *$v$*"Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
>
> Default value for index search prefix is "$v$"
> Can be changed using the property "atlas.graph.index.search.vertex.prefix"
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3240) Update 'http' urls to 'https' in maven settings
[ https://issues.apache.org/jira/browse/ATLAS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3240: Attachment: ATLAS-3240-Update-http-urls-to-https-in-maven-settin-#2.patch > Update 'http' urls to 'https' in maven settings > --- > > Key: ATLAS-3240 > URL: https://issues.apache.org/jira/browse/ATLAS-3240 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.1.0, 2.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Minor > Fix For: 1.2.0, 2.1.0 > > Attachments: > ATLAS-3240-Update-http-urls-to-https-in-maven-branch-0.8-#2.patch, > ATLAS-3240-Update-http-urls-to-https-in-maven-branch-0.8-v0.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3240) Update 'http' urls to 'https' in maven settings
[ https://issues.apache.org/jira/browse/ATLAS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3240: Attachment: ATLAS-3240-Update-http-urls-to-https-in-maven-branch-0.8-#2.patch > Update 'http' urls to 'https' in maven settings > --- > > Key: ATLAS-3240 > URL: https://issues.apache.org/jira/browse/ATLAS-3240 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.1.0, 2.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Minor > Fix For: 1.2.0, 2.1.0 > > Attachments: > ATLAS-3240-Update-http-urls-to-https-in-maven-branch-0.8-#2.patch, > ATLAS-3240-Update-http-urls-to-https-in-maven-branch-0.8-v0.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3240) Update 'http' urls to 'https' in maven settings
[ https://issues.apache.org/jira/browse/ATLAS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3240: Attachment: (was: ATLAS-3240-Update-http-urls-to-https-in-maven-settin-#2.patch) > Update 'http' urls to 'https' in maven settings > --- > > Key: ATLAS-3240 > URL: https://issues.apache.org/jira/browse/ATLAS-3240 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.1.0, 2.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Minor > Fix For: 1.2.0, 2.1.0 > > Attachments: > ATLAS-3240-Update-http-urls-to-https-in-maven-branch-0.8-#2.patch, > ATLAS-3240-Update-http-urls-to-https-in-maven-branch-0.8-v0.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-3240) Update 'http' urls to 'https' in maven settings
[ https://issues.apache.org/jira/browse/ATLAS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125677#comment-17125677 ] Nikhil Bonte edited comment on ATLAS-3240 at 6/4/20, 10:19 AM: --- Attached patch to backport this to branch-0.8 [^ATLAS-3240-Update-http-urls-to-https-in-maven-branch-0.8-v0.patch]. PC build : [https://builds.apache.org/job/PreCommit-ATLAS-Build-Test/1950/console] (Finished: SUCCESS) was (Author: nikhilbonte): Attached patch to backport this to branch-0.8 [^ATLAS-3240-Update-http-urls-to-https-in-maven-branch-0.8-v0.patch]. > Update 'http' urls to 'https' in maven settings > --- > > Key: ATLAS-3240 > URL: https://issues.apache.org/jira/browse/ATLAS-3240 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.1.0, 2.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Minor > Fix For: 1.2.0, 2.1.0 > > Attachments: > ATLAS-3240-Update-http-urls-to-https-in-maven-branch-0.8-v0.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3240) Update 'http' urls to 'https' in maven settings
[ https://issues.apache.org/jira/browse/ATLAS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3240: Attachment: ATLAS-3240-Update-http-urls-to-https-in-maven-branch-0.8-v0.patch > Update 'http' urls to 'https' in maven settings > --- > > Key: ATLAS-3240 > URL: https://issues.apache.org/jira/browse/ATLAS-3240 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.1.0, 2.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Minor > Fix For: 1.2.0, 2.1.0 > > Attachments: > ATLAS-3240-Update-http-urls-to-https-in-maven-branch-0.8-v0.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3240) Update 'http' urls to 'https' in maven settings
[ https://issues.apache.org/jira/browse/ATLAS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125677#comment-17125677 ] Nikhil Bonte commented on ATLAS-3240: - Attached patch to backport this to branch-0.8 [^ATLAS-3240-Update-http-urls-to-https-in-maven-branch-0.8-v0.patch]. > Update 'http' urls to 'https' in maven settings > --- > > Key: ATLAS-3240 > URL: https://issues.apache.org/jira/browse/ATLAS-3240 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.1.0, 2.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Minor > Fix For: 1.2.0, 2.1.0 > > Attachments: > ATLAS-3240-Update-http-urls-to-https-in-maven-branch-0.8-v0.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3816) Backport: Basic search issue with IndexSerializer
[
https://issues.apache.org/jira/browse/ATLAS-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3816:
Description:
*Background:*
Atlas with property
_"atlas.use.index.query.to.find.entity.by.unique.attributes=true"_
Direct index query which has pattern *"v."* throws exception, e.g.
v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
This will throw
{code:java}
java.lang.IllegalArgumentException: Found reference to non-existant property
key in query at position...{code}
*Solution:*
Backporting ATLAS-2371.
It is resolved with janusgraph, for titan implementation backporting required.
was:
*Background:*
Direct index query which has pattern *"v."* throws exception, e.g.
v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
This will throw
{code:java}
java.lang.IllegalArgumentException: Found reference to non-existant property
key in query at position...{code}
*Solution:*
Backporting ATLAS-2371.
It is resolved with janusgraph, for titan implementation backporting required.
> Backport: Basic search issue with IndexSerializer
> -
>
> Key: ATLAS-3816
> URL: https://issues.apache.org/jira/browse/ATLAS-3816
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8.4
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
>
> *Background:*
> Atlas with property
> _"atlas.use.index.query.to.find.entity.by.unique.attributes=true"_
> Direct index query which has pattern *"v."* throws exception, e.g.
>
> v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
>
> This will throw
> {code:java}
> java.lang.IllegalArgumentException: Found reference to non-existant property
> key in query at position...{code}
>
> *Solution:*
> Backporting ATLAS-2371.
> It is resolved with janusgraph, for titan implementation backporting required.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3816) Backport: Basic search issue with IndexSerializer
[
https://issues.apache.org/jira/browse/ATLAS-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3816:
Description:
*Background:*
Direct index query which has pattern *"v."* throws exception, e.g.
v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
This will throw
{code:java}
java.lang.IllegalArgumentException: Found reference to non-existant property
key in query at position...{code}
*Solution:*
Backporting ATLAS-2371.
It is resolved with janusgraph, for titan implementation backporting required.
was:
*Background:*
Direct index query which has pattern *"v."* throws exception, e.g.
v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
This will throw
{code:java}
java.lang.IllegalArgumentException: Found reference to non-existant property
key in query at position...{code}
*Solution:*
Backporting direct index query issue resolved in ATLAS-2371.
> Backport: Basic search issue with IndexSerializer
> -
>
> Key: ATLAS-3816
> URL: https://issues.apache.org/jira/browse/ATLAS-3816
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8.4
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
>
> *Background:*
> Direct index query which has pattern *"v."* throws exception, e.g.
>
> v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
>
> This will throw
> {code:java}
> java.lang.IllegalArgumentException: Found reference to non-existant property
> key in query at position...{code}
>
> *Solution:*
> Backporting ATLAS-2371.
> It is resolved with janusgraph, for titan implementation backporting required.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3816) Backport: Basic search issue with IndexSerializer
[
https://issues.apache.org/jira/browse/ATLAS-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3816:
Description:
*Background:*
Direct index query which has pattern *"v."* throws exception, e.g.
v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
This will throw
{code:java}
java.lang.IllegalArgumentException: Found reference to non-existant property
key in query at position...{code}
*Solution:*
Backporting direct index query issue resolved in ATLAS-2371.
was:
*Background:*
Direct index query which has pattern *"v."* throws exception, e.g.
v."Referenceable.qualifiedName":"atscale_agg_in*{color:#FF}v.{color}*as_agg_2cfb287d_dal_fixed_inco@edldev"
This will throw
{code:java}
java.lang.IllegalArgumentException: Found reference to non-existant property
key in query at position...{code}
*Solution:*
Backporting direct index query issue resolved in ATLAS-2371.
> Backport: Basic search issue with IndexSerializer
> -
>
> Key: ATLAS-3816
> URL: https://issues.apache.org/jira/browse/ATLAS-3816
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8.4
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
>
> *Background:*
> Direct index query which has pattern *"v."* throws exception, e.g.
>
> v."Referenceable.qualifiedName":"atscale_agg_in{color:#ff}v.{color}as_agg_2cfb287d_dal_fixed_inco@edldev"
>
> This will throw
> {code:java}
> java.lang.IllegalArgumentException: Found reference to non-existant property
> key in query at position...{code}
>
> *Solution:*
> Backporting direct index query issue resolved in ATLAS-2371.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3816) Backport: Basic search issue with IndexSerializer
[
https://issues.apache.org/jira/browse/ATLAS-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Bonte updated ATLAS-3816:
Description:
*Background:*
Direct index query which has pattern *"v."* throws exception, e.g.
v."Referenceable.qualifiedName":"atscale_agg_in*{color:#FF}v.{color}*as_agg_2cfb287d_dal_fixed_inco@edldev"
This will throw
{code:java}
java.lang.IllegalArgumentException: Found reference to non-existant property
key in query at position...{code}
*Solution:*
Backporting direct index query issue resolved in ATLAS-2371.
was:
*Background:*
Direct index query which has pattern *"v."* throws exception, e.g.
v."Referenceable.qualifiedName":"atscale_agg_in*v.*as_agg_2cfb287d_dal_fixed_inco@edldev"
This will throw
{code:java}
java.lang.IllegalArgumentException: Found reference to non-existant property
key in query at position...{code}
*Solution:*
Backporting direct index query issue resolved in ATLAS-2371.
> Backport: Basic search issue with IndexSerializer
> -
>
> Key: ATLAS-3816
> URL: https://issues.apache.org/jira/browse/ATLAS-3816
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8.4
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
>
> *Background:*
> Direct index query which has pattern *"v."* throws exception, e.g.
>
> v."Referenceable.qualifiedName":"atscale_agg_in*{color:#FF}v.{color}*as_agg_2cfb287d_dal_fixed_inco@edldev"
>
> This will throw
> {code:java}
> java.lang.IllegalArgumentException: Found reference to non-existant property
> key in query at position...{code}
>
> *Solution:*
> Backporting direct index query issue resolved in ATLAS-2371.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-3816) Backport: Basic search issue with IndexSerializer
Nikhil Bonte created ATLAS-3816:
---
Summary: Backport: Basic search issue with IndexSerializer
Key: ATLAS-3816
URL: https://issues.apache.org/jira/browse/ATLAS-3816
Project: Atlas
Issue Type: Bug
Affects Versions: 0.8.4
Reporter: Nikhil Bonte
Assignee: Nikhil Bonte
*Background:*
Direct index query which has pattern *"v."* throws exception, e.g.
v."Referenceable.qualifiedName":"atscale_agg_in*v.*as_agg_2cfb287d_dal_fixed_inco@edldev"
This will throw
{code:java}
java.lang.IllegalArgumentException: Found reference to non-existant property
key in query at position...{code}
*Solution:*
Backporting direct index query issue resolved in ATLAS-2371.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3805) UI:- Basic Search: System Attribute 'typeName' in classification filter, should list classification Names in drop down
[ https://issues.apache.org/jira/browse/ATLAS-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17117601#comment-17117601 ] Nikhil Bonte commented on ATLAS-3805: - +1 for the patch, Thanks Keval. > UI:- Basic Search: System Attribute 'typeName' in classification filter, > should list classification Names in drop down > --- > > Key: ATLAS-3805 > URL: https://issues.apache.org/jira/browse/ATLAS-3805 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3805.patch, Screen Shot 2020-05-21 at 12.55.53 > PM.png > > > !Screen Shot 2020-05-21 at 12.55.53 PM.png|width=602,height=342! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3798) Import Service: Percentage Display Problem with Large Datasets
[ https://issues.apache.org/jira/browse/ATLAS-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108334#comment-17108334 ] Nikhil Bonte commented on ATLAS-3798: - +1 for the patch. Thanks [~amestry] > Import Service: Percentage Display Problem with Large Datasets > -- > > Key: ATLAS-3798 > URL: https://issues.apache.org/jira/browse/ATLAS-3798 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Minor > Fix For: trunk > > Attachments: ATLAS-3798-Import-percentage-display-fix.patch > > > *Steps to Duplicate* > # Start migration import with 100M entities. Observe the log for > _last-imported_. > _Expected output:_ Display should proceed in increasing order of %ages. > _Actual output_: Display starts showing -ve %ages after 37%. > *Root Cause* > Existing implementation uses _integer_ for storing _currentIndex_. > *Additional Information* > * Start position computation is not impacted. > * Resume is not impacted. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3799) Migration Import: EntityConsumer Adds GUIDs to Result that Will Not Get Cleared
[ https://issues.apache.org/jira/browse/ATLAS-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108331#comment-17108331 ] Nikhil Bonte commented on ATLAS-3799: - +1 for the patch. Thanks [~amestry] > Migration Import: EntityConsumer Adds GUIDs to Result that Will Not Get > Cleared > --- > > Key: ATLAS-3799 > URL: https://issues.apache.org/jira/browse/ATLAS-3799 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: trunk > > Attachments: > ATLAS-3799-EntityConumer-only-adds-entity-GUIDs-that.patch > > > *Background* > Zip file-based migration import introduced _EntityConsumer_. This uses > _StatusReporter_ that is used to determine which which of the produced items > are processed. This, in turn, helps determine the right position to set in > case of resuming the import. > The _EntityConumer_ class is responsible for adding the right GUIDs to the > result that helps _StatusReporter_ determine the right GUIDs. This is done > correctly except that it also adds additional GUIDs that were updated or > deleted. This causes _StatusReporter_._processedSet_ to be filled with GUIDs > that will never be cleared. This will grow over time and can potentially lead > to memory pressure. > *Solution* > Add only the GUIDs that were processed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3775) Migration Import Display: Incorrect Status Display
[ https://issues.apache.org/jira/browse/ATLAS-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100023#comment-17100023 ] Nikhil Bonte commented on ATLAS-3775: - +1 for the patch, thanks [~amestry] . > Migration Import Display: Incorrect Status Display > -- > > Key: ATLAS-3775 > URL: https://issues.apache.org/jira/browse/ATLAS-3775 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3775-Migration-Import-Status-display-fix.patch > > > *Background* > Zip file based migration introduced _DataMigrationStatusService_. This class > is responsible for displaying the status. > *Steps to Duplicate* > Pre-requisites: > * Keep the REST http:///api/atlas/admin output open in a browser > window. > * Keep zip-file based migration import in progress. > * Ensure that you see the current status. Once migration progress, refresh > the REST API output to display the status. The status should be accurate. > * Refresh the REST API output after 5 mins. This will expire the status > cache and make a request to _DataMigrationService_ for status. > _Expected results_ > * Status returned by API should reflect the status logged. > > _Actual results_ > * There is a mismatch in the status. > * Additional information: The status is never updated for that session. > Root cause: > - _DataMigrationService_ maintains cached status object for each requestor. > This is not refreshed from the database status. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3702) Entity Creation: Improve Edge Creation
[ https://issues.apache.org/jira/browse/ATLAS-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076041#comment-17076041 ] Nikhil Bonte commented on ATLAS-3702: - +1 for the part 2 patch. Thanks Ashutosh for the patch. > Entity Creation: Improve Edge Creation > -- > > Key: ATLAS-3702 > URL: https://issues.apache.org/jira/browse/ATLAS-3702 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: trunk > > Attachments: > ATLAS-3702-Edge-creation-performance-improvements.-P.patch > > > *Background* > When creating entities with Atlas at scale, few inefficiencies were observed. > They were: > * _GraphHelper.getAdjacentEdgesByLabel_: The existing approach results in > high memory usage. The method could use graph api that already exists. > * _AtlasRelationshipStoreV2.getRelationshipEdge_: This does full vertex > comparison. This is expensive. > * Edge label is not index. Indexing this will improve speed of edge by label > lookup. > *Solution* > Profile Atlas with (using metrics) to establish baseline. > Use the fixes mentioned to the places above and profile. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3701) Performance improvements in writing audit logs - Classification dissociation
[ https://issues.apache.org/jira/browse/ATLAS-3701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte resolved ATLAS-3701. - Fix Version/s: 3.0.0 2.1.0 Resolution: Fixed > Performance improvements in writing audit logs - Classification dissociation > > > Key: ATLAS-3701 > URL: https://issues.apache.org/jira/browse/ATLAS-3701 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > Fix For: 2.1.0, 3.0.0 > > > Further to ATLAS-3568, > this will improve audit writing in case of classfication dissociation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3701) Performance improvements in writing audit logs - Classification dissociation
[ https://issues.apache.org/jira/browse/ATLAS-3701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Bonte updated ATLAS-3701: Component/s: atlas-core > Performance improvements in writing audit logs - Classification dissociation > > > Key: ATLAS-3701 > URL: https://issues.apache.org/jira/browse/ATLAS-3701 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Nikhil Bonte >Assignee: Nikhil Bonte >Priority: Major > > Further to ATLAS-3568, > this will improve audit writing in case of classfication dissociation -- This message was sent by Atlassian Jira (v8.3.4#803005)
