[jira] [Updated] (ATLAS-1911) UI / Search using entity and trait attributes : Specifying no value for one of the filters makes the complete filter null.
[
https://issues.apache.org/jira/browse/ATLAS-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-1911:
Fix Version/s: 0.8.1
1.0.0
> UI / Search using entity and trait attributes : Specifying no value for one
> of the filters makes the complete filter null.
> --
>
> Key: ATLAS-1911
> URL: https://issues.apache.org/jira/browse/ATLAS-1911
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
>
> 1.Created a kafka_topic with name="kt1" and empty description.
> 2.Searched kafka_topic in typeName , applied filters:
> 1. Name = kt1
> 2. Description = (empty Description)
> 3.The body sent to POST request is :
> {code}
> {"entityFilters":null,"tagFilters":null,"query":null,"excludeDeletedEntities":true,"limit":25,"typeName":"kafka_topic","classification":null}
> {code}
> entityFilters is null , and the Name applied filter was not found in UI or in
> the request body.The search result was similar to typeName='kafka_topic'.
> The same applies to tag filters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-1909) Import/Export : Exception while using "transforms" option during import
[
https://issues.apache.org/jira/browse/ATLAS-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-1909:
Fix Version/s: 1.0.0
> Import/Export : Exception while using "transforms" option during import
> ---
>
> Key: ATLAS-1909
> URL: https://issues.apache.org/jira/browse/ATLAS-1909
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
>Priority: Blocker
> Fix For: 1.0.0
>
> Attachments: Import_transforms_error.txt
>
>
> 1. Created a table t5 in cluster1.
> 2. Created the export zip file for table t5 on firing export API on cluster1.
> 3. Created the t5transforms.json file
> {code}
> {
> "options": {
>"transforms": {
> "hive_table": {
> "qualifiedName": [
> "replace:@cl1:@cl2"
> ]
> }
> }
> }
> }
> {code}
> 4.Fired import API on cluster2 using curl call :
> {code}
> curl -v -g -X POST -u admin:admin -H "Content-Type: multipart/form-data" -H
> "Cache-Control: no-cache" -F request=@t5transforms.json -F data=@t5.zip
> "http://cluster2:21000/api/atlas/admin/import;
> {code}
> Request failed with 500 Internal server error and the following message :
> {code}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
> java.lang.NullPointerException"}
> {code}
> Attached the complete exception stack trace found in cluster2's application
> logs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-1949) Fix coverity scan issues and IT failure due to ATLAS-1907
[ https://issues.apache.org/jira/browse/ATLAS-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1949: Fix Version/s: 1.0.0 > Fix coverity scan issues and IT failure due to ATLAS-1907 > - > > Key: ATLAS-1949 > URL: https://issues.apache.org/jira/browse/ATLAS-1949 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-1949.1.patch > > > Fix coverity scan issues and IT failure due to ATLAS-1907 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1959) Enhance relationship attributes to support different cardinality mappings
[ https://issues.apache.org/jira/browse/ATLAS-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1959: Fix Version/s: 1.0.0 > Enhance relationship attributes to support different cardinality mappings > - > > Key: ATLAS-1959 > URL: https://issues.apache.org/jira/browse/ATLAS-1959 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: trunk, 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-1959.1.patch > > > 1. Improve relationship model to support create/update operations and the > following cardinalities (previously supported using inverseReference): > * 1 to 1 > * 1 to many > * many to 1 > * many to many > 2. Change legacyLabel flag in AtlasRelationshipEndDef to boolean flag. > 3. Add unit tests for the above cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1980) Add relationship instance validation to check end point type
[
https://issues.apache.org/jira/browse/ATLAS-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-1980:
Fix Version/s: 1.0.0
Component/s: atlas-core
> Add relationship instance validation to check end point type
>
>
> Key: ATLAS-1980
> URL: https://issues.apache.org/jira/browse/ATLAS-1980
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: David Radley
>Assignee: David Radley
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-1980.patch
>
>
> Using a model RelationshipDef that is defines
> {
> "name": "CategoryAnchor",
> "typeVersion": "1.0",
> "endDef1": {
>"name": "categories",
>"type": "Glossary",
>"cardinality":"SET",
> "isContainer":true
> },
> "endDef2": {
>"name": "anchor",
>"type": "GlossaryCategory",
>"cardinality":"SINGLE"
> },
> "relationshipCategory":"COMPOSITION",
> "propagateTags":"NONE"
> },
> - it does not check that the guid of the relationship is actually of the
> right type. If I create an instance of the above relationships passing 2
> GlossaryCategory guids ; it works. This should be rejected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-1914) UI - Search using entity and trait attributes : "Clear" button doesn't clear the filter applied to a type
[ https://issues.apache.org/jira/browse/ATLAS-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1914: Fix Version/s: 0.8.1 1.0.0 > UI - Search using entity and trait attributes : "Clear" button doesn't clear > the filter applied to a type > - > > Key: ATLAS-1914 > URL: https://issues.apache.org/jira/browse/ATLAS-1914 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8.1, 1.0.0 > > Attachments: ATLAS-1914.patch > > > 1. Searched type "hive_table" and applied filter "name = table1" > 2.Clicked Search. > 3.Clicked Clear button , which cleared the type selected. > 4.Searched type "hive_table" again. The search had the same "name" filter > applied before Clearing. > Expected that the Clear button would clear the filter too. > Is this expected ? > Should there be a Save button instead to explicitly save the queries ? > > CC : [~kevalbhatt] [~apoorvnaik] [~ashutoshm][~madhan.neethiraj] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1997) Search indexer NPE
[ https://issues.apache.org/jira/browse/ATLAS-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1997: Affects Version/s: (was: trunk) Fix Version/s: (was: 0.8-incubating) (was: trunk) 0.8.2 1.0.0 Component/s: atlas-core Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/38297a84 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/096917e9 > Search indexer NPE > -- > > Key: ATLAS-1997 > URL: https://issues.apache.org/jira/browse/ATLAS-1997 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 0.8.2, 1.0.0 > > Attachments: > 0001-ATLAS-1997-Search-Indexer-NPE-on-the-vertex_index.patch > > > Getting the vertex index from the graph management system sometimes runs into > an NPE if the graph hasn't been completely initialized. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1999) Use AtlasRelatedObjectId to display relationshipAttribute values during entity retrieval
[ https://issues.apache.org/jira/browse/ATLAS-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1999: Affects Version/s: (was: trunk) 1.0.0 Fix Version/s: (was: trunk) 1.0.0 > Use AtlasRelatedObjectId to display relationshipAttribute values during > entity retrieval > > > Key: ATLAS-1999 > URL: https://issues.apache.org/jira/browse/ATLAS-1999 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-1999.1.patch > > > * Currently relationship attribute values during entity retrieval is using > AtlasObjectId format. Change this to use AtlasRelatedObjectId to contain > additional information for use during search and UI > * validate and normalize relationship attribute values during entity creation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1523) Implement GET entity by guid and unique attributes in V2 Entity API using AtlasObjectID
[ https://issues.apache.org/jira/browse/ATLAS-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1523: Fix Version/s: 0.8-incubating > Implement GET entity by guid and unique attributes in V2 Entity API using > AtlasObjectID > --- > > Key: ATLAS-1523 > URL: https://issues.apache.org/jira/browse/ATLAS-1523 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 0.8-incubating > > Attachments: ATLAS-1523.23.patch > > > Current implementation of GET API for entity v2 still routes to V1 entity > APIs and does a V1toV2 conversion. We need to directly query the v2 > entitiesStore to get the required entity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1527) Batch entity retrievals in DefaultMetadataService.loadEntities
[ https://issues.apache.org/jira/browse/ATLAS-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1527: Fix Version/s: 0.8-incubating Component/s: atlas-core Committed to master: http://git-wip-us.apache.org/repos/asf/atlas/commit/1e105174 > Batch entity retrievals in DefaultMetadataService.loadEntities > -- > > Key: ATLAS-1527 > URL: https://issues.apache.org/jira/browse/ATLAS-1527 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Wojciech Wojcik >Assignee: Wojciech Wojcik >Priority: Minor > Fix For: 0.8-incubating > > Attachments: rb56324.patch > > > DefaultMetadataService.loadEntities() is called at the conclusion of entity > creation and update, to load the created/updated entities which are passed to > the EntityChangeListener's. The entities are being loaded one at time, > because MetadataRepository does not expose a method to retrieve multiple > entities by GUID. MetadataRepository can be enhanced to provide a > getEntityDefinitions() entrypoint, and the implementation in > GraphBackedMetadataRepository can batch the vertex retrievals using > GraphHelper.getVerticesForGUIDs(). This will reduce the graph calls to > retrieve the vertices. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1510) Consolidate/batch calls to GraphBackedTypeStore.findVertex()
[ https://issues.apache.org/jira/browse/ATLAS-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1510: Fix Version/s: 0.8-incubating > Consolidate/batch calls to GraphBackedTypeStore.findVertex() > > > Key: ATLAS-1510 > URL: https://issues.apache.org/jira/browse/ATLAS-1510 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Jeffrey Hagelberg >Assignee: Jeffrey Hagelberg >Priority: Major > Fix For: 0.8-incubating > > > This showed up as a major hotspot during our profiling of the Atlas > initialization. The idea here is to reduce the number of queries made during > type creation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2153) UI : Adding more columns to the search table masks the "Remove tag" button
[ https://issues.apache.org/jira/browse/ATLAS-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2153: Fix Version/s: 0.8.3 1.0.0 > UI : Adding more columns to the search table masks the "Remove tag" button > --- > > Key: ATLAS-2153 > URL: https://issues.apache.org/jira/browse/ATLAS-2153 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Minor > Fix For: 1.0.0, 0.8.3 > > Attachments: ATLAS-2153.patch > > > For basic search typename = hive_table , 20 attributes can be added in the > columns filter. When more attributes are added , "Remove Tag" (Cross button) > on the Tag under Tags column is masked. This happens when the screen size is > less and more columns are added. When columns are removed , Remove button > shows up again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2145) Errors during build
[
https://issues.apache.org/jira/browse/ATLAS-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2145:
Fix Version/s: 0.8.3
1.0.0
> Errors during build
> ---
>
> Key: ATLAS-2145
> URL: https://issues.apache.org/jira/browse/ATLAS-2145
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 0.8-incubating, 1.0.0
>Reporter: Péter Gergő Barna
>Assignee: Péter Gergő Barna
>Priority: Major
> Fix For: 1.0.0, 0.8.3
>
> Attachments: ATLAS-2145-2.patch, ATLAS-2145-3.patch, ATLAS-2145.patch
>
>
> Compilation error while building atlas-intg
> atlas-intg error:
> {noformat}
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 8.358 s
> [INFO] Finished at: 2017-09-18T14:38:00+02:00
> [INFO] Final Memory: 70M/888M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile)
> on project atlas-intg: Compilation failure: Compilation failure:
> [ERROR]
> /Users/pbarna/Desktop/apache-source/atlas/intg/src/main/java/org/apache/atlas/model/SearchFilter.java:[20,32]
> package com.sun.jersey.core.util does not exist
> {noformat}
> dashboardv2 npm error:
> {noformat}
> [ERROR] npm ERR! path
> /Users/pbarna/Desktop/apache-source/atlas/dashboardv2/target/node_modules/js-beautify/js/bin/css-beautify.js
> [ERROR] npm ERR! code ENOENT
> [ERROR] npm ERR! errno -2
> [ERROR] npm ERR! syscall chmod
> [ERROR]
> [ERROR] npm ERR! enoent ENOENT: no such file or directory, chmod
> '/Users/pbarna/Desktop/apache-source/atlas/dashboardv2/target/node_modules/js-beautify/js/bin/css-beautify.js'
> [ERROR] npm ERR! enoent ENOENT: no such file or directory, chmod
> '/Users/pbarna/Desktop/apache-source/atlas/dashboardv2/target/node_modules/js-beautify/js/bin/css-beautify.js'
> [ERROR] npm ERR! enoent This is most likely not a problem with npm itself
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2146) Remove Powermock Usage
[ https://issues.apache.org/jira/browse/ATLAS-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2146: Fix Version/s: 0.8.3 1.0.0 Component/s: atlas-core Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/1dee77af - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/cbd60249 > Remove Powermock Usage > -- > > Key: ATLAS-2146 > URL: https://issues.apache.org/jira/browse/ATLAS-2146 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Minor > Fix For: 1.0.0, 0.8.3 > > Attachments: ATLAS-2146.patch > > > *Background* > Some time back _Powermocks_ library was added with the intention of being > able to test private methods in unit tests. Short coming of this is that does > do it in a type safe way. > *Solution* > Existing _TestNG_ framework supports _VisibleForTesting_ annotation that > allows for a type safe way to address this. > Short coming of this is that _VisibleForTesting_ does is supported only for a > given package. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2134) Code Improvement To Follow Best Practices
[ https://issues.apache.org/jira/browse/ATLAS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2134: Fix Version/s: (was: trunk) 0.8.3 1.0.0 Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/8eb9c956 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/4c7430dd > Code Improvement To Follow Best Practices > - > > Key: ATLAS-2134 > URL: https://issues.apache.org/jira/browse/ATLAS-2134 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 1.0.0, 0.8.3 > > > Code Improvement To Follow Best Practices -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2131) Issues during navigation from table in Tables tab with Include historical entities checked
[
https://issues.apache.org/jira/browse/ATLAS-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2131:
Fix Version/s: 0.8.2
1.0.0
> Issues during navigation from table in Tables tab with Include historical
> entities checked
> --
>
> Key: ATLAS-2131
> URL: https://issues.apache.org/jira/browse/ATLAS-2131
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.2, 1.0.0
>
> Attachments: TablesInDbNavigation.mov
>
>
> Following is one of the scenarios where there is issue when navigating. Not
> sure what other scenarios can also lead to the issue.
> 1.Created 100 hive_table entities in a database db1.
> 2. Fired basic query hive_db = db1.
> 3. In the Tables tab of db1 , all 100 tables were listed.
> 4.Checked Include historical entities check box. Now , URL changed to
> {code}
> localhost:21000/#!/search/searchResult?guid=8c7549db-c514-419e-bc2c-f3fe9e3c34f6=relationship=true=true
> {code}
> 5.Clicked on any of the tables in the result which landed in the detailsPage
> of the table.
> 6.Now , when "Back To Results" button is clicked , URL changed to
> {code}
> http://localhost:21000/#!/search/searchResult?guid=8c7549db-c514-419e-bc2c-f3fe9e3c34f6=relationship=true=true
> {code}
> and landed in Atlas home page (ie. Search page) with all search cleared.
> 7. Fired some basic query and clicked Search . Search was not functioning.
> 8.Switched from Basic - DSL - Basic . Now fired search again . This time
> search was working . But Include Historical entities was checked on by
> default.
> 9. If Include historical entities was not checked in Tables tab and any
> entity was selected , this issue was not seen.
> Added a screen recording of the scenario explained above.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2091) Search using entity and trait attributes - "#" in string attribute filter doesn't fetch results
[ https://issues.apache.org/jira/browse/ATLAS-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2091: Fix Version/s: 0.8.2 1.0.0 > Search using entity and trait attributes - "#" in string attribute filter > doesn't fetch results > --- > > Key: ATLAS-2091 > URL: https://issues.apache.org/jira/browse/ATLAS-2091 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Assignee: Apoorv Naik >Priority: Major > Fix For: 0.8.2, 1.0.0 > > Attachments: > 0001-ATLAS-2091-Attribute-values-containing-Tokenizer-cha.patch > > > 1. Created an hdfs_path entity with owner name = "user#3" > 2. Fired basic search with type name = hdfs_path and filter - owner = user#3. > hdfs_path entity was returned. > 3. Fired basic search with type name = hdfs_path and filter - owner contains > user#3. No entity is returned. > Other than "=" , operators like != , contains , ends_with , begins_with are > not fetching expected results due to # in search filter key. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2010) Atlas Hook consumer runs into type not found
[ https://issues.apache.org/jira/browse/ATLAS-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2010: Fix Version/s: (was: 0.8-incubating) (was: trunk) 1.0.0 > Atlas Hook consumer runs into type not found > > > Key: ATLAS-2010 > URL: https://issues.apache.org/jira/browse/ATLAS-2010 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk, 0.8-incubating, 0.8.1 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 0.8.1, 1.0.0 > > Attachments: > 0001-ATLAS-2010-Hook-should-start-consuming-messages-only.patch > > > Sometimes the Hook consumer bean gets created before the type registry has > been fully initialized and when it's trying to create the entity, the type > name is missing from the registry. > Add depends on the HookConsumer class to make sure that the creation only > happens after type registry is completely bootstrapped. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2010) Atlas Hook consumer runs into type not found
[ https://issues.apache.org/jira/browse/ATLAS-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478466#comment-16478466 ] Madhan Neethiraj commented on ATLAS-2010: - Committed to master: http://git-wip-us.apache.org/repos/asf/atlas/commit/eb5d6fcd > Atlas Hook consumer runs into type not found > > > Key: ATLAS-2010 > URL: https://issues.apache.org/jira/browse/ATLAS-2010 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk, 0.8-incubating, 0.8.1 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 0.8.1, 1.0.0 > > Attachments: > 0001-ATLAS-2010-Hook-should-start-consuming-messages-only.patch > > > Sometimes the Hook consumer bean gets created before the type registry has > been fully initialized and when it's trying to create the entity, the type > name is missing from the registry. > Add depends on the HookConsumer class to make sure that the creation only > happens after type registry is completely bootstrapped. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2010) Atlas Hook consumer runs into type not found
[ https://issues.apache.org/jira/browse/ATLAS-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2010: Affects Version/s: (was: 0.8.1) (was: 0.8-incubating) (was: trunk) Fix Version/s: (was: 0.8.1) > Atlas Hook consumer runs into type not found > > > Key: ATLAS-2010 > URL: https://issues.apache.org/jira/browse/ATLAS-2010 > Project: Atlas > Issue Type: Bug >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: > 0001-ATLAS-2010-Hook-should-start-consuming-messages-only.patch > > > Sometimes the Hook consumer bean gets created before the type registry has > been fully initialized and when it's trying to create the entity, the type > name is missing from the registry. > Add depends on the HookConsumer class to make sure that the creation only > happens after type registry is completely bootstrapped. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2019) Search using entity and trait attributes - Equals comparison using filter key when filter key is present between special characters
[ https://issues.apache.org/jira/browse/ATLAS-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2019: Fix Version/s: (was: 0.8-incubating) (was: trunk) 0.8.1 1.0.0 > Search using entity and trait attributes - Equals comparison using filter key > when filter key is present between special characters > --- > > Key: ATLAS-2019 > URL: https://issues.apache.org/jira/browse/ATLAS-2019 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Assignee: Apoorv Naik >Priority: Major > Fix For: 0.8.1, 1.0.0 > > > 1. Created hdfs_path entity with name = "user" , path = "/user" > 2. Created another hdfs_path with name="dir1" , path = "/user/dir1" > 3. Searched for hdfs_path , filter Path = /user > 4. The search listed down both the hdfs_path entities - user and dir1. > Expected that only "user" entity would be returned. > Here, the filter key is "/user" and if the filter key is present between > special characters in the attribute values ( "/" in this case) , all those > entities are returned. > Please note that , filter applied is "=" and not "contains" > Created few random hdfs_path entities for testing : > For the query type ="hdfs_path" and path = "/user" , entities with following > path attribute values are returned : > * user > * /user > * user/ > * /user/dir1 > * @user@dir1 > * /user@dir1 > Entities with following path values are *NOT* returned > * /userdir1 > * rootuser/dir2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2047) NotificationHookConsumer: Exception Thrown by Kafka Consumer Ends up Filling Logs Due to Incorrect Handling
[ https://issues.apache.org/jira/browse/ATLAS-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2047: Affects Version/s: (was: trunk) Fix Version/s: (was: trunk) 0.8.2 1.0.0 Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/b837c0ee - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/cb151bdc > NotificationHookConsumer: Exception Thrown by Kafka Consumer Ends up Filling > Logs Due to Incorrect Handling > > > Key: ATLAS-2047 > URL: https://issues.apache.org/jira/browse/ATLAS-2047 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 0.8.2, 1.0.0 > > Attachments: ATLAS-2047-HookConsumer-ExceptionHandling.patch > > > *Background* > _KafkaConsumer_ is abstracted by _AtlasKafkaConsumer_. This is run using > _HookConsumer_ which is derived from _kafka.utils.ShutdownableThread_. > The _ShutdownableThread_ manages the thread. It handles exceptions thrown in > the _doWork_ method and logs them. > *Problem* > Exception reported in the bug is thrown by _KafkaConsumer_ is handed by > _HookConsumer_. Exception is logged but the thread keeps running. In cases > where Kafa is in irrecoverable state, this behavior ends up filling up logs > and providing no value in return. > *Solution* > Let _ShutdownableThread_ hand exceptions thrown by _KafkaConsumer_. Stop the > thread if _KafkaConsumer_ suffers from irrecoverable error. This will avoid > the situation described in the problem section. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2050) Add helper method in relationship store to check if entity has relationship associated
[ https://issues.apache.org/jira/browse/ATLAS-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2050: Affects Version/s: (was: trunk) > Add helper method in relationship store to check if entity has relationship > associated > -- > > Key: ATLAS-2050 > URL: https://issues.apache.org/jira/browse/ATLAS-2050 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Minor > Fix For: 1.0.0 > > Attachments: ATLAS-2050.2.patch > > > Add helper method in AtlasRelationshipStoreV1 to check whether entity vertex > has a relationship associated with a relationship type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2051) Provide a utility to Import HBase entities into Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2051: Affects Version/s: (was: trunk) Fix Version/s: (was: trunk) 0.8.3 1.0.0 Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/d1e79fa0 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/d6e69c6d, http://git-wip-us.apache.org/repos/asf/atlas/commit/239fa807 > Provide a utility to Import HBase entities into Atlas > - > > Key: ATLAS-2051 > URL: https://issues.apache.org/jira/browse/ATLAS-2051 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 1.0.0, 0.8.3 > > Attachments: > 0001-ATLAS-2051-Provide-a-utility-to-Import-HBase-entitie.patch, > 0001-ATLAS-2051-Provide-a-utility-to-Import-HBase-entitie_002.patch, > 0001-ATLAS-2051-Provide-a-utility-to-Import-HBase-entitie_003.patch, > 0001-ATLAS-2051-Provide-a-utility-to-Import-HBase-entitie_004.patch, > 0001-ATLAS-2051-Provide-a-utility-to-Import-HBase-entitie_005.patch > > > Provide a utility to do Import HBase entities into Atlas -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2054) Add flag to exclude attribute mapping in FullTextMapper
[ https://issues.apache.org/jira/browse/ATLAS-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2054: Fix Version/s: (was: 0.8-incubating) (was: trunk) 0.8.3 1.0.0 > Add flag to exclude attribute mapping in FullTextMapper > --- > > Key: ATLAS-2054 > URL: https://issues.apache.org/jira/browse/ATLAS-2054 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk, 0.8-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Critical > Fix For: 1.0.0, 0.8.3 > > Attachments: ATLAS-2054.1.patch > > > Add property in atlas-application.properties to exclude listed attributes to > be excluded when mapping fulltext > e.g. > atlas.search.fulltext.followReferences=false > atlas.search.fulltext.type.hive_table.attributes.exclude=profileData > atlas.search.fulltext.type.hive_column.attributes.exclude=profileData -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ATLAS-2081) Test EntityJerseyResourceIT#testPartialUpdate fails consistently
[
https://issues.apache.org/jira/browse/ATLAS-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj reopened ATLAS-2081:
-
> Test EntityJerseyResourceIT#testPartialUpdate fails consistently
>
>
> Key: ATLAS-2081
> URL: https://issues.apache.org/jira/browse/ATLAS-2081
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 1.0.0
> Environment: Ubuntu:14.04
> $java -version
> openjdk version "1.8.0_111"
> OpenJDK Runtime Environment (build 1.8.0_111-8u111-b14-3~14.04.1-b14)
> OpenJDK 64-Bit Server VM (build 25.111-b14, mixed mode)
>Reporter: Sneha Kanekar
>Priority: Major
> Labels: ppc64le, x86
> Attachments: standard_output_log.txt
>
>
> The integration test
> org.apache.atlas.web.integration.EntityJerseyResourceIT.testPartialUpdate
> fails consistently with java assertion error. The error message is as follows:
> {code:borderStyle=solid}
> java.lang.AssertionError: expected:<1> but was:<3>
> at
> org.apache.atlas.web.integration.EntityJerseyResourceIT.testPartialUpdate(EntityJerseyResourceIT.java:881)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ATLAS-2081) Test EntityJerseyResourceIT#testPartialUpdate fails consistently
[
https://issues.apache.org/jira/browse/ATLAS-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-2081.
-
Resolution: Cannot Reproduce
> Test EntityJerseyResourceIT#testPartialUpdate fails consistently
>
>
> Key: ATLAS-2081
> URL: https://issues.apache.org/jira/browse/ATLAS-2081
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 1.0.0
> Environment: Ubuntu:14.04
> $java -version
> openjdk version "1.8.0_111"
> OpenJDK Runtime Environment (build 1.8.0_111-8u111-b14-3~14.04.1-b14)
> OpenJDK 64-Bit Server VM (build 25.111-b14, mixed mode)
>Reporter: Sneha Kanekar
>Priority: Major
> Labels: ppc64le, x86
> Attachments: standard_output_log.txt
>
>
> The integration test
> org.apache.atlas.web.integration.EntityJerseyResourceIT.testPartialUpdate
> fails consistently with java assertion error. The error message is as follows:
> {code:borderStyle=solid}
> java.lang.AssertionError: expected:<1> but was:<3>
> at
> org.apache.atlas.web.integration.EntityJerseyResourceIT.testPartialUpdate(EntityJerseyResourceIT.java:881)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2064) Compress Hook Messages Posted to Kafka Atlas Topic
[ https://issues.apache.org/jira/browse/ATLAS-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2064: Fix Version/s: (was: trunk) > Compress Hook Messages Posted to Kafka Atlas Topic > -- > > Key: ATLAS-2064 > URL: https://issues.apache.org/jira/browse/ATLAS-2064 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 0.8-incubating >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: ATLAS-2064-compressed-hook-message-envelope.patch > > > *Background* > Messages posted by hooks to Atlas Kafka topics are JSON format. > Kafka imposes a 1MB limit on the message size. > Occasionally, depending on operations performed, this threshold is reached. > This results in messages being dropped. > The entities are thus not reflected in Atlas. > *Solution* > Applying compression to these message will alleviate the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2064) Compress Hook Messages Posted to Kafka Atlas Topic
[ https://issues.apache.org/jira/browse/ATLAS-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2064. - Resolution: Duplicate > Compress Hook Messages Posted to Kafka Atlas Topic > -- > > Key: ATLAS-2064 > URL: https://issues.apache.org/jira/browse/ATLAS-2064 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 0.8-incubating >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: trunk > > Attachments: ATLAS-2064-compressed-hook-message-envelope.patch > > > *Background* > Messages posted by hooks to Atlas Kafka topics are JSON format. > Kafka imposes a 1MB limit on the message size. > Occasionally, depending on operations performed, this threshold is reached. > This results in messages being dropped. > The entities are thus not reflected in Atlas. > *Solution* > Applying compression to these message will alleviate the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ATLAS-2064) Compress Hook Messages Posted to Kafka Atlas Topic
[ https://issues.apache.org/jira/browse/ATLAS-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj reopened ATLAS-2064: - > Compress Hook Messages Posted to Kafka Atlas Topic > -- > > Key: ATLAS-2064 > URL: https://issues.apache.org/jira/browse/ATLAS-2064 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 0.8-incubating >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: trunk > > Attachments: ATLAS-2064-compressed-hook-message-envelope.patch > > > *Background* > Messages posted by hooks to Atlas Kafka topics are JSON format. > Kafka imposes a 1MB limit on the message size. > Occasionally, depending on operations performed, this threshold is reached. > This results in messages being dropped. > The entities are thus not reflected in Atlas. > *Solution* > Applying compression to these message will alleviate the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1907) Create RelationshipDefs for all base models and use this definitions when creating edges for entities
[ https://issues.apache.org/jira/browse/ATLAS-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1907: Affects Version/s: (was: trunk) Fix Version/s: 1.0.0 > Create RelationshipDefs for all base models and use this definitions when > creating edges for entities > - > > Key: ATLAS-1907 > URL: https://issues.apache.org/jira/browse/ATLAS-1907 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 0.8.1, 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-1907.1.patch > > > Create relationshipDefs for all out of the box models. Use relationshipDef > information when creating edges for composite attributes in entities. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1905) Search UI is confusing to user
[ https://issues.apache.org/jira/browse/ATLAS-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1905: Fix Version/s: 0.8.2 1.0.0 > Search UI is confusing to user > -- > > Key: ATLAS-1905 > URL: https://issues.apache.org/jira/browse/ATLAS-1905 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating >Reporter: Laura Ngo >Assignee: pratik pandey >Priority: Major > Fix For: 0.8.2, 1.0.0 > > Attachments: ATLAS-1905.patch > > > As a business user it has taken me days to understand why my UI search > queries were 'unstable' - it turns out the UI is unclear! > The search interface must be clear to business users. What we actually have > is: > Basic search > * Search By Type > * Search By Tag > * Search By Query > Advanced search > * Search By Type > * Search By Query > So it looks as if the Advanced search has fewer options than the basic! > ...but worse, the two aren't analogous despite having the same lables. > A 'Search By Query' in Basic return many results, but 'Search By Query' in > Advanced returns 1 for hive_table where > qualifiedName='db_name.table_name@clauster_name'. > Only by reading JIRA tickets here did I realise that Basic was a full text > search whereas Advanced as DSL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1943) Fix IT failure, lineage due to incorrect inverse reference check using relationship
[ https://issues.apache.org/jira/browse/ATLAS-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1943: Fix Version/s: 1.0.0 Component/s: atlas-core > Fix IT failure, lineage due to incorrect inverse reference check using > relationship > --- > > Key: ATLAS-1943 > URL: https://issues.apache.org/jira/browse/ATLAS-1943 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Critical > Fix For: 1.0.0 > > Attachments: ATLAS-1943.1.patch > > > Fix the following IT failures due to > Failed tests: > EntityJerseyResourceIT.testCompleteUpdate:952 » AtlasService Metadata > service ... > EntityJerseyResourceIT.testPartialUpdate:877 » AtlasService Metadata > service A... > After creating a relationship for inverse reference attribute, call is made > to create relationship for ownedRef attribute. But relationship for ownedRef > has already been created and we see exception in log - “relationship already > exists”. > For e.g.: after creating a relationship for hive_storagedesc.table, a new > relationship to create hive_table.sd is attempted – but fails since > relationship already exists (already created). Added a new method > getOrCreate(relationship) - If a relationship already exists between two > entities on an attribute retrieve it, if not create one. Validated the patch > by creating hive_table, views – lineage are rendered fine. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1938) UI - Search using entity and trait attributes - Refresh Button fires the search query (Basic/DSL) again.
[ https://issues.apache.org/jira/browse/ATLAS-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1938: Fix Version/s: 0.8.1 1.0.0 Component/s: atlas-webui > UI - Search using entity and trait attributes - Refresh Button fires the > search query (Basic/DSL) again. > > > Key: ATLAS-1938 > URL: https://issues.apache.org/jira/browse/ATLAS-1938 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar >Priority: Major > Fix For: 0.8.1, 1.0.0 > > Attachments: ATLAS-1938.1.patch, ATLAS-1938.2.patch > > > On clicking the Refresh Button to refresh types (data-id : refreshBtn) , > makes the following 2 queries : > # /api/atlas/v2/types/typedefs/headers > # Search query > Before the new search feature in place , only query no.1 was made. > In Advanced search tab , when refresh button is clicked without any type or > query , following invalid query is made in addition to query no.1 > http://localhost:21000/api/atlas/v2/search? > which throws 500 Internal server error. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1927) UI - changing the look and feel of attribute in details page.
[ https://issues.apache.org/jira/browse/ATLAS-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1927: Fix Version/s: 0.8.1 1.0.0 Component/s: atlas-webui > UI - changing the look and feel of attribute in details page. > - > > Key: ATLAS-1927 > URL: https://issues.apache.org/jira/browse/ATLAS-1927 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar >Priority: Major > Fix For: 0.8.1, 1.0.0 > > Attachments: ATLAS-1927.1.patch, ATLAS-1927.2.patch, > ATLAS-1927.3.patch, ATLAS-1927.4.patch, ATLAS-1927.patch > > > Show the attributes of entities in tag format instead of showing comma(,) > separator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1979) Update storm model relationship category and fix for UT and Coverity scan issues
[ https://issues.apache.org/jira/browse/ATLAS-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1979: Fix Version/s: 1.0.0 Component/s: atlas-core > Update storm model relationship category and fix for UT and Coverity scan > issues > > > Key: ATLAS-1979 > URL: https://issues.apache.org/jira/browse/ATLAS-1979 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-1979.1.patch > > > * Update storm_topology_nodes relationshipCategory from ASSOCIATION to > AGGREGATION > * Fix the following UT failures: > _Failed tests: > > AtlasRelationshipStoreHardDeleteV1Test>AtlasRelationshipStoreV1Test.testDepartmentEmployeeEntitiesUsingRelationship:172 > expected: but was:<[]> > > AtlasRelationshipStoreSoftDeleteV1Test>AtlasRelationshipStoreV1Test.testDepartmentEmployeeEntitiesUsingRelationship:172 > expected: but was:<[]>_ > * Fix coverity scan issues flagged in last report related to ATLAS-1959 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1984) Use AtlasRelatedObjectId to refer to relationship attributes during entity create/update
[
https://issues.apache.org/jira/browse/ATLAS-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-1984:
Affects Version/s: (was: trunk)
Fix Version/s: 1.0.0
> Use AtlasRelatedObjectId to refer to relationship attributes during entity
> create/update
>
>
> Key: ATLAS-1984
> URL: https://issues.apache.org/jira/browse/ATLAS-1984
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Affects Versions: 1.0.0
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-1984.1.patch
>
>
> AtlasObjectId is used to refer to entity attributes referring to another
> entity.
> hive_table.columns => List
> hive_table.db => AtlasObjectId
> Change this to use AtlasRelatedObjectId with the following structure:
> class AtlasRelatedObjectId {
>String relationshipGuid;
>String displayText;
>AtlasStruct relationshipAttributes;
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-1992) UI : Restrict unnecessary API call on selecting columns from drop-down (search table)
[ https://issues.apache.org/jira/browse/ATLAS-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1992: Fix Version/s: 0.8.1 1.0.0 Component/s: atlas-webui > UI : Restrict unnecessary API call on selecting columns from drop-down > (search table) > - > > Key: ATLAS-1992 > URL: https://issues.apache.org/jira/browse/ATLAS-1992 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8.1, 1.0.0 > > > API call should not hit if data available in the collection. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1493) Create Entity in UI : Inputs,Outputs attributes of types make the same DSL query twice.
[
https://issues.apache.org/jira/browse/ATLAS-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-1493:
Fix Version/s: 0.8-incubating
> Create Entity in UI : Inputs,Outputs attributes of types make the same DSL
> query twice.
> ---
>
> Key: ATLAS-1493
> URL: https://issues.apache.org/jira/browse/ATLAS-1493
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Trivial
> Fix For: 0.8-incubating
>
>
> Types inheriting Process have Inputs , Outputs field make same DSL query
> twice, once for Inputs and once for Outputs while Creating /Editing an Entity
> in UI.
> DSL query :
> {code}
> /api/atlas/discovery/search/dsl?query=DataSet
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-1488) Create Entity in UI : FileSize attribute of hdfs_path and fs_path is long. Opens a calendar when clicked.(UI bug)
[ https://issues.apache.org/jira/browse/ATLAS-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1488: Fix Version/s: 0.8-incubating Component/s: atlas-webui > Create Entity in UI : FileSize attribute of hdfs_path and fs_path is long. > Opens a calendar when clicked.(UI bug) > - > > Key: ATLAS-1488 > URL: https://issues.apache.org/jira/browse/ATLAS-1488 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Minor > Fix For: 0.8-incubating > > > hdfs_path and fs_path have FileSize (long type) as one of its attributes . > Clicking on the field when creating /editing hdfs_path/fs_path , opens up a > calendar. Providing a long number (valid input) or date for the same field , > it is always updated as 0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1521) Update UI to eliminate REST calls to obtain schema data
[
https://issues.apache.org/jira/browse/ATLAS-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-1521:
Fix Version/s: 0.8-incubating
> Update UI to eliminate REST calls to obtain schema data
> ---
>
> Key: ATLAS-1521
> URL: https://issues.apache.org/jira/browse/ATLAS-1521
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Madhan Neethiraj
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1521.1.patch, ATLAS-1521.2.patch, ATLAS-1521.patch
>
>
> When rendering entity details page, UI makes a REST API call to
> /schema/{guid} to obtain the schema data. For entity types that don't support
> the notion of schema, this REST API call returns an error. When such error is
> returned, UI does not add 'Schema' tab to the details page. When the call
> returns data, UI renders the data in 'Schema' tab.
> Given that only few entity-types (like hive_table) support schema, most calls
> to retrieve schema return an error. Having additional schema related
> information in the type can eliminate the need for unnecessary REST calls.
> ATLAS-1517 introduces additional data in 'typeDefOptions' attribute of
> entity-type definition. UI can use the following logic to render the schema
> tab contents:
> # Does an entity-type support schema?
> Is {{entityDef.typeDefOptions\[schemaElementsAttribute]}} set and its value
> non empty? If yes, schema is supported else not-supported. For hive_table
> type, this will be set to 'columns' - as shown below:
> {code}
> "typeDefOptions": {
> "schemaElementsAttribute": "columns"
> }
> {code}
> # How does UI get the data to display in schema tab?
> Value of {{entityDef.typeDefOptions\[schemaElementsAttribute]}} will be the
> name of the attribute in the entity being rendered. This attribute should be
> of type array. The value of this attribute will have the data needed to
> render the schema tab
> # What are the columns to display in schema tab?
> Each element of the array attribute value will hold an entity/struct
> instance.For example, In case of hive_table, columns attribute will have an
> array of hive_column objects. From each such element, UI should get value of
> attributes listed in {{elementDef.typeDefOptions\[schemaAttributes]}} to
> render the schema table. For example, hive_column will have the following:
> {code}
> "typeDefOptions": {
> "schemaAttributes": "[\"name\", \"description\", \"owner\", \"type\",
> \"comment\", \"position\"]"
> }
> {code}
> The value will be a json-ified string array.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-1491) UI : Properties tab of detailsPage of all entities has "columns" field.
[ https://issues.apache.org/jira/browse/ATLAS-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1491: Fix Version/s: 0.8-incubating > UI : Properties tab of detailsPage of all entities has "columns" field. > --- > > Key: ATLAS-1491 > URL: https://issues.apache.org/jira/browse/ATLAS-1491 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Minor > Fix For: 0.8-incubating > > > Properties tab of all entities has "columns" field. No other entity except > hive_table has values for "columns". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1492) Create Entity in UI : Inputs and Outputs field of types takes forever to list the entities (UI issue)
[
https://issues.apache.org/jira/browse/ATLAS-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-1492:
Fix Version/s: 0.8-incubating
> Create Entity in UI : Inputs and Outputs field of types takes forever to list
> the entities (UI issue)
> -
>
> Key: ATLAS-1492
> URL: https://issues.apache.org/jira/browse/ATLAS-1492
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 0.8-incubating
>
>
> Types with Process as supertype have Inputs and Outputs field which are of
> type array . DSL Query :
> {code}
> /api/atlas/discovery/search/dsl?query=DataSet
> {code}
> returns response soon . But in the Edit Entity window, Inputs and Outputs
> doesn't return the entities in the drop down list box.
> Example :
> In my cluster setup , the above DSL query returned 100 results in less than 3
> seconds but the UI doesn't list down the entities.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-1564) EntityResource v1 should start routing its calls to v2 EntityREST
[ https://issues.apache.org/jira/browse/ATLAS-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1564: Fix Version/s: 0.8-incubating > EntityResource v1 should start routing its calls to v2 EntityREST > - > > Key: ATLAS-1564 > URL: https://issues.apache.org/jira/browse/ATLAS-1564 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 0.8-incubating > > Attachments: ATLAS-1564.3.patch > > > With the v2 implementation of EntityREST ready, we must start routing all v1 > entity CRUD calls to start using v2 APIs in EntityREST. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1585) Search result page should show the entityType for each result
[
https://issues.apache.org/jira/browse/ATLAS-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-1585:
Fix Version/s: 0.8-incubating
> Search result page should show the entityType for each result
> -
>
> Key: ATLAS-1585
> URL: https://issues.apache.org/jira/browse/ATLAS-1585
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Srikanth Venkat
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1585.patch
>
>
> Currently, the search result page shows the following columns:
> {noformat}
> - Name
> - Description
> - Owner
> - Tags
> {noformat}
> In addition, it will be helpful to include the entityType for each entry in
> the result - given that the result might include entities of different types,
> especially in full-text search and tag-search.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-1578) Problem with Firefox UI : While creating/editing entity in UI ,value to be selected from a drop down list gets auto selected.
[ https://issues.apache.org/jira/browse/ATLAS-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1578: Fix Version/s: 0.8.1 > Problem with Firefox UI : While creating/editing entity in UI ,value to be > selected from a drop down list gets auto selected. > - > > Key: ATLAS-1578 > URL: https://issues.apache.org/jira/browse/ATLAS-1578 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui > Environment: Firefox 45.0 >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Minor > Fix For: 0.8.1, 1.0.0 > > > When creating hbase_column_family , hbase_table is one of its attributes > which is a drop down list of all hbase_tables. Even before providing the > hbase_table, an hbase_table entity is pre selected. This preselection doesn't > happen on Chrome or Safari. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1555) Move classification endpoint from Entities API to Entity API and remove Entities API
[ https://issues.apache.org/jira/browse/ATLAS-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1555: Fix Version/s: 0.8-incubating Component/s: atlas-core > Move classification endpoint from Entities API to Entity API and remove > Entities API > > > Key: ATLAS-1555 > URL: https://issues.apache.org/jira/browse/ATLAS-1555 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Vimal Sharma >Assignee: Vimal Sharma >Priority: Major > Fix For: 0.8-incubating > > Attachments: ATLAS-1555.patch > > > Entities API has a single method(API endpoint) to associate a classification > to multiple entities. > Move this classification endpoint from Entities API to Entity API and remove > Entities API -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1565) Create EntityREST endpoints for delete operations
[ https://issues.apache.org/jira/browse/ATLAS-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1565: Fix Version/s: 0.8-incubating > Create EntityREST endpoints for delete operations > - > > Key: ATLAS-1565 > URL: https://issues.apache.org/jira/browse/ATLAS-1565 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 0.8-incubating > > Attachments: ATLAS-1565.1.patch > > > EntityREST delete endpoints need to hook to the v2 delete methods in v2 > entitiesStore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1562) Not able to delete hbase_column_family once associated to the hbase_table.
[ https://issues.apache.org/jira/browse/ATLAS-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1562: Fix Version/s: 0.8-incubating > Not able to delete hbase_column_family once associated to the hbase_table. > -- > > Key: ATLAS-1562 > URL: https://issues.apache.org/jira/browse/ATLAS-1562 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8-incubating > > > Created > 1. hbase_table "table1" > 2. hbase_column_family "colfam1" wit hbase_table as "table1" > 3. Edited "table1" and added "colfam1" . Column family is added. > 4. Edited "table1" and removed "colfam1". Column family is not removed and > still associated to table1. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2689) Change version from 1.0.0-SNAPSHOT to 1.0.0
[ https://issues.apache.org/jira/browse/ATLAS-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2689: Attachment: ATLAS-2689.patch > Change version from 1.0.0-SNAPSHOT to 1.0.0 > --- > > Key: ATLAS-2689 > URL: https://issues.apache.org/jira/browse/ATLAS-2689 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 1.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Attachments: ATLAS-2689.patch > > > Update pom.xml files to replace version 1.0.0-SNAPSHOT to 1.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2679) [Glossary] Derive category's qualifiedName using hierarchy
[ https://issues.apache.org/jira/browse/ATLAS-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2679. - Resolution: Fixed Fix Version/s: 1.0.0 Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/66f8ae16 - branch-1.0: http://git-wip-us.apache.org/repos/asf/atlas/commit/65e3a114 > [Glossary] Derive category's qualifiedName using hierarchy > -- > > Key: ATLAS-2679 > URL: https://issues.apache.org/jira/browse/ATLAS-2679 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > > Currently the qualifiedName is derived using displayName and Glossary's > qualifiedName. > > In this patch, the qualifiedName is derived from it's Hierarchy and any > changes in the hierarchy itself will trigger a cascaded update of all > children. > > E.g. Cat1 is parent category, Cat2 is child category > > Derived qualfiedName of Cat2 = Cat2.Cat1@ > > The following actions trigger a cascaded update of the children categories > > # Change of anchor > # Change of Parent > # Removal of children from a parent (similar to #2) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-2671) Dependency version upgrade to latest stable release
[ https://issues.apache.org/jira/browse/ATLAS-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476848#comment-16476848 ] Madhan Neethiraj edited comment on ATLAS-2671 at 5/16/18 5:15 AM: -- Committed to following branches: master: http://git-wip-us.apache.org/repos/asf/atlas/commit/f65aecee branch-1.0: http://git-wip-us.apache.org/repos/asf/atlas/commit/05d50359 was (Author: apoorvnaik): Committed on master: https://git-wip-us.apache.org/repos/asf?p=atlas.git;a=commit;h=f65aeceeb97156ff9e26f1352a6da4100845cb7a > Dependency version upgrade to latest stable release > --- > > Key: ATLAS-2671 > URL: https://issues.apache.org/jira/browse/ATLAS-2671 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-ATLAS-2671-Dependency-upgrades.patch > > > Spring, Jackson and Lucene upgrades -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1578) Problem with Firefox UI : While creating/editing entity in UI ,value to be selected from a drop down list gets auto selected.
[ https://issues.apache.org/jira/browse/ATLAS-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1578: Fix Version/s: 1.0.0 > Problem with Firefox UI : While creating/editing entity in UI ,value to be > selected from a drop down list gets auto selected. > - > > Key: ATLAS-1578 > URL: https://issues.apache.org/jira/browse/ATLAS-1578 > Project: Atlas > Issue Type: Sub-task > Components: atlas-webui > Environment: Firefox 45.0 >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Minor > Fix For: 0.8.1, 1.0.0 > > > When creating hbase_column_family , hbase_table is one of its attributes > which is a drop down list of all hbase_tables. Even before providing the > hbase_table, an hbase_table entity is pre selected. This preselection doesn't > happen on Chrome or Safari. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1605) Edit Entity in UI : Update button is not enabled when updating attribute of type date
[ https://issues.apache.org/jira/browse/ATLAS-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1605: Fix Version/s: 0.8-incubating > Edit Entity in UI : Update button is not enabled when updating attribute of > type date > - > > Key: ATLAS-1605 > URL: https://issues.apache.org/jira/browse/ATLAS-1605 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Assignee: Kalyani Kashikar >Priority: Major > Fix For: 0.8-incubating > > Attachments: ATLAS-1605.1.patch, ATLAS-1605.patch > > > On editing attributes of hdfs_path like CreateTime , ModifiedTime which are > of type date , Update button is not enabled. This happens for all entity > types which have attributes of type date. Editing other types enables the > Update button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1612) Regression: DSL search using a non-unique attribute of user-defined types results in empty response
[
https://issues.apache.org/jira/browse/ATLAS-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-1612.
-
Resolution: Not A Problem
Fix Version/s: (was: trunk)
> Regression: DSL search using a non-unique attribute of user-defined types
> results in empty response
> ---
>
> Key: ATLAS-1612
> URL: https://issues.apache.org/jira/browse/ATLAS-1612
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: trunk, 0.8-incubating
>Reporter: Ayub Pathan
>Assignee: Vimal Sharma
>Priority: Blocker
> Fix For: 0.8-incubating
>
>
> Steps to repro:
> 1. Create a user defined type like below
> {noformat}
> {
> "enumTypes":[
> ],
> "structTypes":[
> ],
> "traitTypes":[
> ],
> "classTypes":[
> {
> "superTypes":[
> ],
>
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.ClassType",
> "typeName":"sample",
> "typeDescription":null,
> "typeVersion":"1.0",
> "attributeDefinitions":[
> {
> "name":"name",
> "dataTypeName":"string",
> "multiplicity":"required",
> "isComposite":false,
> "isUnique":false,
> "isIndexable":false,
> "reverseAttributeName":null
> }
> ]
> }
> ]
> }
> {noformat}
> 2. create an entity of above type
> {noformat}
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-16993187400044476",
> "version":0,
> "typeName":"sample",
> "state":"ACTIVE"
> },
> "typeName":"sample",
> "values":{
> "name":"simple_column"
> },
> "traitNames":[
> ],
> "traits":{
> },
> "systemAttributes":{
> "createdBy":null,
> "modifiedBy":null,
> "createdTime":null,
> "modifiedTime":null
> }
> }
> {noformat}
> 3. Now perform a dsl search using below query - "query": "sample where name =
> \"sample_column\"",
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-1610) Regression: GUID order in the entity create response is not returned in the expected order(i.e; creation order).
[
https://issues.apache.org/jira/browse/ATLAS-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-1610:
Fix Version/s: (was: trunk)
> Regression: GUID order in the entity create response is not returned in the
> expected order(i.e; creation order).
>
>
> Key: ATLAS-1610
> URL: https://issues.apache.org/jira/browse/ATLAS-1610
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: trunk, 0.8-incubating
>Reporter: Ayub Pathan
>Assignee: Sarath Subramanian
>Priority: Blocker
> Fix For: 0.8-incubating
>
>
> Steps to repro:
> 1. create below entity with two reference entities in it using /entities POST
> rest call
> {noformat}
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-16989787630260306",
> "version":0,
> "typeName":"ComplexEntityTestTable9u3zoazpsj",
> "state":"ACTIVE"
> },
> "typeName":"ComplexEntityTestTable9u3zoazpsj",
> "values":{
> "columns":[
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-16989787630260309",
> "version":0,
> "typeName":"ComplexEntityTestColumn2iv0d87lrb",
> "state":"ACTIVE"
> },
> "typeName":"ComplexEntityTestColumn2iv0d87lrb",
> "values":{
> "name":"column14vqfo3ocvf13"
> },
> "traitNames":[
> ],
> "traits":{
> },
> "systemAttributes":{
> "createdBy":null,
> "modifiedBy":null,
> "createdTime":null,
> "modifiedTime":null
> }
> },
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-16989787630260308",
> "version":0,
> "typeName":"ComplexEntityTestColumn2iv0d87lrb",
> "state":"ACTIVE"
> },
> "typeName":"ComplexEntityTestColumn2iv0d87lrb",
> "values":{
> "name":"column2dofzvezzh12123"
> },
> "traitNames":[
> ],
> "traits":{
> },
> "systemAttributes":{
> "createdBy":null,
> "modifiedBy":null,
> "createdTime":null,
> "modifiedTime":null
> }
> }
> ],
> "db":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"bad8c2eb-050e-4dbc-b219-92a5fe850fef",
> "version":0,
> "typeName":"ComplexEntityTestDB2dnlau6arq",
> "state":"ACTIVE"
> },
> "name":"createComplexEntityTablebllw6t3u1x123"
> },
> "traitNames":[
> ],
> "traits":{
> },
> "systemAttributes":{
> "createdBy":null,
> "modifiedBy":null,
> "createdTime":null,
> "modifiedTime":null
> }
> }
> {noformat}
> 2. Check the response for this POST request. Ideally first the reference
> entity GUID should be present in entities.created[] array.
> For example:
> IF table1 is created with col1 and col2 then the response object should
> contain entities.created["col1.GUID", "col2.GUID", "table1.GUID"] but the
> actual response contains in reverse order. *This breaks the exisitng behavior
> and hence regression*
> {noformat}
> {
> "requestId": "pool-2-thread-10 - c79079a0-db10-4fa1-8eaa-b088993b23b0",
> "entities": {
> "created": [
> "6797d3c6-ee99-4d97-8fa8-b11d37fe4801",
> "9cc65c33-ab3a-4de3-8b27-3684b6580171",
> "9a29b72c-fb6a-4f54-b4fe-f306da87e383"
> ]
> },
> "definition": {
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id": {
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "6797d3c6-ee99-4d97-8fa8-b11d37fe4801",
> "version": 0,
> "typeName": "ComplexEntityTestTable9u3zoazpsj",
> "state": "ACTIVE"
> },
> "typeName": "ComplexEntityTestTable9u3zoazpsj",
> "values": {
> "columns": [
> {
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id": {
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "9cc65c33-ab3a-4de3-8b27-3684b6580171",
> "version": 0,
> "typeName": "ComplexEntityTestColumn2iv0d87lrb",
>
[jira] [Reopened] (ATLAS-1612) Regression: DSL search using a non-unique attribute of user-defined types results in empty response
[
https://issues.apache.org/jira/browse/ATLAS-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj reopened ATLAS-1612:
-
> Regression: DSL search using a non-unique attribute of user-defined types
> results in empty response
> ---
>
> Key: ATLAS-1612
> URL: https://issues.apache.org/jira/browse/ATLAS-1612
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: trunk, 0.8-incubating
>Reporter: Ayub Pathan
>Assignee: Vimal Sharma
>Priority: Blocker
> Fix For: 0.8-incubating
>
>
> Steps to repro:
> 1. Create a user defined type like below
> {noformat}
> {
> "enumTypes":[
> ],
> "structTypes":[
> ],
> "traitTypes":[
> ],
> "classTypes":[
> {
> "superTypes":[
> ],
>
> "hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.ClassType",
> "typeName":"sample",
> "typeDescription":null,
> "typeVersion":"1.0",
> "attributeDefinitions":[
> {
> "name":"name",
> "dataTypeName":"string",
> "multiplicity":"required",
> "isComposite":false,
> "isUnique":false,
> "isIndexable":false,
> "reverseAttributeName":null
> }
> ]
> }
> ]
> }
> {noformat}
> 2. create an entity of above type
> {noformat}
> {
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-16993187400044476",
> "version":0,
> "typeName":"sample",
> "state":"ACTIVE"
> },
> "typeName":"sample",
> "values":{
> "name":"simple_column"
> },
> "traitNames":[
> ],
> "traits":{
> },
> "systemAttributes":{
> "createdBy":null,
> "modifiedBy":null,
> "createdTime":null,
> "modifiedTime":null
> }
> }
> {noformat}
> 3. Now perform a dsl search using below query - "query": "sample where name =
> \"sample_column\"",
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-1651) Change master version to 0.9-incubating
[ https://issues.apache.org/jira/browse/ATLAS-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1651: Fix Version/s: (was: trunk) 1.0.0-alpha > Change master version to 0.9-incubating > --- > > Key: ATLAS-1651 > URL: https://issues.apache.org/jira/browse/ATLAS-1651 > Project: Atlas > Issue Type: Sub-task >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 1.0.0-alpha > > Attachments: ATLAS-1651.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1641) UI Regression : Clicking on "Add Tag" button in the Search result table in index.html page doesn't open up the Add Tag window.
[ https://issues.apache.org/jira/browse/ATLAS-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1641: Fix Version/s: 0.8-incubating > UI Regression : Clicking on "Add Tag" button in the Search result table in > index.html page doesn't open up the Add Tag window. > -- > > Key: ATLAS-1641 > URL: https://issues.apache.org/jira/browse/ATLAS-1641 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Critical > Fix For: 0.8-incubating > > > Clicking on "Add Tag" button corresponding to any entity in the Search result > table in index.html page doesn't open up the Add Tag window. Network tab in > the browser shows no action or query being fired on clicking the button. > But in the detailsPage of entity , Add tag button is clickable and opens up > the Add Tag Window. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ATLAS-1662) New governance action API to support Ranger tags from v2 glossary
[
https://issues.apache.org/jira/browse/ATLAS-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj reopened ATLAS-1662:
-
> New governance action API to support Ranger tags from v2 glossary
> -
>
> Key: ATLAS-1662
> URL: https://issues.apache.org/jira/browse/ATLAS-1662
> Project: Atlas
> Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>
> Today Ranger obtains classification ("tags") from atlas via a tagsync process
> which
> - looks at interesting types
> - going through entities of those types
> - pulling traits/trait instances to get tags
> - formulating these into a map
> - persisting in ranger
> ATLAS-1410 proposes a new enterprise ready glossary which allows for a more
> sophticated approach to classification.
> To support this we will develop a new consumer-centric ("omas") API to
> support Ranger or other enforcement engines . The implementation behind the
> first function of this API will navigate the new glossary structure to
> present ranger with the simplified entity:classification map it needs rather
> than the more elaborate structure of the glossary.
> A new ranger tagsync process will then use this api to push tags into ranger
> without needing changes
> More generally this API will support anything an enforcement engine needs
> more detail to follow
> (Note to observers: could you assign this one to me or grant permission)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-1734) Import API: Add Support to Update Attributes of Existing Types During Import
[ https://issues.apache.org/jira/browse/ATLAS-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1734: Affects Version/s: (was: trunk) Fix Version/s: (was: trunk) 0.8.1 1.0.0 Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/8101883c - branch-0.8: http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/f62f077f > Import API: Add Support to Update Attributes of Existing Types During Import > > > Key: ATLAS-1734 > URL: https://issues.apache.org/jira/browse/ATLAS-1734 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Labels: patch > Fix For: 0.8.1, 1.0.0 > > Attachments: > ATLAS-1734-Import-with-additional-attribute-processi.patch > > > *Background* > Existing version of Import API allows for importing types that are not > already present in the system being imported in. This causes import to fail > in the cases where the data being imported happens to have the additional > attribute. > *Solution* > During import, existing types are checked to determine if the types being > imported have additional attributes. If additional attributes exist, then the > existing type is updated with the new attributes. The import then proceeds. > *Impact Assessment* > - Import API: > -- Type import: Additional capability (mentioned above). > -- Entity creation and processing: No impact. > - Export API: No impact. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1662) New governance action API to support Ranger tags from v2 glossary
[
https://issues.apache.org/jira/browse/ATLAS-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-1662.
-
Resolution: Duplicate
> New governance action API to support Ranger tags from v2 glossary
> -
>
> Key: ATLAS-1662
> URL: https://issues.apache.org/jira/browse/ATLAS-1662
> Project: Atlas
> Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
>
> Today Ranger obtains classification ("tags") from atlas via a tagsync process
> which
> - looks at interesting types
> - going through entities of those types
> - pulling traits/trait instances to get tags
> - formulating these into a map
> - persisting in ranger
> ATLAS-1410 proposes a new enterprise ready glossary which allows for a more
> sophticated approach to classification.
> To support this we will develop a new consumer-centric ("omas") API to
> support Ranger or other enforcement engines . The implementation behind the
> first function of this API will navigate the new glossary structure to
> present ranger with the simplified entity:classification map it needs rather
> than the more elaborate structure of the glossary.
> A new ranger tagsync process will then use this api to push tags into ranger
> without needing changes
> More generally this API will support anything an enforcement engine needs
> more detail to follow
> (Note to observers: could you assign this one to me or grant permission)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-1778) Incorrect error code returned in V2 APIs when updating an entity with invalid values using PUT/POST
[
https://issues.apache.org/jira/browse/ATLAS-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-1778:
Fix Version/s: (was: trunk)
> Incorrect error code returned in V2 APIs when updating an entity with invalid
> values using PUT/POST
> ---
>
> Key: ATLAS-1778
> URL: https://issues.apache.org/jira/browse/ATLAS-1778
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8-incubating, 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 0.8.1
>
> Attachments:
> 0001-ErrorCode-fixes-and-bad-request-when-invalid-attribu.patch
>
>
> Entity Update using PUT /POST with wrong values for attributes throws 404 Not
> Found exception . Expected is 400 Bad Request .
> {code}
> curl -v -u admin:admin -H "Content-Type: application/json" -d @entity.json
> -X POST
> "http://ctr-e133-1493418528701-6996-01-06.hwx.site:21000/api/atlas/v2/entity;
> * Trying 172.27.14.75...
> * Connected to ctr-e133-1493418528701-6996-01-06.hwx.site (172.27.14.75)
> port 21000 (#0)
> * Server auth using Basic with user 'admin'
> > POST /api/atlas/v2/entity HTTP/1.1
> > Host: ctr-e133-1493418528701-6996-01-06.hwx.site:21000
> > Authorization: Basic YWRtaW46YWRtaW4=
> > User-Agent: curl/7.43.0
> > Accept: */*
> > Content-Type: application/json
> > Content-Length: 937
> >
> * upload completely sent off: 937 out of 937 bytes
> < HTTP/1.1 404 Not Found
> < Date: Fri, 05 May 2017 06:09:21 GMT
> < Set-Cookie: ATLASSESSIONID=1e65za9f72n3n7dcxp6bsgf2o;Path=/;HttpOnly
> < Expires: Thu, 01 Jan 1970 00:00:00 GMT
> < X-Frame-Options: DENY
> < Content-Type: application/json; charset=UTF-8
> < Transfer-Encoding: chunked
> < Server: Jetty(9.2.12.v20150709)
> <
> * Connection #0 to host ctr-e133-1493418528701-6996-01-06.hwx.site left
> intact
> {"errorCode":"ATLAS-404-00-007","errorMessage":"Invalid instance
> creation/updation parameters passed : entity_type_VNsAA.type_date=str:
> invalid value for type date"}
> {code}
> *V1 APIs return 400 Bad Request*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-1788) UI : Wildcard search with "?" throws exception in basic search
[
https://issues.apache.org/jira/browse/ATLAS-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-1788:
Fix Version/s: 0.8.1
1.0.0
> UI : Wildcard search with "?" throws exception in basic search
> --
>
> Key: ATLAS-1788
> URL: https://issues.apache.org/jira/browse/ATLAS-1788
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: trunk, 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 0.8.1, 1.0.0
>
> Attachments: wildcard_search.txt
>
>
> Wildcard search with "?" throws 500 internal error.
> Example :
> Basic search :
> type name : kafka_topic
> query : kakfa_topic_iAEz?
> throws 500 Internal server error .
> The corresponding query fired is
> {code}
> http://172.27.19.74:21000/api/atlas/v2/search?limit=25=kakfa_topic_iAEz
> {code}
> if query is "kafka_topic_?AEzb"
> corresponding query fired is :
> {code}
> http://172.27.19.74:21000/api/atlas/v2/search?limit=25=kafka_topic_
> {code}
> Note : content after "?" is ignored and query is not formed correctly (basic
> keyword is missed)
> The following curl command runs fine returns 200 Ok with correct results.
> {code}
> curl -u admin:admin -X GET
> "http://172.27.19.74:21000/api/atlas/v2/search/basic?limit=25=true=kakfa_topic_iAEz?=kafka_topic;
> {code}
> Attached the WebApplication exception thrown while making the query.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-1763) UI : Atlas lands in the page of Deleted tag (the only tag) on clicking TAGS tab
[ https://issues.apache.org/jira/browse/ATLAS-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1763: Fix Version/s: 0.8.1 1.0.0 > UI : Atlas lands in the page of Deleted tag (the only tag) on clicking TAGS > tab > > > Key: ATLAS-1763 > URL: https://issues.apache.org/jira/browse/ATLAS-1763 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Trivial > Fix For: 0.8.1, 1.0.0 > > > 1. Created tag tag1 > 2. Clicked on TAGS tab which landed in > http://localhost:21000/index.html#!/tag/tagAttribute/tag1 > 3. Deleted the tag through REST. > 4. Clicked on the TAGS tab. The TAGS tab listed tag1 . But on disabling cache > , tag1 is removed. > 5.But Atlas lands in > http://localhost:21000/index.html#!/tag/tagAttribute/tag1 which throws 404 > exception while clicking Tags tab . > On opening Atlas in another incognito window , this issue is not seen . Atlas > possibly caches tag1 which lands in /tag/tagAttribute/tag1 and causes issue. > When there are 1 or more ACTIVE tags , this issue is not seen as it lands in > /tag/tagAttribute/. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1897) UI - Render HTML element based on attribute data-type while assigning Tag to entity.
[ https://issues.apache.org/jira/browse/ATLAS-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1897: Fix Version/s: 0.8.1 1.0.0 Component/s: atlas-webui > UI - Render HTML element based on attribute data-type while assigning Tag to > entity. > > > Key: ATLAS-1897 > URL: https://issues.apache.org/jira/browse/ATLAS-1897 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar >Priority: Major > Fix For: 0.8.1, 1.0.0 > > Attachments: ATLAS-1897.patch > > > While assigning tag to entity, It allows inputs based on attribute data-type -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1899) A correction identified during ATLAS-1891 review ended up not getting committed.
[ https://issues.apache.org/jira/browse/ATLAS-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1899: Fix Version/s: 1.0.0 Component/s: atlas-core Committed to master: http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/617bc25e > A correction identified during ATLAS-1891 review ended up not getting > committed. > - > > Key: ATLAS-1899 > URL: https://issues.apache.org/jira/browse/ATLAS-1899 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: David Radley >Assignee: David Radley >Priority: Major > Fix For: 1.0.0 > > > A correction identified during ATLAS-1891 ended up not getting committed. The > existing logic is > valid but the code could be cleaner. I am submitting the cleaner version of > the code as I have tested it -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1894) UI : Search using entity and trait attributes
[ https://issues.apache.org/jira/browse/ATLAS-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1894: Fix Version/s: 0.8.1 1.0.0 Component/s: atlas-webui > UI : Search using entity and trait attributes > - > > Key: ATLAS-1894 > URL: https://issues.apache.org/jira/browse/ATLAS-1894 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8.1, 1.0.0 > > Attachments: ATLAS-1894.1.patch, ATLAS-1894.2.patch, > ATLAS-1894.3.patch, ATLAS-1894.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1892) Implement logic to create relationship attributes in AtlasEntityType
[ https://issues.apache.org/jira/browse/ATLAS-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1892: Fix Version/s: 1.0.0 > Implement logic to create relationship attributes in AtlasEntityType > > > Key: ATLAS-1892 > URL: https://issues.apache.org/jira/browse/ATLAS-1892 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: trunk, 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-1856.4.patch > > > When a new relationshipDef is created, relation attributes needs to be > populated in AtlasEntityType during resolveReference stage. > This JIRA also adds UT and IT and addresses review comments in > https://reviews.apache.org/r/59769/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1892) Implement logic to create relationship attributes in AtlasEntityType
[ https://issues.apache.org/jira/browse/ATLAS-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-1892: Affects Version/s: (was: trunk) > Implement logic to create relationship attributes in AtlasEntityType > > > Key: ATLAS-1892 > URL: https://issues.apache.org/jira/browse/ATLAS-1892 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-1856.4.patch > > > When a new relationshipDef is created, relation attributes needs to be > populated in AtlasEntityType during resolveReference stage. > This JIRA also adds UT and IT and addresses review comments in > https://reviews.apache.org/r/59769/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2703) [Glossary] Term relation edge shouldn't be deleted when entity is deleted
[ https://issues.apache.org/jira/browse/ATLAS-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481263#comment-16481263 ] Madhan Neethiraj commented on ATLAS-2703: - +1 for the patch. Thanks [~apoorvnaik]! > [Glossary] Term relation edge shouldn't be deleted when entity is deleted > - > > Key: ATLAS-2703 > URL: https://issues.apache.org/jira/browse/ATLAS-2703 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.0.0 > > Attachments: > 0001-ATLAS-2703-Term-to-Referenceable-edge-shouldn-t-be-a.patch > > > With a recent hard delete change all internal relationship edges were > deleted, when an entity is deleted the desired behavior is to mark the > relation as DELETED (soft delete). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2708) AWS S3 data lake typedefs for Atlas
[
https://issues.apache.org/jira/browse/ATLAS-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16507520#comment-16507520
]
Madhan Neethiraj commented on ATLAS-2708:
-
[~barbara] - thanks for adding models for S3 types. Couple of comments:
{noformat}
AWSTag, AWSCloudWatchMetric, AWSS3BucketLifeCycleRule: are these really
datasets? Perhaps Referenceable should be the only super-type?
{noformat}
{noformat}
AWSS3PseudoDir, AWSS3Bucket: both DataSet and Asset as listed as super-types.
Given DataSet already has has Asset as its super-type, it is enough to list
only DataSet as the super-type.
{noformat}
> AWS S3 data lake typedefs for Atlas
> ---
>
> Key: ATLAS-2708
> URL: https://issues.apache.org/jira/browse/ATLAS-2708
> Project: Atlas
> Issue Type: New Feature
> Components: atlas-core
>Reporter: Barbara Eckman
>Assignee: Barbara Eckman
>Priority: Critical
> Attachments: all_datalake_types.json
>
>
> Currently the base types in Atlas do not include AWS data lake objects. It
> would be nice to add typedefs for AWS data lake objects (buckets and
> pseudo-directories) and lineage processes that move the data from another
> source (e.g., kafka topic) to the data lake. For example:
> * AWSS3PseudoDir type represents the pseudo-directory “prefix” of objects in
> an S3 bucket. For example, in the case of an object with key
> “myWork/Development/Projects1.xls”, “myWork/Development” is the
> pseudo-directory. It supports:
> ** Array of avro schemas that are associated with the data in the
> pseudo-directory (based on Avro schema extensions outlined in ATLAS-2694)
> ** what type of data it contains, e.g., avro, json, unstructured
> ** time of creation
> * AWSS3BucketLifeCycleRule type represents a rule specifying a transition of
> the data in a bucket to a storageClass after a specific time interval, or
> expiration. For example, transition to GLACIER after 60 days, or expire
> (i.e. be deleted) after 90 days:
> ** ruleType (e.g., transition or expiration)
> ** time interval in days before rule is executed
> ** storageClass to which the data is transitioned (null if ruleType is
> expiration)
> * AWSTag type represents a tag-value pair created by the user and associated
> with an AWS object.
> ** tag
> ** value
> * AWSCloudWatchMetric type represents a storage or request metric that is
> monitored by AWS CloudWatch and can be configured for a bucket
> ** metricName, for example, “AllRequests”, “GetRequests”,
> TotalRequestLatency, BucketSizeBytes
> ** scope: null if entire bucket; otherwise, the prefixes/tags that filter or
> limit the monitoring of the metric.
> * AWSS3Bucket type represents a bucket in an S3 instance. It supports:
> ** Array of AWSS3PseudoDirectories that are associated with objects stored
> in the bucket
> ** AWS region
> ** IsEncrypted (boolean)
> ** encryptionType, e.g., AES-256
> ** S3AccessPolicy, a JSON object expressing access policies, eg GetObject,
> PutObject
> ** time of creation
> ** Array of AWSS3BucketLifeCycleRules that are associated with the bucket
> ** Array of AWSS3CloudWatchMetrics that are associated with the bucket or
> its tags or prefixes
> ** Array of AWSTags that are associated with the bucket
> * Generic dataset2Dataset process to represent movement of data from one
> dataset to another. It supports:
> ** array of transforms performed by the process
> ** map of tag/value pairs representing configurationParameters of the process
> ** inputs and outputs are arrays of dataset objects, e.g., kafka topic and
> S3 pseudo-directory.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-641) Lineage for a view created from a view seems to be confusing(from user's perspective).
[
https://issues.apache.org/jira/browse/ATLAS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-641:
---
Attachment: ATLAS-641.patch
> Lineage for a view created from a view seems to be confusing(from user's
> perspective).
> --
>
> Key: ATLAS-641
> URL: https://issues.apache.org/jira/browse/ATLAS-641
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8.1, 0.8.2, 1.0.0
>Reporter: Ayub Pathan
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 0.8.3, 1.1.0, 2.0.0
>
> Attachments: ATLAS-641.patch
>
>
> Lineage for a table created from the view seems to be confusing(from user's
> perspective).
> Steps to reproduce:
> {noformat}
> 0: jdbc:hive2://localhost:1/default>
> 0: jdbc:hive2://localhost:1/default> create table src (x int, y int, s
> string);
> No rows affected (0.384 seconds)
> 0: jdbc:hive2://localhost:1/default> create view view1 as select * from
> src;
> No rows affected (0.225 seconds)
> 0: jdbc:hive2://localhost:1/default> create table view_table as select *
> from view1;
> INFO : Number of reduce tasks is set to 0 since there's no reduce operator
> INFO : number of splits:1
> INFO : Submitting tokens for job: job_local1883260823_0021
> INFO : The url to track the job: http://localhost:8080/
> INFO : Job running in-process (local Hadoop)
> INFO : 2016-04-06 18:15:02,538 Stage-1 map = 100%, reduce = 0%
> INFO : Ended Job = job_local1883260823_0021
> INFO : Stage-4 is selected by condition resolver.
> INFO : Stage-3 is filtered out by condition resolver.
> INFO : Stage-5 is filtered out by condition resolver.
> INFO : Moving data to:
> hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2016-04-06_18-14-59_156_3909183228338665119-12/-ext-10001
> from
> hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2016-04-06_18-14-59_156_3909183228338665119-12/-ext-10003
> INFO : Moving data to: hdfs://localhost:9000/user/hive/warehouse/view_table
> from
> hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2016-04-06_18-14-59_156_3909183228338665119-12/-ext-10001
> INFO : Table default.view_table stats: [numFiles=1, numRows=0, totalSize=0,
> rawDataSize=0]
> No rows affected (3.8 seconds)
> 0: jdbc:hive2://localhost:1/default> alter view view1 as select * from t2;
> No rows affected (0.602 seconds)
> 0: jdbc:hive2://localhost:1/default>
> {noformat}
> Check the lineage of the resultant table(view_table).
> Link showing confusing lineage:
> https://monosnap.com/file/qaYZcJRQnNX5BsyM12hkryv70RZK1I
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (ATLAS-641) Lineage for a view created from a view seems to be confusing(from user's perspective).
[
https://issues.apache.org/jira/browse/ATLAS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj reassigned ATLAS-641:
--
Assignee: Madhan Neethiraj
> Lineage for a view created from a view seems to be confusing(from user's
> perspective).
> --
>
> Key: ATLAS-641
> URL: https://issues.apache.org/jira/browse/ATLAS-641
> Project: Atlas
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Pathan
>Assignee: Madhan Neethiraj
>Priority: Major
>
> Lineage for a table created from the view seems to be confusing(from user's
> perspective).
> Steps to reproduce:
> {noformat}
> 0: jdbc:hive2://localhost:1/default>
> 0: jdbc:hive2://localhost:1/default> create table src (x int, y int, s
> string);
> No rows affected (0.384 seconds)
> 0: jdbc:hive2://localhost:1/default> create view view1 as select * from
> src;
> No rows affected (0.225 seconds)
> 0: jdbc:hive2://localhost:1/default> create table view_table as select *
> from view1;
> INFO : Number of reduce tasks is set to 0 since there's no reduce operator
> INFO : number of splits:1
> INFO : Submitting tokens for job: job_local1883260823_0021
> INFO : The url to track the job: http://localhost:8080/
> INFO : Job running in-process (local Hadoop)
> INFO : 2016-04-06 18:15:02,538 Stage-1 map = 100%, reduce = 0%
> INFO : Ended Job = job_local1883260823_0021
> INFO : Stage-4 is selected by condition resolver.
> INFO : Stage-3 is filtered out by condition resolver.
> INFO : Stage-5 is filtered out by condition resolver.
> INFO : Moving data to:
> hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2016-04-06_18-14-59_156_3909183228338665119-12/-ext-10001
> from
> hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2016-04-06_18-14-59_156_3909183228338665119-12/-ext-10003
> INFO : Moving data to: hdfs://localhost:9000/user/hive/warehouse/view_table
> from
> hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2016-04-06_18-14-59_156_3909183228338665119-12/-ext-10001
> INFO : Table default.view_table stats: [numFiles=1, numRows=0, totalSize=0,
> rawDataSize=0]
> No rows affected (3.8 seconds)
> 0: jdbc:hive2://localhost:1/default> alter view view1 as select * from t2;
> No rows affected (0.602 seconds)
> 0: jdbc:hive2://localhost:1/default>
> {noformat}
> Check the lineage of the resultant table(view_table).
> Link showing confusing lineage:
> https://monosnap.com/file/qaYZcJRQnNX5BsyM12hkryv70RZK1I
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ATLAS-641) Lineage for a view created from a view seems to be confusing(from user's perspective).
[
https://issues.apache.org/jira/browse/ATLAS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16514618#comment-16514618
]
Madhan Neethiraj commented on ATLAS-641:
Pre-commit test run:
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/477/
> Lineage for a view created from a view seems to be confusing(from user's
> perspective).
> --
>
> Key: ATLAS-641
> URL: https://issues.apache.org/jira/browse/ATLAS-641
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8.1, 0.8.2, 1.0.0
>Reporter: Ayub Pathan
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 0.8.3, 1.1.0, 2.0.0
>
> Attachments: ATLAS-641.patch
>
>
> Lineage for a table created from the view seems to be confusing(from user's
> perspective).
> Steps to reproduce:
> {noformat}
> 0: jdbc:hive2://localhost:1/default>
> 0: jdbc:hive2://localhost:1/default> create table src (x int, y int, s
> string);
> No rows affected (0.384 seconds)
> 0: jdbc:hive2://localhost:1/default> create view view1 as select * from
> src;
> No rows affected (0.225 seconds)
> 0: jdbc:hive2://localhost:1/default> create table view_table as select *
> from view1;
> INFO : Number of reduce tasks is set to 0 since there's no reduce operator
> INFO : number of splits:1
> INFO : Submitting tokens for job: job_local1883260823_0021
> INFO : The url to track the job: http://localhost:8080/
> INFO : Job running in-process (local Hadoop)
> INFO : 2016-04-06 18:15:02,538 Stage-1 map = 100%, reduce = 0%
> INFO : Ended Job = job_local1883260823_0021
> INFO : Stage-4 is selected by condition resolver.
> INFO : Stage-3 is filtered out by condition resolver.
> INFO : Stage-5 is filtered out by condition resolver.
> INFO : Moving data to:
> hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2016-04-06_18-14-59_156_3909183228338665119-12/-ext-10001
> from
> hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2016-04-06_18-14-59_156_3909183228338665119-12/-ext-10003
> INFO : Moving data to: hdfs://localhost:9000/user/hive/warehouse/view_table
> from
> hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2016-04-06_18-14-59_156_3909183228338665119-12/-ext-10001
> INFO : Table default.view_table stats: [numFiles=1, numRows=0, totalSize=0,
> rawDataSize=0]
> No rows affected (3.8 seconds)
> 0: jdbc:hive2://localhost:1/default> alter view view1 as select * from t2;
> No rows affected (0.602 seconds)
> 0: jdbc:hive2://localhost:1/default>
> {noformat}
> Check the lineage of the resultant table(view_table).
> Link showing confusing lineage:
> https://monosnap.com/file/qaYZcJRQnNX5BsyM12hkryv70RZK1I
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-641) Lineage for a view created from a view seems to be confusing(from user's perspective).
[
https://issues.apache.org/jira/browse/ATLAS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-641:
---
Attachment: (was: ATLAS-641.patch)
> Lineage for a view created from a view seems to be confusing(from user's
> perspective).
> --
>
> Key: ATLAS-641
> URL: https://issues.apache.org/jira/browse/ATLAS-641
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8.1, 0.8.2, 1.0.0
>Reporter: Ayub Pathan
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 0.8.3, 1.1.0, 2.0.0
>
> Attachments: ATLAS-641.patch
>
>
> Lineage for a table created from the view seems to be confusing(from user's
> perspective).
> Steps to reproduce:
> {noformat}
> 0: jdbc:hive2://localhost:1/default>
> 0: jdbc:hive2://localhost:1/default> create table src (x int, y int, s
> string);
> No rows affected (0.384 seconds)
> 0: jdbc:hive2://localhost:1/default> create view view1 as select * from
> src;
> No rows affected (0.225 seconds)
> 0: jdbc:hive2://localhost:1/default> create table view_table as select *
> from view1;
> INFO : Number of reduce tasks is set to 0 since there's no reduce operator
> INFO : number of splits:1
> INFO : Submitting tokens for job: job_local1883260823_0021
> INFO : The url to track the job: http://localhost:8080/
> INFO : Job running in-process (local Hadoop)
> INFO : 2016-04-06 18:15:02,538 Stage-1 map = 100%, reduce = 0%
> INFO : Ended Job = job_local1883260823_0021
> INFO : Stage-4 is selected by condition resolver.
> INFO : Stage-3 is filtered out by condition resolver.
> INFO : Stage-5 is filtered out by condition resolver.
> INFO : Moving data to:
> hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2016-04-06_18-14-59_156_3909183228338665119-12/-ext-10001
> from
> hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2016-04-06_18-14-59_156_3909183228338665119-12/-ext-10003
> INFO : Moving data to: hdfs://localhost:9000/user/hive/warehouse/view_table
> from
> hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2016-04-06_18-14-59_156_3909183228338665119-12/-ext-10001
> INFO : Table default.view_table stats: [numFiles=1, numRows=0, totalSize=0,
> rawDataSize=0]
> No rows affected (3.8 seconds)
> 0: jdbc:hive2://localhost:1/default> alter view view1 as select * from t2;
> No rows affected (0.602 seconds)
> 0: jdbc:hive2://localhost:1/default>
> {noformat}
> Check the lineage of the resultant table(view_table).
> Link showing confusing lineage:
> https://monosnap.com/file/qaYZcJRQnNX5BsyM12hkryv70RZK1I
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-641) Lineage for a view created from a view seems to be confusing(from user's perspective).
[
https://issues.apache.org/jira/browse/ATLAS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16514618#comment-16514618
]
Madhan Neethiraj edited comment on ATLAS-641 at 6/16/18 6:28 AM:
-
Pre-commit test run:
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/478
was (Author: madhan.neethiraj):
Pre-commit test run:
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/477/
> Lineage for a view created from a view seems to be confusing(from user's
> perspective).
> --
>
> Key: ATLAS-641
> URL: https://issues.apache.org/jira/browse/ATLAS-641
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8.1, 0.8.2, 1.0.0
>Reporter: Ayub Pathan
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 0.8.3, 1.1.0, 2.0.0
>
> Attachments: ATLAS-641.patch
>
>
> Lineage for a table created from the view seems to be confusing(from user's
> perspective).
> Steps to reproduce:
> {noformat}
> 0: jdbc:hive2://localhost:1/default>
> 0: jdbc:hive2://localhost:1/default> create table src (x int, y int, s
> string);
> No rows affected (0.384 seconds)
> 0: jdbc:hive2://localhost:1/default> create view view1 as select * from
> src;
> No rows affected (0.225 seconds)
> 0: jdbc:hive2://localhost:1/default> create table view_table as select *
> from view1;
> INFO : Number of reduce tasks is set to 0 since there's no reduce operator
> INFO : number of splits:1
> INFO : Submitting tokens for job: job_local1883260823_0021
> INFO : The url to track the job: http://localhost:8080/
> INFO : Job running in-process (local Hadoop)
> INFO : 2016-04-06 18:15:02,538 Stage-1 map = 100%, reduce = 0%
> INFO : Ended Job = job_local1883260823_0021
> INFO : Stage-4 is selected by condition resolver.
> INFO : Stage-3 is filtered out by condition resolver.
> INFO : Stage-5 is filtered out by condition resolver.
> INFO : Moving data to:
> hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2016-04-06_18-14-59_156_3909183228338665119-12/-ext-10001
> from
> hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2016-04-06_18-14-59_156_3909183228338665119-12/-ext-10003
> INFO : Moving data to: hdfs://localhost:9000/user/hive/warehouse/view_table
> from
> hdfs://localhost:9000/user/hive/warehouse/.hive-staging_hive_2016-04-06_18-14-59_156_3909183228338665119-12/-ext-10001
> INFO : Table default.view_table stats: [numFiles=1, numRows=0, totalSize=0,
> rawDataSize=0]
> No rows affected (3.8 seconds)
> 0: jdbc:hive2://localhost:1/default> alter view view1 as select * from t2;
> No rows affected (0.602 seconds)
> 0: jdbc:hive2://localhost:1/default>
> {noformat}
> Check the lineage of the resultant table(view_table).
> Link showing confusing lineage:
> https://monosnap.com/file/qaYZcJRQnNX5BsyM12hkryv70RZK1I
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ATLAS-2760) Update Hive hook to create AWS S3 entities for S3 path references
Madhan Neethiraj created ATLAS-2760: --- Summary: Update Hive hook to create AWS S3 entities for S3 path references Key: ATLAS-2760 URL: https://issues.apache.org/jira/browse/ATLAS-2760 Project: Atlas Issue Type: Bug Components: atlas-intg Reporter: Madhan Neethiraj Assignee: Madhan Neethiraj Entity types for AWS S3 have been added recently via ATLAS-2708. Hive hook should be updated to create AWS S3 entities for references to S3 paths - for example in 'insert overwrite' operation. This will capture the lineage between Hive tables and S3 paths. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2744) Update Atlas website with Downloads page to include Release notes
[ https://issues.apache.org/jira/browse/ATLAS-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512771#comment-16512771 ] Madhan Neethiraj commented on ATLAS-2744: - +1 for the website updates. Thanks [~abhib4]! > Update Atlas website with Downloads page to include Release notes > -- > > Key: ATLAS-2744 > URL: https://issues.apache.org/jira/browse/ATLAS-2744 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2744-3.patch, ATLAS-2744.patch, ATLAS-2744_1.patch > > > * I think it will be useful to rename 'Releases' menu as 'Downloads' and > link it to Downloads page. And this page will be updated to include Release > notes. > * Update all URLs to use https - which will result in red-rose for all links. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2744) Update Atlas website with Downloads page to include Release notes
[ https://issues.apache.org/jira/browse/ATLAS-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512806#comment-16512806 ] Madhan Neethiraj commented on ATLAS-2744: - Committed to following branches: - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/399468e6 - branch-1.0: http://git-wip-us.apache.org/repos/asf/atlas/commit/71ac8781 Updated Atlas web-site: http://git-wip-us.apache.org/repos/asf/atlas-website/commit/240841c2 > Update Atlas website with Downloads page to include Release notes > -- > > Key: ATLAS-2744 > URL: https://issues.apache.org/jira/browse/ATLAS-2744 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2744-3.patch, ATLAS-2744.patch, ATLAS-2744_1.patch > > > * I think it will be useful to rename 'Releases' menu as 'Downloads' and > link it to Downloads page. And this page will be updated to include Release > notes. > * Update all URLs to use https - which will result in red-rose for all links. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2757) Hive hook fails with NPE while processing column-rename on temporary table
Madhan Neethiraj created ATLAS-2757:
---
Summary: Hive hook fails with NPE while processing column-rename
on temporary table
Key: ATLAS-2757
URL: https://issues.apache.org/jira/browse/ATLAS-2757
Project: Atlas
Issue Type: Bug
Components: atlas-intg
Affects Versions: 1.0.0, 0.8.2
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj
Atlas hook for Hive fails with NPE while processing column-rename on temporary
table.
{noformat}
create temporary table testTempTable(id int, name string, dob date);
alter table testTempTable CHANGE name last_name string;
{noformat}
{noformat}
HiveHook.run(): failed to process operation ALTERTABLE_RENAMECOL
java.lang.NullPointerException: null
at java.util.ArrayList.(ArrayList.java:177) ~[?:1.8.0_112]
at
org.apache.atlas.hive.hook.events.AlterTableRenameCol.getNotificationMessages(AlterTableRenameCol.java:57)
at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:156)
at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:52)
at
org.apache.hadoop.hive.ql.HookRunner.invokeGeneralHook(HookRunner.java:296)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2757) Hive hook fails with NPE while processing column-rename on temporary table
[
https://issues.apache.org/jira/browse/ATLAS-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2757:
Reporter: Aswathy Chellammal Sreekumar (was: Madhan Neethiraj)
> Hive hook fails with NPE while processing column-rename on temporary table
> --
>
> Key: ATLAS-2757
> URL: https://issues.apache.org/jira/browse/ATLAS-2757
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 0.8.2, 1.0.0
>Reporter: Aswathy Chellammal Sreekumar
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 0.8.3, 1.1.0
>
> Attachments: ATLAS-2757.patch
>
>
> Atlas hook for Hive fails with NPE while processing column-rename on
> temporary table.
> {noformat}
> create temporary table testTempTable(id int, name string, dob date);
> alter table testTempTable CHANGE name last_name string;
> {noformat}
> {noformat}
> HiveHook.run(): failed to process operation ALTERTABLE_RENAMECOL
> java.lang.NullPointerException: null
> at java.util.ArrayList.(ArrayList.java:177) ~[?:1.8.0_112]
> at
> org.apache.atlas.hive.hook.events.AlterTableRenameCol.getNotificationMessages(AlterTableRenameCol.java:57)
> at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:156)
> at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:52)
> at
> org.apache.hadoop.hive.ql.HookRunner.invokeGeneralHook(HookRunner.java:296)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2757) Hive hook fails with NPE while processing column-rename on temporary table
[
https://issues.apache.org/jira/browse/ATLAS-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2757:
Fix Version/s: 2.0.0
> Hive hook fails with NPE while processing column-rename on temporary table
> --
>
> Key: ATLAS-2757
> URL: https://issues.apache.org/jira/browse/ATLAS-2757
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 0.8.2, 1.0.0
>Reporter: Aswathy Chellammal Sreekumar
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 0.8.3, 1.1.0, 2.0.0
>
> Attachments: ATLAS-2757.patch
>
>
> Atlas hook for Hive fails with NPE while processing column-rename on
> temporary table.
> {noformat}
> create temporary table testTempTable(id int, name string, dob date);
> alter table testTempTable CHANGE name last_name string;
> {noformat}
> {noformat}
> HiveHook.run(): failed to process operation ALTERTABLE_RENAMECOL
> java.lang.NullPointerException: null
> at java.util.ArrayList.(ArrayList.java:177) ~[?:1.8.0_112]
> at
> org.apache.atlas.hive.hook.events.AlterTableRenameCol.getNotificationMessages(AlterTableRenameCol.java:57)
> at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:156)
> at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:52)
> at
> org.apache.hadoop.hive.ql.HookRunner.invokeGeneralHook(HookRunner.java:296)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ATLAS-2708) AWS S3 data lake typedefs for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16515156#comment-16515156 ] Madhan Neethiraj commented on ATLAS-2708: - [~barbara] - thanks for the updated model files. The changes look good. To be consistent with type-names used in rest of the models, I renamed the types to replace CamelCase with lower_case_underscore_seperation. Please review. > AWS S3 data lake typedefs for Atlas > --- > > Key: ATLAS-2708 > URL: https://issues.apache.org/jira/browse/ATLAS-2708 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Reporter: Barbara Eckman >Assignee: Barbara Eckman >Priority: Critical > Fix For: 1.1.0 > > Attachments: 3010-aws_model.json, ATLAS-2708.patch, > all_AWS_common_typedefs.json, all_AWS_common_typedefs_v2.json, > all_datalake_typedefs.json, all_datalake_typedefs_v2.json > > > Currently the base types in Atlas do not include AWS data lake objects. It > would be nice to add typedefs for AWS data lake objects (buckets and > pseudo-directories) and lineage processes that move the data from another > source (e.g., kafka topic) to the data lake. For example: > * AWSS3PseudoDir type represents the pseudo-directory “prefix” of objects in > an S3 bucket. For example, in the case of an object with key > “myWork/Development/Projects1.xls”, “myWork/Development” is the > pseudo-directory. It supports: > ** Array of avro schemas that are associated with the data in the > pseudo-directory (based on Avro schema extensions outlined in ATLAS-2694) > ** what type of data it contains, e.g., avro, json, unstructured > ** time of creation > * AWSS3BucketLifeCycleRule type represents a rule specifying a transition of > the data in a bucket to a storageClass after a specific time interval, or > expiration. For example, transition to GLACIER after 60 days, or expire > (i.e. be deleted) after 90 days: > ** ruleType (e.g., transition or expiration) > ** time interval in days before rule is executed > ** storageClass to which the data is transitioned (null if ruleType is > expiration) > * AWSTag type represents a tag-value pair created by the user and associated > with an AWS object. > ** tag > ** value > * AWSCloudWatchMetric type represents a storage or request metric that is > monitored by AWS CloudWatch and can be configured for a bucket > ** metricName, for example, “AllRequests”, “GetRequests”, > TotalRequestLatency, BucketSizeBytes > ** scope: null if entire bucket; otherwise, the prefixes/tags that filter or > limit the monitoring of the metric. > * AWSS3Bucket type represents a bucket in an S3 instance. It supports: > ** Array of AWSS3PseudoDirectories that are associated with objects stored > in the bucket > ** AWS region > ** IsEncrypted (boolean) > ** encryptionType, e.g., AES-256 > ** S3AccessPolicy, a JSON object expressing access policies, eg GetObject, > PutObject > ** time of creation > ** Array of AWSS3BucketLifeCycleRules that are associated with the bucket > ** Array of AWSS3CloudWatchMetrics that are associated with the bucket or > its tags or prefixes > ** Array of AWSTags that are associated with the bucket > * Generic dataset2Dataset process to represent movement of data from one > dataset to another. It supports: > ** array of transforms performed by the process > ** map of tag/value pairs representing configurationParameters of the process > ** inputs and outputs are arrays of dataset objects, e.g., kafka topic and > S3 pseudo-directory. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2708) AWS S3 data lake typedefs for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2708: Attachment: ATLAS-2708-2.patch > AWS S3 data lake typedefs for Atlas > --- > > Key: ATLAS-2708 > URL: https://issues.apache.org/jira/browse/ATLAS-2708 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Reporter: Barbara Eckman >Assignee: Barbara Eckman >Priority: Critical > Fix For: 1.1.0 > > Attachments: 3010-aws_model.json, ATLAS-2708-2.patch, > ATLAS-2708.patch, all_AWS_common_typedefs.json, > all_AWS_common_typedefs_v2.json, all_datalake_typedefs.json, > all_datalake_typedefs_v2.json > > > Currently the base types in Atlas do not include AWS data lake objects. It > would be nice to add typedefs for AWS data lake objects (buckets and > pseudo-directories) and lineage processes that move the data from another > source (e.g., kafka topic) to the data lake. For example: > * AWSS3PseudoDir type represents the pseudo-directory “prefix” of objects in > an S3 bucket. For example, in the case of an object with key > “myWork/Development/Projects1.xls”, “myWork/Development” is the > pseudo-directory. It supports: > ** Array of avro schemas that are associated with the data in the > pseudo-directory (based on Avro schema extensions outlined in ATLAS-2694) > ** what type of data it contains, e.g., avro, json, unstructured > ** time of creation > * AWSS3BucketLifeCycleRule type represents a rule specifying a transition of > the data in a bucket to a storageClass after a specific time interval, or > expiration. For example, transition to GLACIER after 60 days, or expire > (i.e. be deleted) after 90 days: > ** ruleType (e.g., transition or expiration) > ** time interval in days before rule is executed > ** storageClass to which the data is transitioned (null if ruleType is > expiration) > * AWSTag type represents a tag-value pair created by the user and associated > with an AWS object. > ** tag > ** value > * AWSCloudWatchMetric type represents a storage or request metric that is > monitored by AWS CloudWatch and can be configured for a bucket > ** metricName, for example, “AllRequests”, “GetRequests”, > TotalRequestLatency, BucketSizeBytes > ** scope: null if entire bucket; otherwise, the prefixes/tags that filter or > limit the monitoring of the metric. > * AWSS3Bucket type represents a bucket in an S3 instance. It supports: > ** Array of AWSS3PseudoDirectories that are associated with objects stored > in the bucket > ** AWS region > ** IsEncrypted (boolean) > ** encryptionType, e.g., AES-256 > ** S3AccessPolicy, a JSON object expressing access policies, eg GetObject, > PutObject > ** time of creation > ** Array of AWSS3BucketLifeCycleRules that are associated with the bucket > ** Array of AWSS3CloudWatchMetrics that are associated with the bucket or > its tags or prefixes > ** Array of AWSTags that are associated with the bucket > * Generic dataset2Dataset process to represent movement of data from one > dataset to another. It supports: > ** array of transforms performed by the process > ** map of tag/value pairs representing configurationParameters of the process > ** inputs and outputs are arrays of dataset objects, e.g., kafka topic and > S3 pseudo-directory. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2708) AWS S3 data lake typedefs for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16513574#comment-16513574 ] Madhan Neethiraj commented on ATLAS-2708: - [~barbara] - thanks for AWS/S3 model types. Here are my comments: - looks like following types are suitable to be modeled as a struct, instead of entity - given each instance will be contained within an instance of AWSS3Bucket; and they don't need their own separate identity outside of its container. -- AWSTag -- AWSCloudWatchMetric -- AWSS3BucketLifeCycleRule - is avroSchema applicable for AWSS3PseudoDir? - consider renaming attribute AWSTag.tag to AWSTag.key - to be in sync with names used in https://docs.aws.amazon.com/AmazonS3/latest/dev/object-tagging.html - I would suggest using attribute names that begin with a lower case letter, to be consistent with rest of types. AWSS3Bucket.S3AccessPolicy, AWSS3Bucket.AWSTags - AWSS3Object has an array of avro_schema associated with. Wouldn't a single avro_schema be enough? I updated the model files for above comments, except the last one, and uploaded in this JIRA - 3010-aws_model.json. Please review. > AWS S3 data lake typedefs for Atlas > --- > > Key: ATLAS-2708 > URL: https://issues.apache.org/jira/browse/ATLAS-2708 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Reporter: Barbara Eckman >Assignee: Barbara Eckman >Priority: Critical > Attachments: all_AWS_common_typedefs.json, all_datalake_typedefs.json > > > Currently the base types in Atlas do not include AWS data lake objects. It > would be nice to add typedefs for AWS data lake objects (buckets and > pseudo-directories) and lineage processes that move the data from another > source (e.g., kafka topic) to the data lake. For example: > * AWSS3PseudoDir type represents the pseudo-directory “prefix” of objects in > an S3 bucket. For example, in the case of an object with key > “myWork/Development/Projects1.xls”, “myWork/Development” is the > pseudo-directory. It supports: > ** Array of avro schemas that are associated with the data in the > pseudo-directory (based on Avro schema extensions outlined in ATLAS-2694) > ** what type of data it contains, e.g., avro, json, unstructured > ** time of creation > * AWSS3BucketLifeCycleRule type represents a rule specifying a transition of > the data in a bucket to a storageClass after a specific time interval, or > expiration. For example, transition to GLACIER after 60 days, or expire > (i.e. be deleted) after 90 days: > ** ruleType (e.g., transition or expiration) > ** time interval in days before rule is executed > ** storageClass to which the data is transitioned (null if ruleType is > expiration) > * AWSTag type represents a tag-value pair created by the user and associated > with an AWS object. > ** tag > ** value > * AWSCloudWatchMetric type represents a storage or request metric that is > monitored by AWS CloudWatch and can be configured for a bucket > ** metricName, for example, “AllRequests”, “GetRequests”, > TotalRequestLatency, BucketSizeBytes > ** scope: null if entire bucket; otherwise, the prefixes/tags that filter or > limit the monitoring of the metric. > * AWSS3Bucket type represents a bucket in an S3 instance. It supports: > ** Array of AWSS3PseudoDirectories that are associated with objects stored > in the bucket > ** AWS region > ** IsEncrypted (boolean) > ** encryptionType, e.g., AES-256 > ** S3AccessPolicy, a JSON object expressing access policies, eg GetObject, > PutObject > ** time of creation > ** Array of AWSS3BucketLifeCycleRules that are associated with the bucket > ** Array of AWSS3CloudWatchMetrics that are associated with the bucket or > its tags or prefixes > ** Array of AWSTags that are associated with the bucket > * Generic dataset2Dataset process to represent movement of data from one > dataset to another. It supports: > ** array of transforms performed by the process > ** map of tag/value pairs representing configurationParameters of the process > ** inputs and outputs are arrays of dataset objects, e.g., kafka topic and > S3 pseudo-directory. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2708) AWS S3 data lake typedefs for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2708: Attachment: 3010-aws_model.json > AWS S3 data lake typedefs for Atlas > --- > > Key: ATLAS-2708 > URL: https://issues.apache.org/jira/browse/ATLAS-2708 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Reporter: Barbara Eckman >Assignee: Barbara Eckman >Priority: Critical > Attachments: 3010-aws_model.json, all_AWS_common_typedefs.json, > all_datalake_typedefs.json > > > Currently the base types in Atlas do not include AWS data lake objects. It > would be nice to add typedefs for AWS data lake objects (buckets and > pseudo-directories) and lineage processes that move the data from another > source (e.g., kafka topic) to the data lake. For example: > * AWSS3PseudoDir type represents the pseudo-directory “prefix” of objects in > an S3 bucket. For example, in the case of an object with key > “myWork/Development/Projects1.xls”, “myWork/Development” is the > pseudo-directory. It supports: > ** Array of avro schemas that are associated with the data in the > pseudo-directory (based on Avro schema extensions outlined in ATLAS-2694) > ** what type of data it contains, e.g., avro, json, unstructured > ** time of creation > * AWSS3BucketLifeCycleRule type represents a rule specifying a transition of > the data in a bucket to a storageClass after a specific time interval, or > expiration. For example, transition to GLACIER after 60 days, or expire > (i.e. be deleted) after 90 days: > ** ruleType (e.g., transition or expiration) > ** time interval in days before rule is executed > ** storageClass to which the data is transitioned (null if ruleType is > expiration) > * AWSTag type represents a tag-value pair created by the user and associated > with an AWS object. > ** tag > ** value > * AWSCloudWatchMetric type represents a storage or request metric that is > monitored by AWS CloudWatch and can be configured for a bucket > ** metricName, for example, “AllRequests”, “GetRequests”, > TotalRequestLatency, BucketSizeBytes > ** scope: null if entire bucket; otherwise, the prefixes/tags that filter or > limit the monitoring of the metric. > * AWSS3Bucket type represents a bucket in an S3 instance. It supports: > ** Array of AWSS3PseudoDirectories that are associated with objects stored > in the bucket > ** AWS region > ** IsEncrypted (boolean) > ** encryptionType, e.g., AES-256 > ** S3AccessPolicy, a JSON object expressing access policies, eg GetObject, > PutObject > ** time of creation > ** Array of AWSS3BucketLifeCycleRules that are associated with the bucket > ** Array of AWSS3CloudWatchMetrics that are associated with the bucket or > its tags or prefixes > ** Array of AWSTags that are associated with the bucket > * Generic dataset2Dataset process to represent movement of data from one > dataset to another. It supports: > ** array of transforms performed by the process > ** map of tag/value pairs representing configurationParameters of the process > ** inputs and outputs are arrays of dataset objects, e.g., kafka topic and > S3 pseudo-directory. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-2708) AWS S3 data lake typedefs for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16513574#comment-16513574 ] Madhan Neethiraj edited comment on ATLAS-2708 at 6/15/18 9:14 AM: -- [~barbara] - thanks for AWS/S3 model types. Here are my comments: - looks like following types are suitable to be modeled as a struct, instead of entity - given each instance will be contained within an instance of AWSS3Bucket; and they don't need their own separate identity outside of its container. -- AWSTag -- AWSCloudWatchMetric -- AWSS3BucketLifeCycleRule - is avroSchema applicable for AWSS3PseudoDir? - consider renaming attribute AWSTag.tag to AWSTag.key - to be in sync with names used in https://docs.aws.amazon.com/AmazonS3/latest/dev/object-tagging.html - I would suggest using attribute names that begin with a lower case letter, to be consistent with rest of types. AWSS3Bucket.S3AccessPolicy, AWSS3Bucket.AWSTags - AWSS3Object has an array of avro_schema associated with. Wouldn't a single avro_schema be enough? I updated the model files for above comments, except the last one, and uploaded in this JIRA - [^3010-aws_model.json]. Please review. was (Author: madhan.neethiraj): [~barbara] - thanks for AWS/S3 model types. Here are my comments: - looks like following types are suitable to be modeled as a struct, instead of entity - given each instance will be contained within an instance of AWSS3Bucket; and they don't need their own separate identity outside of its container. -- AWSTag -- AWSCloudWatchMetric -- AWSS3BucketLifeCycleRule - is avroSchema applicable for AWSS3PseudoDir? - consider renaming attribute AWSTag.tag to AWSTag.key - to be in sync with names used in https://docs.aws.amazon.com/AmazonS3/latest/dev/object-tagging.html - I would suggest using attribute names that begin with a lower case letter, to be consistent with rest of types. AWSS3Bucket.S3AccessPolicy, AWSS3Bucket.AWSTags - AWSS3Object has an array of avro_schema associated with. Wouldn't a single avro_schema be enough? I updated the model files for above comments, except the last one, and uploaded in this JIRA - 3010-aws_model.json. Please review. > AWS S3 data lake typedefs for Atlas > --- > > Key: ATLAS-2708 > URL: https://issues.apache.org/jira/browse/ATLAS-2708 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Reporter: Barbara Eckman >Assignee: Barbara Eckman >Priority: Critical > Attachments: 3010-aws_model.json, all_AWS_common_typedefs.json, > all_datalake_typedefs.json > > > Currently the base types in Atlas do not include AWS data lake objects. It > would be nice to add typedefs for AWS data lake objects (buckets and > pseudo-directories) and lineage processes that move the data from another > source (e.g., kafka topic) to the data lake. For example: > * AWSS3PseudoDir type represents the pseudo-directory “prefix” of objects in > an S3 bucket. For example, in the case of an object with key > “myWork/Development/Projects1.xls”, “myWork/Development” is the > pseudo-directory. It supports: > ** Array of avro schemas that are associated with the data in the > pseudo-directory (based on Avro schema extensions outlined in ATLAS-2694) > ** what type of data it contains, e.g., avro, json, unstructured > ** time of creation > * AWSS3BucketLifeCycleRule type represents a rule specifying a transition of > the data in a bucket to a storageClass after a specific time interval, or > expiration. For example, transition to GLACIER after 60 days, or expire > (i.e. be deleted) after 90 days: > ** ruleType (e.g., transition or expiration) > ** time interval in days before rule is executed > ** storageClass to which the data is transitioned (null if ruleType is > expiration) > * AWSTag type represents a tag-value pair created by the user and associated > with an AWS object. > ** tag > ** value > * AWSCloudWatchMetric type represents a storage or request metric that is > monitored by AWS CloudWatch and can be configured for a bucket > ** metricName, for example, “AllRequests”, “GetRequests”, > TotalRequestLatency, BucketSizeBytes > ** scope: null if entire bucket; otherwise, the prefixes/tags that filter or > limit the monitoring of the metric. > * AWSS3Bucket type represents a bucket in an S3 instance. It supports: > ** Array of AWSS3PseudoDirectories that are associated with objects stored > in the bucket > ** AWS region > ** IsEncrypted (boolean) > ** encryptionType, e.g., AES-256 > ** S3AccessPolicy, a JSON object expressing access policies, eg GetObject, > PutObject > ** time of creation > ** Array of AWSS3BucketLifeCycleRules that are associated with the bucket > ** Array of AWSS3CloudWatchMetrics that are associated
[jira] [Created] (ATLAS-2723) Improve search performance by creating composite indices for typeName+traitNames
Madhan Neethiraj created ATLAS-2723: --- Summary: Improve search performance by creating composite indices for typeName+traitNames Key: ATLAS-2723 URL: https://issues.apache.org/jira/browse/ATLAS-2723 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 1.0.0 Reporter: Madhan Neethiraj Assignee: Madhan Neethiraj For built-in attributes __traitNames, __propagatedTraitNames don't have composite index along with typeName. Given that searching of an entity of given type (hive_column) having specific classification (PII) is likely to be a common search scenario, having a composite index for these attributes with typeName will result in a quicker search response time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2723) Improve search performance by creating composite indices for typeName+traitNames
[ https://issues.apache.org/jira/browse/ATLAS-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2723: Attachment: ATLAS-2723.patch > Improve search performance by creating composite indices for > typeName+traitNames > > > Key: ATLAS-2723 > URL: https://issues.apache.org/jira/browse/ATLAS-2723 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Critical > Attachments: ATLAS-2723.patch > > > For built-in attributes __traitNames, __propagatedTraitNames don't have > composite index along with typeName. Given that searching of an entity of > given type (hive_column) having specific classification (PII) is likely to be > a common search scenario, having a composite index for these attributes with > typeName will result in a quicker search response time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2725) Update license for JanusGraph usage
[ https://issues.apache.org/jira/browse/ATLAS-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2725: Attachment: ATLAS-2725.patch > Update license for JanusGraph usage > --- > > Key: ATLAS-2725 > URL: https://issues.apache.org/jira/browse/ATLAS-2725 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 1.0.0 > > Attachments: ATLAS-2725.patch > > > Update license txt for JanusGraph usage in Apache Atlas 1.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2725) Update license for JanusGraph usage
Madhan Neethiraj created ATLAS-2725: --- Summary: Update license for JanusGraph usage Key: ATLAS-2725 URL: https://issues.apache.org/jira/browse/ATLAS-2725 Project: Atlas Issue Type: Bug Affects Versions: 1.0.0 Reporter: Madhan Neethiraj Assignee: Madhan Neethiraj Update license txt for JanusGraph usage in Apache Atlas 1.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2733) Download page must not link to dist.apache.org
[ https://issues.apache.org/jira/browse/ATLAS-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2733. - Resolution: Fixed Assignee: Madhan Neethiraj Fix Version/s: 1.0.0 > Download page must not link to dist.apache.org > -- > > Key: ATLAS-2733 > URL: https://issues.apache.org/jira/browse/ATLAS-2733 > Project: Atlas > Issue Type: Bug > Environment: http://atlas.apache.org/Downloads.html >Reporter: Sebb >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 1.0.0 > > > The download page should not link to dist.apache.org. > Please change the KEYS, sigs and hashes links to use the following instead: > https://www.apache.org/dist/atlas/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2734) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/ATLAS-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-2734. - Resolution: Fixed Fix Version/s: 1.0.0 Deleted 0.8.1 release from dist. Keeping 0.8.2, as this is the latest release from branch-0.8. > Please delete old releases from mirroring system > > > Key: ATLAS-2734 > URL: https://issues.apache.org/jira/browse/ATLAS-2734 > Project: Atlas > Issue Type: Bug > Environment: https://dist.apache.org/repos/dist/release/atlas/ >Reporter: Sebb >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 1.0.0 > > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases from the mirrors? > It looks like 0.8.2 and 0.8.1 are no longer current. > It's unfair to expect the 3rd party mirrors to carry old releases. > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2734) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/ATLAS-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj reassigned ATLAS-2734: --- Assignee: Madhan Neethiraj > Please delete old releases from mirroring system > > > Key: ATLAS-2734 > URL: https://issues.apache.org/jira/browse/ATLAS-2734 > Project: Atlas > Issue Type: Bug > Environment: https://dist.apache.org/repos/dist/release/atlas/ >Reporter: Sebb >Assignee: Madhan Neethiraj >Priority: Major > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases from the mirrors? > It looks like 0.8.2 and 0.8.1 are no longer current. > It's unfair to expect the 3rd party mirrors to carry old releases. > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2735) Update version in master branch to 2.0.0-SNAPSHOT
Madhan Neethiraj created ATLAS-2735: --- Summary: Update version in master branch to 2.0.0-SNAPSHOT Key: ATLAS-2735 URL: https://issues.apache.org/jira/browse/ATLAS-2735 Project: Atlas Issue Type: Bug Affects Versions: trunk Reporter: Madhan Neethiraj Assignee: Madhan Neethiraj Now that Apache Atlas 1.0.0 has been released, update master branch to use version 2.0.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2735) Update version in master branch to 2.0.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/ATLAS-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2735: Attachment: ATLAS-2735.patch > Update version in master branch to 2.0.0-SNAPSHOT > - > > Key: ATLAS-2735 > URL: https://issues.apache.org/jira/browse/ATLAS-2735 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: trunk > > Attachments: ATLAS-2735.patch > > > Now that Apache Atlas 1.0.0 has been released, update master branch to use > version 2.0.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2735) Update version in master branch to 2.0.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/ATLAS-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2735: Affects Version/s: (was: trunk) 2.0.0 Fix Version/s: (was: trunk) 2.0.0 > Update version in master branch to 2.0.0-SNAPSHOT > - > > Key: ATLAS-2735 > URL: https://issues.apache.org/jira/browse/ATLAS-2735 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 2.0.0 > > Attachments: ATLAS-2735.patch > > > Now that Apache Atlas 1.0.0 has been released, update master branch to use > version 2.0.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2736) Cannot find link to download page
[ https://issues.apache.org/jira/browse/ATLAS-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2736: Attachment: Atlas_Downloads.png > Cannot find link to download page > - > > Key: ATLAS-2736 > URL: https://issues.apache.org/jira/browse/ATLAS-2736 > Project: Atlas > Issue Type: Bug >Reporter: Sebb >Priority: Major > Attachments: Atlas_Downloads.png > > > The download page: > http://atlas.apache.org/Downloads.html > does not appear to be linked from the main page > http://atlas.apache.org/ > Nor even from the Installation page: > http://atlas.apache.org/InstallationSteps.html > Also the installation page should refer to using the source release archive, > not a branch in Git. > Files in Git have not been formally released (VOTED on) and should not be > advertised to the general public; references to Git should be confined to > pages which are clearly intended for developers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2736) Cannot find link to download page
[ https://issues.apache.org/jira/browse/ATLAS-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16501008#comment-16501008 ] Madhan Neethiraj commented on ATLAS-2736: - [~s...@apache.org] - Downloads link can be accessed via 'Apache Atlas' menu item at the top-left; please see the attached image. Thanks for helpful comments on installation page contents. I will review and update InstallationSteps.html shortly. > Cannot find link to download page > - > > Key: ATLAS-2736 > URL: https://issues.apache.org/jira/browse/ATLAS-2736 > Project: Atlas > Issue Type: Bug >Reporter: Sebb >Priority: Major > Attachments: Atlas_Downloads.png > > > The download page: > http://atlas.apache.org/Downloads.html > does not appear to be linked from the main page > http://atlas.apache.org/ > Nor even from the Installation page: > http://atlas.apache.org/InstallationSteps.html > Also the installation page should refer to using the source release archive, > not a branch in Git. > Files in Git have not been formally released (VOTED on) and should not be > advertised to the general public; references to Git should be confined to > pages which are clearly intended for developers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
