[jira] [Closed] (ATLAS-3180) New Bulk retrieval API with servicetype parameter
[
https://issues.apache.org/jira/browse/ATLAS-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diego Marino Monetti closed ATLAS-3180.
---
> New Bulk retrieval API with servicetype parameter
> --
>
> Key: ATLAS-3180
> URL: https://issues.apache.org/jira/browse/ATLAS-3180
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 1.2.0, 2.0.0
> Environment: All OS
>Reporter: Diego Marino Monetti
>Priority: Major
> Fix For: 1.2.0, trunk
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Bulk api retrieval returns all defined types or filtered types by name,
> type and supertype. With the addition of the service type among the basic
> attributes of the Atlas types it is necessary to have the possibility to
> search also for service type through a http request of the type:
> {quote}[http://host:port/api/atlas/V2/types/typedefs?serviceType|http://hostport/]
> = requested-service-type
> {quote}
> to search only for types related to a specific service type.
> This pull request solves this problem
> l[https://github.com/apache/atlas/pull/49]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ATLAS-3180) New Bulk retrieval API with servicetype parameter
[
https://issues.apache.org/jira/browse/ATLAS-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diego Marino Monetti resolved ATLAS-3180.
-
Resolution: Abandoned
> New Bulk retrieval API with servicetype parameter
> --
>
> Key: ATLAS-3180
> URL: https://issues.apache.org/jira/browse/ATLAS-3180
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 1.2.0, 2.0.0
> Environment: All OS
>Reporter: Diego Marino Monetti
>Priority: Major
> Fix For: 1.2.0, trunk
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Bulk api retrieval returns all defined types or filtered types by name,
> type and supertype. With the addition of the service type among the basic
> attributes of the Atlas types it is necessary to have the possibility to
> search also for service type through a http request of the type:
> {quote}[http://host:port/api/atlas/V2/types/typedefs?serviceType|http://hostport/]
> = requested-service-type
> {quote}
> to search only for types related to a specific service type.
> This pull request solves this problem
> l[https://github.com/apache/atlas/pull/49]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: Contributor on Atlas
Merryle, Thanks for your interest in contributing to Apache Atlas. You have been added as a contributor. Welcome to Apache Atlas community! Regards, Madhan On 5/25/19, 7:33 AM, "Merryle Wang" < merryle.w...@cloudera.com.INVALID> wrote: Hello, I would like to contribute to Apache Atlas. Can you please add me as a contributor in Apache Atlas? My JIRA account name is merrylewang. Thanks, Merryle
Re: Add me as a contributor in Atlas project
Diego Marino Monetti, Thanks for your contributions to Apache Atlas. You have been added as a contributor. Welcome to Apache Atlas community! Regards, Madhan On 5/24/19, 11:14 AM, "Diego Marino Monetti" wrote: Please could you add me as Atlas contributor so to link my issues to my account ? Regards Diego Marino Monetti
[jira] [Updated] (ATLAS-2928) Namespace entity relationship-attribute names to avoid conflict with entity attributes
[ https://issues.apache.org/jira/browse/ATLAS-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2928: Fix Version/s: (was: 2.0.0) trunk > Namespace entity relationship-attribute names to avoid conflict with entity > attributes > -- > > Key: ATLAS-2928 > URL: https://issues.apache.org/jira/browse/ATLAS-2928 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.0.0, 1.1.0 >Reporter: Madhan Neethiraj >Assignee: Le Ma >Priority: Critical > Fix For: 1.2.0, trunk > > > Apache Atlas 1.0 introduced relationships as first-class types. A > relationship effectively 'injects' an attribute on the entities at each end. > For example, assignment of a glossary term to an entity is captured by > relationship AtlasGlossarySemanticAssignment (in > -Area0/0011-glossary_model.json). This relationship adds following > attributes: > - Referceable.meanings: set > - AtlasGlossaryTerm.assignedEntities: set > This works fine as long as the entity-types involved in the relationship, or > their sub-types don't have an attribute with the same name as the attribute > injected by the relationships. Once such instance was reported by [~bolke], > about relationship attribute DataSet.schema introduced by > avro_schema_associatedEntities - which conflicts with spark_table.schema, > since spark_table type is a sub-type of DataSet. > Such name conflicts can be avoided by prefixing relationship-attribute names > with a prefix like "r:". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3232) Relationships, Export & Import : Updates to relationshipDef are not honored during import
[ https://issues.apache.org/jira/browse/ATLAS-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3232: Fix Version/s: (was: 2.0.0) trunk > Relationships, Export & Import : Updates to relationshipDef are not honored > during import > - > > Key: ATLAS-3232 > URL: https://issues.apache.org/jira/browse/ATLAS-3232 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Sharmadha Sainath >Priority: Major > Fix For: trunk > > > 1. In source cluster , updated relationshipDef "hive_table_db" propagateTags > to "ONE_TO_TWO" from NONE and exported. > 2.In export zip , atlas-typesdef.json has "ONE_TO_TWO" propagateTags value > for "hive_table_db" . > 3. But in the import cluster, propagateTags value for hive_table_db is NONE > still. In the import options , provided updateTypeDefinition to True too. > CC : [~ashutoshm] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2859) Basic search loads atlas internal type entities when searched with _NOT_CLASSIFIED classification paramter
[ https://issues.apache.org/jira/browse/ATLAS-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2859: Fix Version/s: (was: 2.0.0) trunk > Basic search loads atlas internal type entities when searched with > _NOT_CLASSIFIED classification paramter > -- > > Key: ATLAS-2859 > URL: https://issues.apache.org/jira/browse/ATLAS-2859 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 1.2.0, trunk > > Attachments: > 0001-ATLAS-2859-Fix-to-not-loads-atlas-internal-type-enti.patch, > _NOT_CLASSIFIED.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3198) update/delete/truncate operations ATLAS_HOOK and ATLAS_ENTITIES improvements
[ https://issues.apache.org/jira/browse/ATLAS-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3198: Fix Version/s: (was: 2.0.0) trunk > update/delete/truncate operations ATLAS_HOOK and ATLAS_ENTITIES improvements > - > > Key: ATLAS-3198 > URL: https://issues.apache.org/jira/browse/ATLAS-3198 > Project: Atlas > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Umesh Padashetty >Assignee: Yu-Hsin Chang >Priority: Critical > Fix For: trunk > > Attachments: ATLAS_HOOK and ATLAS_ENTITIES messages.xlsx > > > With the recent changes, we have now stopped ingesting simple insert > operations since with this operation, there is no change in the metadata. > Ideally, we should be doing similar improvements w.r.t. update, delete and > truncate operations too. > Currently, for update/delete/truncate, we are pushing messages in both > ATLAS_HOOK as well as ATLAS_ENTITIES topic, which can be avoided. > If we stop ingesting updates/deletes/truncates, it will further help us > reduce the burden on Kafka and save CPU cycles > I have created and attached an excel sheet, with the list of operations and > the corresponding messages generated in ATLAS_HOOK and ATLAS_ENTITIES topic, > along with suitable comments. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3086) Regression : Atlas Hive Hook doesn't capture insert into table values() queries
[ https://issues.apache.org/jira/browse/ATLAS-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3086: Fix Version/s: (was: 2.0.0) trunk > Regression : Atlas Hive Hook doesn't capture insert into table values() > queries > --- > > Key: ATLAS-3086 > URL: https://issues.apache.org/jira/browse/ATLAS-3086 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Priority: Major > Fix For: trunk > > > Atlas Hive Hook doesn't capture the query "insert into table values()" . This > is a regression as this event was captured in 0.8 > Other queries like > "from table1 a insert overwrite table bkp_table select a.id", > "insert into tableB select c1,c2 from tableA" , information is captured and > lineage is created in 1.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3219) Implemented new serviceType Rest API
[
https://issues.apache.org/jira/browse/ATLAS-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-3219:
Fix Version/s: (was: 2.0.0)
trunk
> Implemented new serviceType Rest API
>
>
> Key: ATLAS-3219
> URL: https://issues.apache.org/jira/browse/ATLAS-3219
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core, atlas-intg
>Affects Versions: 2.0.0
> Environment: all
>Reporter: Diego Marino Monetti
>Priority: Major
> Fix For: trunk
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This pull request supersedes the pull request ATLAS-3180.
> The new basic attribute serviceType, introduced by Atlas Team, has no use if
> it is not searchable ina any way. This pull request solves this problem by
> adding the following REST APIs.
> GET / typedef / servicetype / \{servicetype}
> GET / typedefs / headers? Servicetype = \{serviceType}
> GET / typedefs? Servicetype = \{servicetype}
> GET / enumdef / servicetype / \{servicetype}
> GET / entitydef / servicetype / \{servicetype}
> GET / structdef / servicetype / \{servicetype}
> GET / relationshipdef / servicetype / \{servicetype}
> DELETE / typedef / servicetype / \{servicetype}
> The APIs were tested on ATLAS 2.0 and on the new SNAPSHOT 3.0
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-3161) Add support for Java11
[ https://issues.apache.org/jira/browse/ATLAS-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3161: Fix Version/s: (was: 2.0.0) trunk > Add support for Java11 > -- > > Key: ATLAS-3161 > URL: https://issues.apache.org/jira/browse/ATLAS-3161 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Diego Marino Monetti >Priority: Major > Fix For: trunk > > > To support Java11 distribution needs add javax.annotation to atlas-common > project -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3012) Import of hive_db fails to create deleted column entity which was recreated again.
[
https://issues.apache.org/jira/browse/ATLAS-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-3012:
Fix Version/s: (was: 2.0.0)
trunk
> Import of hive_db fails to create deleted column entity which was recreated
> again.
> ---
>
> Key: ATLAS-3012
> URL: https://issues.apache.org/jira/browse/ATLAS-3012
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core, atlas-intg
>Affects Versions: 1.1.0
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: trunk
>
> Attachments: ATLAS-3012.patch, response.zip
>
>
> *Following is the test scenario:*
> In the source cluster :
> 1. create table with 3 columns (id,name,dob)
> 2. drop column dob
> 3. add the same dob column again.
> Now table has 3 ACTIVE columns and 1 DELETED column.
> Export the db into the target cluster.
> In the target cluster :
> only 2 ACTIVE (id,name) and 1 DELETED (dob) column is present. The ACTIVE
> column (dob) is not present.
> The exported zip contains both the DELETED and the ACTIVE dob column entity.
> In the source cluster ,
> if GUID1 is GUID of ACTIVE dob entity , and GUID2 is GUID of deleted dob
> entity.
> In the target cluster ,
> GUID1 is GUID of DELETED entity.
> Example :
> *In source :*
> ACTIVE:
> [https://atlas_source_host/index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070|https://ctr-e139-1542663976389-33282-01-08.hwx.site:21443/index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070]
> DELETED:[https://|https://ctr-e139-1542663976389-33282-01-08.hwx.site:21443/index.html#!/detailPage/f7686214-7585-4da3-875f-3e5223875289]
>
> [atlas_source_host|https://ctr-e139-1542663976389-33282-01-08.hwx.site:21443/index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070]
>
> [/index.html#!/detailPage/f7686214-7585-4da3-875f-3e5223875289|https://ctr-e139-1542663976389-33282-01-08.hwx.site:21443/index.html#!/detailPage/f7686214-7585-4da3-875f-3e5223875289]
> *In target :*
> DELETED :
> [https://|https://ctr-e139-1542663976389-33282-01-07.hwx.site:21443/index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070]
>
> [atlas_target_host|https://ctr-e139-1542663976389-33282-01-08.hwx.site:21443/index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070]
>
> [/index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070|https://ctr-e139-1542663976389-33282-01-07.hwx.site:21443/index.html#!/detailPage/7cca7064-8519-4db3-aab5-ebd446d15070]
> *{color:#d04437}Entity with GUID f7686214-7585-4da3-875f-3e5223875289 is not
> found.{color}*
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-2964) Unit TestCases for Exporting multiple hdfs_path
[ https://issues.apache.org/jira/browse/ATLAS-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2964: Fix Version/s: (was: 2.0.0) trunk > Unit TestCases for Exporting multiple hdfs_path > --- > > Key: ATLAS-2964 > URL: https://issues.apache.org/jira/browse/ATLAS-2964 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Kapildeo Nayak >Assignee: Kapildeo Nayak >Priority: Major > Fix For: trunk > > Attachments: > 0001-ATLAS-2964-Unit-TestCases-for-Exporting-multiple-hdf.patch > > > Modified: HdfsPathEntityHandler.java returned path instead of name in > toPath() method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3163) Incorrect syntax for combine-children in repository pom
[ https://issues.apache.org/jira/browse/ATLAS-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3163: Fix Version/s: (was: 2.0.0) trunk > Incorrect syntax for combine-children in repository pom > --- > > Key: ATLAS-3163 > URL: https://issues.apache.org/jira/browse/ATLAS-3163 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Diego Marino Monetti >Priority: Major > Fix For: trunk > > > in atlas-repository the syntax > org.apache.maven.plugins > maven-surefire-plugin > > > is incorrect. > The correct syntax is > org.apache.maven.plugins > maven-surefire-plugin > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3227) Bulk delete does not delete the indexes properly
[ https://issues.apache.org/jira/browse/ATLAS-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3227: Fix Version/s: (was: 2.0.0) trunk > Bulk delete does not delete the indexes properly > > > Key: ATLAS-3227 > URL: https://issues.apache.org/jira/browse/ATLAS-3227 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 > Environment: All >Reporter: Diego Marino Monetti >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: ATLAS-3227.patch, application-with-patch.log, > application-without-patch.log, bulkCreateType, bulkDeleteType, > sample_type.json > > Time Spent: 10m > Remaining Estimate: 0h > > Currently the Bulk Delete, first clears the cache and then does physical > deletion from Janus of the required types. At the end of this operation it > cycles through the attributes of the deleted types and for those attributes > for which it is possible to have indexes, built-ins, enums and structs, marks > the indexes as deleted. Since for each attribute the routine goes back to the > type of attribute using the typeRegistry, that is the cache, if this > attribute is a custom type the attribute was deleted before and the bulk > delete partially fails. > In particular, for each attribute in which this error does not occur, for > example because built-in type, a label delete is added to the property key > with the number of occurrences with which this property key is present in the > store. Something like property_key_deleted_0. In fact, if you try to reload > the same types and re-delete, the property keys are now marked as > property_key_deleted_1. > If, however, for the aforementioned reason the search for the type in the > cache fails the property key is not marked and remains fully active, which, > from what I can understand at this level of my knowledge, generates at least > some MEMORY LEAKs. > If I reload the types with the same entities and attributes it seems to be > all right, but if I change some attributes, in my opinion, the result is > unpredictable. > This path tested on version 2.0 and SNAPSHOT 3.0 would resolve this issue. > In attachment there is a small example that shows this behavior with and > without this patch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3042) Add relationship notification on drop table/column while processing hook message
[ https://issues.apache.org/jira/browse/ATLAS-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3042: Fix Version/s: (was: 2.0.0) trunk > Add relationship notification on drop table/column while processing hook > message > > > Key: ATLAS-3042 > URL: https://issues.apache.org/jira/browse/ATLAS-3042 > Project: Atlas > Issue Type: Sub-task >Affects Versions: trunk >Reporter: Nixon Rodrigues >Priority: Major > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3177) Regression , Export : changeMarker is not set right - set to older value compared to entity's lastModifedTime
[
https://issues.apache.org/jira/browse/ATLAS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-3177:
Fix Version/s: (was: 2.0.0)
trunk
> Regression , Export : changeMarker is not set right - set to older value
> compared to entity's lastModifedTime
> -
>
> Key: ATLAS-3177
> URL: https://issues.apache.org/jira/browse/ATLAS-3177
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 1.1.0
>Reporter: Sharmadha Sainath
>Priority: Major
> Fix For: 1.1.0, trunk
>
> Attachments: db_axyz.zip, db_def.json
>
>
> Export request body :
> {code}
> {"itemsToExport": [{"typeName": "hive_db", "uniqueAttributes":
> {"qualifiedName": "database_rbltx@mycluster0"}}], "options": {"fetchType":
> "incremental", "changeMarker": 0, "replicatedTo": "mycluster1"}}
> {code}
> The db's createTime is 1556276114134 (Friday, April 26, 2019 4:25:14.134 PM
> GMT+05:30)
> updatedTime is 1556276125588 (Friday, April 26, 2019 4:25:25.588 PM GMT+05:30)
> The changeMarker in exported zip file is 1556187028462 (Thursday, April 25,
> 2019 3:40:28.462 PM GMT+05:30)
> due to this unmodified entities are also exported everytime due to
> incremental export.
> Attaching the entity definition of db entity and the exported zip.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-3094) UniqueAttributes are not populating in relationship notification message
[
https://issues.apache.org/jira/browse/ATLAS-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-3094:
Fix Version/s: (was: 2.0.0)
trunk
> UniqueAttributes are not populating in relationship notification message
>
>
> Key: ATLAS-3094
> URL: https://issues.apache.org/jira/browse/ATLAS-3094
> Project: Atlas
> Issue Type: Sub-task
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
> Fix For: trunk
>
> Attachments:
> ATLAS-3094-UniqueAttributes-are-not-populating-in-re.patch
>
>
> UniqueAttributes are not populating in relationship notification message.
>
> e.g. refer end2 which is not having uniqueAttributes :
>
> {code:java}
> {
> ...,
> "message": {
> "type": "ENTITY_NOTIFICATION_V2",
> "relationship": {
> "typeName": "hive_table_columns",
> "guid": "3d3cec1f-e057-43a3-a167-cac69a1248a6",
> "status": "ACTIVE",
> "label": "__hive_table.columns",
> "end1": {
>"guid": "c44a1dda-5c89-4b3c-9679-9b368ae9f18a",
>"typeName": "hive_table",
>"uniqueAttributes":{
> "qualifiedName": "new_db.new_tbl_12@07012019"
> }
> },
> "end2":{
> "guid": "85bf3819-8289-46ed-9279-34b28a4dbe35",
> "typeName": "hive_column"
> }
> },
> "operationType": "RELATIONSHIP_CREATE",
> "eventTime": 1548828513837
> }
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (ATLAS-3199) **/bin/** in .gitignore is commented
[ https://issues.apache.org/jira/browse/ATLAS-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3199: Fix Version/s: (was: 2.0.0) trunk > **/bin/** in .gitignore is commented > > > Key: ATLAS-3199 > URL: https://issues.apache.org/jira/browse/ATLAS-3199 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 > Environment: all >Reporter: Diego Marino Monetti >Priority: Major > Fix For: trunk > > > I have no idea why, but thinking of some reason related to the development > team I didn't correct it. Can it be corrected? Create lots of untracked files > and confusion possibilities -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2800) UI - In Advance search an additional API request is fire when any column is drag and droped
[ https://issues.apache.org/jira/browse/ATLAS-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-2800: Fix Version/s: (was: 2.0.0) trunk > UI - In Advance search an additional API request is fire when any column is > drag and droped > --- > > Key: ATLAS-2800 > URL: https://issues.apache.org/jira/browse/ATLAS-2800 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8.1, 1.0.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8.2, 1.2.0, trunk > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3233) Relationships, Export & Import : Issue with ACTIVE and DELETED relationship-def instances
[ https://issues.apache.org/jira/browse/ATLAS-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3233: Fix Version/s: (was: 2.0.0) trunk > Relationships, Export & Import : Issue with ACTIVE and DELETED > relationship-def instances > - > > Key: ATLAS-3233 > URL: https://issues.apache.org/jira/browse/ATLAS-3233 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Priority: Major > Fix For: trunk > > > 1. In source cluster , create 2 types and a relationship-def between them. > 2. Create 2 entities and create relationship instance between them. > (relationship_guid_1 is created and it is ACTIVE) > 3. Export & Import entity1. > 4. On target cluster , relationship_guid_1 is imported and it is ACTIVE. > 5. Now, on source cluster , delete relationship_guid_1 and create a new > relationship between entity1 and entity2. > 6. In source cluster , relationship_guid_1 is DELETED and new > relationship_guid_2 is ACTIVE. > 7. Export and Import the entity1 to target cluster. > 8. In target cluster , relationship_guid_1 is still ACTIVE and > relationship_guid_2 is not imported at all . (GET on relationship_guid_2 > throws 404 on target cluster) > 9. In the exported zip , there is no information about relationship_guid_1 > but only about relationship_guid_2. > CC : [~ashutoshm] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Contributor on Atlas
Hello, I would like to contribute to Apache Atlas. Can you please add me as a contributor in Apache Atlas? My JIRA account name is merrylewang. Thanks, Merryle
