[jira] [Updated] (ATLAS-3033) ATLAS Hive hook fails for CTAS query involving UDFs
[
https://issues.apache.org/jira/browse/ATLAS-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carol Drummond updated ATLAS-3033:
--
Labels: (was: release-notes)
> ATLAS Hive hook fails for CTAS query involving UDFs
> ---
>
> Key: ATLAS-3033
> URL: https://issues.apache.org/jira/browse/ATLAS-3033
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8.3
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 0.8.4, 1.2.0, 2.0.0
>
> Attachments: ATLAS-3033-branch-2.0.patch, ATLAS-3033-master.patch,
> ATLAS-3033.patch
>
>
> ATLAS Hive Hook fails to notify for CTAS queries involving UDFs, Hook fails
> with the exception as below
> {code}
> org.apache.hadoop.hive.ql.metadata.InvalidTableException: Table not found
> _dummy_table
> {code}
> complete stack trace.
> {code}
> 2018-12-26 12:15:22,234 ERROR [HiveServer2-Background-Pool: Thread-339]:
> metadata.Hive (Hive.java:getTable(1220)) - Table _dummy_table not found:
> _dummy_database._
> dummy_table table not found
> 2018-12-26 12:15:22,234 ERROR [HiveServer2-Background-Pool: Thread-339]:
> hook.HiveHook (HiveHook.java:run(160)) - HiveHook.run(): failed to process
> operation CREAT
> ETABLE_AS_SELECT
> org.apache.hadoop.hive.ql.metadata.InvalidTableException: Table not found
> _dummy_table
> at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1221)
> at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:1191)
> at
> org.apache.atlas.hive.hook.events.BaseHiveEvent.toAtlasEntity(BaseHiveEvent.java:225)
> at
> org.apache.atlas.hive.hook.events.BaseHiveEvent.getInputOutputEntity(BaseHiveEvent.java:203)
> at
> org.apache.atlas.hive.hook.events.CreateHiveProcess.getEntities(CreateHiveProcess.java:84)
> at
> org.apache.atlas.hive.hook.events.CreateHiveProcess.getNotificationMessages(CreateHiveProcess.java:59)
> at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:157)
> at org.apache.atlas.hive.hook.HiveHook.run(HiveHook.java:52)
> at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1619)
> at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1303)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1170)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1165)
> at
> org.apache.hive.service.cli.operation.SQLOperation.runQuery(SQLOperation.java:197)
> at
> org.apache.hive.service.cli.operation.SQLOperation.access$300(SQLOperation.java:76)
> at
> org.apache.hive.service.cli.operation.SQLOperation$2$1.run(SQLOperation.java:255)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1869)
> at
> org.apache.hive.service.cli.operation.SQLOperation$2.run(SQLOperation.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> 2018-12-26 12:15:22,234 INFO [HiveServer2-Background-Pool: Thread-339]:
> log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) - method=PostHook.org.apache.atlas.hive.hook.HiveHook start=154582659
> end=1545826522234 duration=5 from=org.apache.hadoop.hive.ql.Driver>
> {code}
> The problem looks to be appearing as result being stored for UDF in temporary
> table _dummy_database._dummy_table and while creating a Lineage the process
> fails.
> Steps to reproduce is running below SQL.
> {code}
> create table masktest11 as select stack(2, "eddie", "111", "ravi", "222") as
> (name, ssn);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-2775) Enhance basic search to search entities with any classifications or no classifications
[ https://issues.apache.org/jira/browse/ATLAS-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2775: -- Labels: (was: release-notes) > Enhance basic search to search entities with any classifications or no > classifications > -- > > Key: ATLAS-2775 > URL: https://issues.apache.org/jira/browse/ATLAS-2775 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.1.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.1.0, 2.0.0 > > > Enhance basic search to search on entities with any classifications or no > classifications > Basic search can now take the following value for classification: > * *_CLASSIFIED -* Search on all entities with ANY classification associated > (directly or through propagation) > * *_NOT_CLASSIFIED -* Search on all entities with NO classifications > associated (directly or through propagation) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2986) REST calls during import operations include unnecessary doAs parameter
[ https://issues.apache.org/jira/browse/ATLAS-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2986: -- Labels: (was: release-notes) > REST calls during import operations include unnecessary doAs parameter > -- > > Key: ATLAS-2986 > URL: https://issues.apache.org/jira/browse/ATLAS-2986 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8.1, 0.8.2, 1.0.0, 0.8.3, 1.1.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-2986.patch > > > REST calls to Atlas server during import operations include doAs query > parameter, which is unnecessary. This should be fixed to avoid sending doAs > parameter, since the logged in username is same as the username sent in doAs > parameter. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2786) [Atlas HA] Zookeeper connection issue
[ https://issues.apache.org/jira/browse/ATLAS-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2786: -- Labels: (was: release-notes) > [Atlas HA] Zookeeper connection issue > - > > Key: ATLAS-2786 > URL: https://issues.apache.org/jira/browse/ATLAS-2786 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8.1, 0.8.2, 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Critical > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: > 0001-ATLAS-2786-Honor-ZK-server-ensemble-provided-in-conf.patch, > ATLAS-2786-2.patch > > > The curator client right now only connects to the very first zookeeper server > regardless of the number of zookeeper servers provided in the configuration. > > Due to this behavior if the ZK (that Atlas connected to during startup) goes > down then Atlas fails to serve further request while constantly trying to > reconnect to the dead ZK server. > > This patch makes the change in configuration parsing to allow fallback to > different ZK servers in case the primary goes down. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2878) update FullTextMapper to avoid retrieving referred entities
[ https://issues.apache.org/jira/browse/ATLAS-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2878: -- Labels: (was: release-notes) > update FullTextMapper to avoid retrieving referred entities > --- > > Key: ATLAS-2878 > URL: https://issues.apache.org/jira/browse/ATLAS-2878 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8.2, 1.0.0, 1.1.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Critical > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-2878-branch-0.8.patch, > ATLAS-2878-branch-1.0.patch, ATLAS-2878.patch > > > By default, full-text mapper is configured to not include text from referred > entities. However, the mapper currently retrieves referred entities as well > from the store. This can be avoided to save cycles spent in retrieving > entities not needed for the mapper. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3071) Add Functionalities to Collect Notification Metrics/Entity Lifecyle
[
https://issues.apache.org/jira/browse/ATLAS-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carol Drummond updated ATLAS-3071:
--
Labels: new-feature (was: new-feature release-notes)
> Add Functionalities to Collect Notification Metrics/Entity Lifecyle
> ---
>
> Key: ATLAS-3071
> URL: https://issues.apache.org/jira/browse/ATLAS-3071
> Project: Atlas
> Issue Type: New Feature
>Reporter: Le Ma
>Assignee: Le Ma
>Priority: Major
> Labels: new-feature
> Fix For: 2.0.0
>
> Attachments: ATLAS-3071-2.patch, ATLAS-3071.patch,
> MetricsDataModel.json
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Extend api/atlas/admin/metrics to provide metrics for notifications/entity
> lifycycle:
> # notification
> processed
> # notification
> failed
> today/thisHour/pastHour/total { # entity created
> # entity updated
> # entity deleted
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-2983) Fixes and clean up for Atlas Kafka bridge utility
[ https://issues.apache.org/jira/browse/ATLAS-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2983: -- Labels: (was: release-notes) > Fixes and clean up for Atlas Kafka bridge utility > - > > Key: ATLAS-2983 > URL: https://issues.apache.org/jira/browse/ATLAS-2983 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 1.0.0, 1.1.0 >Reporter: Umesh Padashetty >Assignee: Umesh Padashetty >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-2983.patch > > > # Currently, import-kafka.sh script allows selective kafka topic import by > providing -t or --topic option, but the script only checks for the topics > which start with the topic name provided and does not support regular > expression based selective import. With the fix provided, regex patterns can > be used along with -t as well as -f (file based import) option > # When a bad import-kafka command is being fired, following usage is being > printed on the console. Here, option should be -t instead of -n. Have fixed > this minor issue, along with some more text changes > ** import-kafka.sh [*-n* OR --topic ] > # Since we now have support for kakfa bridge and hbase hook/bridge, option > for creating entities for the following in Atlas UI could be removed > ## hbase_table > ## hbase_column > ## hbase_column_family > ## kafka_topic > ## hbase_namespace -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3076) UI : Relationship Tab improvements.
[ https://issues.apache.org/jira/browse/ATLAS-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3076: -- Labels: (was: release-notes) > UI : Relationship Tab improvements. > --- > > Key: ATLAS-3076 > URL: https://issues.apache.org/jira/browse/ATLAS-3076 > Project: Atlas > Issue Type: Improvement >Reporter: Binit Gutka >Assignee: Binit Gutka >Priority: Trivial > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3076.patch, ATLAS-3076_1.patch > > > In relationships tab, show entity-count along with the attribute name - in > table form. > In relationship tab, showing 'Table' as default rendering choice. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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
]
Carol Drummond updated ATLAS-2757:
--
Labels: (was: release-notes)
> 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
(v8.3.4#803005)
[jira] [Updated] (ATLAS-2766) UI - Turn off hyperlinks for entities with no entity-read access in search result display
[ https://issues.apache.org/jira/browse/ATLAS-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2766: -- Labels: (was: release-notes) > UI - Turn off hyperlinks for entities with no entity-read access in search > result display > - > > Key: ATLAS-2766 > URL: https://issues.apache.org/jira/browse/ATLAS-2766 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2766.patch > > > When ATLAS-2765 will be in place, the search result will have “-1” as guid > for entities on which the user doesn’t have ‘entity-read’ permission. UI > will not hyperlink ‘Name’ column for such result entries. This will prevent > the user from clicking the link to go to entity details page and not able to > tag term/classification. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2724) UI enhancement for Avro schemas and other JSON-valued attributes
[ https://issues.apache.org/jira/browse/ATLAS-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2724: -- Labels: (was: release-notes) > UI enhancement for Avro schemas and other JSON-valued attributes > > > Key: ATLAS-2724 > URL: https://issues.apache.org/jira/browse/ATLAS-2724 > Project: Atlas > Issue Type: New Feature >Affects Versions: 0.8-incubating >Reporter: Barbara Eckman >Assignee: Keval Bhatt >Priority: Critical > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: 0001-Add-pretty-printed-json-values-in-tables.patch, > ATLAS-2724-master.patch, ATLAS-2724.patch, new_table.png > > > Currently JSON-valued attributes are fully displayed in-line with other > attributes, not pretty-printed, cluttering the display. To support a better > display, we can display JSON-valued attributes in a one-line box that can be > scrolled down, or fully expanded with a mouse click that pretty-prints the > JSON. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3138) UI : Stats popup table layout improve for better readability
[ https://issues.apache.org/jira/browse/ATLAS-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3138: -- Labels: (was: release-notes) > UI : Stats popup table layout improve for better readability > > > Key: ATLAS-3138 > URL: https://issues.apache.org/jira/browse/ATLAS-3138 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.0.0 > > Attachments: ATLAS-3138.patch, ATLAS-3138_1.patch, > StatsDialog-updated.png > > > The patch includes the following changes.[^ATLAS-3138.patch] > * Merge active and deleted entities in one panel. > * Created a notification table with better representation. > * By default open Server Statistics panel > [^ATLAS-3138_1.patch] Includes number formatting of entities tab details -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2886) Export & Import Process: Add Support for Qualified Cluster Names
[ https://issues.apache.org/jira/browse/ATLAS-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2886: -- Labels: (was: release-notes) > Export & Import Process: Add Support for Qualified Cluster Names > > > Key: ATLAS-2886 > URL: https://issues.apache.org/jira/browse/ATLAS-2886 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 0.8.2 >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 0.8.3, 1.2.0, 2.0.0 > > Attachments: > ATLAS-2886-Export-Import-Support-fully-qualified-ser.patch > > > *Background* > For cases where cluster same cluster names can exist in different data > centers, it helps to add a data center name as prefix to cluster name. > The _replicatedTo_ and _replicatedFrom_ attributes in _AtlasExportRequest_ > and _AtlasImportRequest_ should be the place to specify this. > *Approach Guidance* > * Follow a convention where _data center name_ and cluster name should be > separated by $. E.g. _dc1$cl1_ > * Modify _AuditsWriter_ to support this. > * _AtlasServer_ already has _qualifiedName_ as a field. This will hold the > fully qualified name. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3084) Adding default value to the relationship
[ https://issues.apache.org/jira/browse/ATLAS-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3084: -- Labels: (was: release-notes) > Adding default value to the relationship > - > > Key: ATLAS-3084 > URL: https://issues.apache.org/jira/browse/ATLAS-3084 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.1.0 >Reporter: Kirankumar D G >Assignee: Kirankumar D G >Priority: Minor > Fix For: 1.2.0, 2.0.0 > > > Adding default value to the relationship -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3056) update rdbms types to remove use of ownedRef/inverseRef constraints for relationships
[ https://issues.apache.org/jira/browse/ATLAS-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3056: -- Labels: (was: release-notes) > update rdbms types to remove use of ownedRef/inverseRef constraints for > relationships > - > > Key: ATLAS-3056 > URL: https://issues.apache.org/jira/browse/ATLAS-3056 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3056-3.patch, ATLAS-3056.patch > > > RDBMS types use following attributes, with ownedRef/inverseRef constraints, > to create relationships between entity-types: > - rdbms_instance.database, rdbms_db.instance > - rdbms_db.tables, rdbms_table.db > - rdbms_table.columns, rdbms_column.table > - rdbms_table.indexes, rdbms_index.table > - rdbms_table.foreign_keys, rdbms_foreign_key.table > These attributes are not necessary, as corresponding relationship-types > (already present in the model) will automatically inject the same attributes > as relationship-attributes. > Above change has several benefits, including: > - improved performance, due to use of only one edge between two related > entities (compare this to 2 edges when ownedRef/inverseRef constraints are > used) > - simper to update a container entity, as there is not need to provide all > contained entities; same for contained entities as well -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2870) Import Service: Update AddClassification Transform to Support Scope
[ https://issues.apache.org/jira/browse/ATLAS-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2870: -- Labels: (was: release-notes) > Import Service: Update AddClassification Transform to Support Scope > --- > > Key: ATLAS-2870 > URL: https://issues.apache.org/jira/browse/ATLAS-2870 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 0.8.2 >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 0.8.3, 1.2.0, 2.0.0 > > Attachments: > ATLAS-2870-Improvement-to-AddClassification-transfor.2.patch > > > *Background* > Existing implementation of _AddClassification_ transform does not allow for > restricting addition of classification. > *Approach* > * Add new parameter to _addClassification_ transform, say _topLevel_. This > will add the transform only to top level entity. Add methods so that filters > can be added to this at runtime. > * Not having this parameter, will fallback to the original behavior. > * Update _ImportTransform__Shaper_ to use the > _ImportResult.getExportResult().getRequest()_ to use to add the required > filters to the transform. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3027) UI : Metric modal Improvements
[ https://issues.apache.org/jira/browse/ATLAS-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3027: -- Labels: (was: release-notes) > UI : Metric modal Improvements > -- > > Key: ATLAS-3027 > URL: https://issues.apache.org/jira/browse/ATLAS-3027 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3027.patch > > > Following point need to improve > * Count column should be right-aligned > * Show 'Total Active Entities’ and ‘Total Deleted Entities' > * Increase the modal height -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2774) Options for hard and soft delete of instances
[ https://issues.apache.org/jira/browse/ATLAS-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2774: -- Labels: (was: release-notes) > Options for hard and soft delete of instances > - > > Key: ATLAS-2774 > URL: https://issues.apache.org/jira/browse/ATLAS-2774 > Project: Atlas > Issue Type: New Feature >Reporter: Graham Wallis >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-2774-Soft-and-hard-delete-impl.patch, > ATLAS-2774-branch-0.8.patch, ATLAS-2774-master.patch > > > *Overview* > For Entities and Relationships, the following delete behaviors are desired. > Atlas can be configured to offer hard delete (only). Alternatively it can be > configured to offer soft-delete. Configuration is achieved by setting the > delete handler configuration property (see atlas-application.properties) to > either the SoftDeleteHandlerV1 or the HardDeleteHandlerV1. The default (for > when the property is not set) is to use the SoftDeleteHandlerV1. > The AtlasEntityStoreV2 deleteById() and deleteByIds() and methods and the > AtlasRelationshipStoreV2 deleteById() method are sensitive to the above > configuration. When the configuration is soft these methods will perform a > soft delete; when it is hard they will perform a hard delete. > In addition to the above methods, the AtlasEntityStoreV2 and > AtlasRelationshipStoreV2 offer a (new) purgeById() method that ALWAYS > performs a hard delete. This is true regardless of which delete handler has > been configured. When the configuration is hard, the purgeById() methods and > deleteById() methods are essentially equivalent. When the configuration is > soft, the purgeById() methods continue to provide a hard delete capability. > The AtlasEntityStoreV2 deleteById(), deleteByIds() and purgeById() methods > will delete the specified entities and any relationships to which they are > connected. The AtlasRelationshipStoreV2 deleteById() and purgeById() methods > will delete the specified relationship. Deletion of a relationship may cause > an upate to an entity to which the relationhsip is connected, if it changes > the propagation of classifications, for example. > In a hard delete or purge operation, an affected entity and relationship will > be removed from the graph and will not be returned in response to any future > queries. This is true regardless of whether the affected entity or > relationship has already been soft deleted or not. i.e. it's status could > initially be ACTIVE or DELETED. Following the operation it will not exist. > In a soft delete, the affected entities and relationships (that initially > have status ACTIVE) are updated to set the status to DELETED. These instances > can still be returned from queries and searches if the appropriate control is > selected (to include deleted instances). Without that control selected they > will not be returned. > *Use Case for soft delete* > Soft delete provides a 'safe' means of deleting instances from the repository > whilst preserving an audit trail and (if supported by the repository) > enabling a deleted instance to be restored (to ACTIVE status). > *Use Cases for hard delete* > One use case for hard delete is to permanently remove soft-deleted items some > period of time after they were soft deleted. > Another use case for hard delete is to is to correct (clean up after) a > mistake in which a potentially large batch of incomplete/corrupted/wrong > metadata is loaded and needs to be fully removed. > *Use Scenario for an OMAS user* > An OMAS provides a delete function that does NOT offer the user a choice of > hard/soft. The OMAS's delete function will invoke the relevant soft delete > method provided by the OMRS - deleteEntity or deleteRelationship. These are > both soft delete methods. > The Atlas OMRS Connector's deleteEntity/deleteRelationship methods will check > whether Atlas is configured for hard or soft delete. If Atlas is configured > for hard delete then soft-delete is not possible, and the method will throw a > FunctionNotSupported exception which is caught by the OMAS. > On catching this exception the OMAS author should automatically escalate the > soft delete to a hard delete by calling either of the mandatory OMRS > purgeEntity() or purgeRelationship() methods. In the Atlas OMRS Connector > these methods will invoke AtlasEntityStoreV2 purgeById() or > AtlasRelationshipStoreV2 purgeById(). The effect of this is that if soft > delete is not possible, a hard delete is used instead. > An OMAS does NOT provide a purge capability to a non-privileged user, but a > suitably expert OMRS or Atlas repository administrator can explicitly issue a > purge call at the OMRS or
[jira] [Updated] (ATLAS-3035) Entity retrieval to include soft-referenced entities in extInfo
[ https://issues.apache.org/jira/browse/ATLAS-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3035: -- Labels: (was: release-notes) > Entity retrieval to include soft-referenced entities in extInfo > --- > > Key: ATLAS-3035 > URL: https://issues.apache.org/jira/browse/ATLAS-3035 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.1.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3035-branch-1.0.patch, ATLAS-3035.patch > > > ATLAS-2813 introduced the notion of soft-reference for attributes that refer > to other entities. This should only change the storage details of the > relationship, but shouldn't introduce any change in the data exchanged via > REST APIs. However, the return from entity-get operations do not include > soft-referenced entities in extInfo. This should be updated such that the > return value would populate extInfo - just as in case of regular > object-references. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2746) [Glossary] Simple Term/Category creation should work with CREATE privilege
[ https://issues.apache.org/jira/browse/ATLAS-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2746: -- Labels: (was: release-notes) > [Glossary] Simple Term/Category creation should work with CREATE privilege > -- > > Key: ATLAS-2746 > URL: https://issues.apache.org/jira/browse/ATLAS-2746 > Project: Atlas > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: > 0001-ATLAS-2746-Term-Category-create-shouldn-t-require-UP.patch > > > Currently this operation needs following privileges > > Entity.READ, Entity.CREATE, Entity.UPDATE > > with the change simple term/category creation without any other relations > e.g. children, parent, categorized terms etc. can work with > > Entity.READ and Entity.CREATE -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2918) Update JanusGraph version to 0.3.1
[ https://issues.apache.org/jira/browse/ATLAS-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2918: -- Labels: (was: release-notes) > Update JanusGraph version to 0.3.1 > -- > > Key: ATLAS-2918 > URL: https://issues.apache.org/jira/browse/ATLAS-2918 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 1.1.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.0.0, 1.2.0, 2.0.0 > > Attachments: 0001-Update-JanusGraph-version-to-0.3.1-master-01.patch > > > Janusgraph community has released their latest version: > [https://github.com/JanusGraph/janusgraph/releases/tag/v0.3.1] > This JIRA will update janus version to 0.3.1 in atlas source. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2950) UI - In newer versions of chrome i.e 70 onwards, if a new column is added the instead of right most it appears at the left most
[ https://issues.apache.org/jira/browse/ATLAS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2950: -- Labels: (was: release-notes) > UI - In newer versions of chrome i.e 70 onwards, if a new column is added the > instead of right most it appears at the left most > > > Key: ATLAS-2950 > URL: https://issues.apache.org/jira/browse/ATLAS-2950 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Tejas Rawool >Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-2950.patch, SS5.png, SS6.png > > > Issue appears in - Version 70.0.3538.77 (Official Build) (64-bit) but doesn't > appears in Version 69.0.3497.100 (Official Build) (64-bit) version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2823) Update hooks to enable asynchronous notifications
[ https://issues.apache.org/jira/browse/ATLAS-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2823: -- Labels: (was: release-notes) > Update hooks to enable asynchronous notifications > - > > Key: ATLAS-2823 > URL: https://issues.apache.org/jira/browse/ATLAS-2823 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Critical > Fix For: 1.1.0, 2.0.0 > > > With refactoring of hooks to use V2 style notifications (ATLAS-2491), the > option to send notifications asynchronously was removed. Sending the > notifications asynchronously is helpful, to avoid delays in host component; > hence should be supported. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2811) Export Process: Support to Optionally Skip Lineage Entities from Being Exported
[ https://issues.apache.org/jira/browse/ATLAS-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2811: -- Labels: (was: release-notes) > Export Process: Support to Optionally Skip Lineage Entities from Being > Exported > --- > > Key: ATLAS-2811 > URL: https://issues.apache.org/jira/browse/ATLAS-2811 > Project: Atlas > Issue Type: Improvement > Components: atlas-core, atlas-intg >Affects Versions: 0.8.3 >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 0.8.3, 1.2.0, 2.0.0 > > > *Background* > In scenarios where importing lineage information can cause ambiguity, it will > be worthwhile having an option within Export to skip exporting lineage. > *Approach Guidance* > * Create a mechanism within _ExportService_ to filter out entities based on > a criteria. > * Within the filter, specify a criteria to skip entities of type _Process_. > * _AtlasExportRequest_ should have an option to specify filters. > * _ImportService_ should not be impacted. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3046) Classification Updater: Types Not Derived from Referenceable are Not Handled
[ https://issues.apache.org/jira/browse/ATLAS-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3046: -- Labels: (was: release-notes) > Classification Updater: Types Not Derived from Referenceable are Not Handled > > > Key: ATLAS-3046 > URL: https://issues.apache.org/jira/browse/ATLAS-3046 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 1.1.0, 2.0.0, trunk > > Attachments: ATLAS-3046-Classification-Updater-Unique-name-fix.patch, > ATLAS-3046-Part-3.-Updated-case-for-handling-deleted.patch > > > *Background* > The classification updater tool released to help users re-tag entities that > were present in an Atlas instance does not handle types that are not derived > from _Referencable_. > *Steps to Duplicate* > * Create a type that that is not derived from the _Referencable._ > * Execute the _prepare_ step_._ > Expected Results: Prepare completes successfully. > Actual Results: Following error is displayed: > ``` > Processing: db_1000_1@cl1 > Processed: 13 > Error writing: java.lang.NullPointerException > Done! > ``` -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2909) Export Process: ChangeMarker Remains Stuck at a Point
[
https://issues.apache.org/jira/browse/ATLAS-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carol Drummond updated ATLAS-2909:
--
Labels: (was: release-notes)
> Export Process: ChangeMarker Remains Stuck at a Point
> -
>
> Key: ATLAS-2909
> URL: https://issues.apache.org/jira/browse/ATLAS-2909
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8.2
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.2, 0.8.3, 1.2.0, 2.0.0
>
> Attachments:
> ATLAS-2909-ChangeMarker-updated-during-initializatio.patch
>
>
> *Pre-requisites*
> - Fresh installation of a build. This can be done by truncating atlas_titan
> and ATLAS_ENTITY_AUDIT_EVENTS tables.
> - Create some entities within Atlas either by 'Create New Entity' UI option
> or via Beeline/Hive.
> *Steps to Duplicate*
> * Perform export few times (more than 1) of the created entities using the
> following options and commands.
> * Observe the server logs (_application.log)_
> _export-options.json_
> {code:java}
> {
> "itemsToExport": [
> { "typeName": "hdfs_path", "uniqueAttributes": { "path":
> "/warehouse/hr/" }}
> ],
> "options": {
> "fetchType": "incremental",
> "matchType": "startsWith",
> "skipLineage": true,
> "replicatedTo": "clMain2"
> }
> }
> {code}
> CURL
> {code:java}
> curl -X POST -u admin:admin -H "Content-Type: application/json" -H
> "Cache-Control: no-cache" -d @../docs/export-options-skip-lineage.json
> http://localhost:21000/api/atlas/admin/export > ../docs/hr-1.zip
> {code}
>
> *Expected Results*
> Each export operation will display _changeMarker_ with new value.
> *Observed Results*
> Each export operation displays the same _changeMarker_ value.
> *Variation*
> Restart Atlas. Perform few exports. The value of _changeMarker_ now changes
> for each export.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3052) metrics query results caching - to be disabled
[ https://issues.apache.org/jira/browse/ATLAS-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3052: -- Labels: (was: release-notes) > metrics query results caching - to be disabled > -- > > Key: ATLAS-3052 > URL: https://issues.apache.org/jira/browse/ATLAS-3052 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.2.0, 2.0.0 >Reporter: Madhan Neethiraj >Assignee: Nikhil Bonte >Priority: Major > Fix For: 1.2.0, 2.0.0 > > > Metrics API introduced in ATLAS-1436 caches the results to provide quick > response and avoid frequent execution of expensive queries. Improvements > introduced in ATLAS-2959 result in much quicker execution of metrics queries, > hence this caching is no more needed. Removing this caching will help to get > recent metrics quickly i.e. without having to wait for cache rebuild. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2853) Entity notifications to be sent after transaction commit
[ https://issues.apache.org/jira/browse/ATLAS-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2853: -- Labels: (was: release-notes) > Entity notifications to be sent after transaction commit > > > Key: ATLAS-2853 > URL: https://issues.apache.org/jira/browse/ATLAS-2853 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Critical > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2853.patch > > > Currently, notification on entity changes (create/update/delete entities, > add/update/remove classifications on entities) are sent before the changes > are committed in the database. If commit fails, the entity state seen by > notification receivers would be different from Atlas. To avoid this, Atlas > server should entity notifications only after the transaction is committed to > the database. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3057) Index Repair Tool: Add JanusGraph-Specific Index Repair Tool
[ https://issues.apache.org/jira/browse/ATLAS-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3057: -- Labels: (was: release-notes) > Index Repair Tool: Add JanusGraph-Specific Index Repair Tool > > > Key: ATLAS-3057 > URL: https://issues.apache.org/jira/browse/ATLAS-3057 > Project: Atlas > Issue Type: New Feature >Reporter: Ashutosh Mestry >Assignee: Nikhil Bonte >Priority: Major > Fix For: 2.0.0, trunk > > Attachments: ATLAS-3057-Atlas-Index-Repair-tool-for-JanusGraph.patch, > ATLAS-3057-Atlas-Index-Repair-tool-for-JanusGraph.patch > > > *Background* > For Atlas version that uses _HBase_ and _Solr_, occasionally if Solr is down > and entities get created, then there is no record of the created entities > within Solr. Basic search does not indicate presence of such entities. > *Solution* > Index Repair Tool (which was present in branch-0.8) should be implemented for > JanusGraph. > *Implementation Guidance* > * Create Java-based implementation rather than Groovy script that needs > graphdb-specific shell to be installed. > * Use JanusGraph APIs for restore instead of custom per-vertex logic. > * Investigate possibility of using MapReduce for higher throughput. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2984) Exported zip file doesn't include relationship-def's referenced by entities
[ https://issues.apache.org/jira/browse/ATLAS-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2984: -- Labels: (was: release-notes) > Exported zip file doesn't include relationship-def's referenced by entities > --- > > Key: ATLAS-2984 > URL: https://issues.apache.org/jira/browse/ATLAS-2984 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.0.0, 1.1.0 >Reporter: Cade Parker >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-2984.patch > > > Zip file generated by export operation includes type-definitions referenced > by the exported entities - like entityDef, classficationDef, enumDef, > structDef. However, it doesn't include type-definitions for relationships > used in the entity-types. When this exported file content is imported into > another Atlas instance, relationship will not be created if the types don't > already exist in Atlas. To avoid this, export operation should include > relationship type definitions sas well in the zip file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3015) Tool: Associate Classifications to Entities based on QualifiedName
[ https://issues.apache.org/jira/browse/ATLAS-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3015: -- Labels: (was: release-notes) > Tool: Associate Classifications to Entities based on QualifiedName > -- > > Key: ATLAS-3015 > URL: https://issues.apache.org/jira/browse/ATLAS-3015 > Project: Atlas > Issue Type: Improvement >Reporter: Nikhil Bonte >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 2.0.0, trunk > > Attachments: 0001-ATLAS-3015.patch, > ATLAS-3015-Classification-Updater-tool-master.patch > > > *Background* > Situation: A setup where Atlas classifications associated with entities the > data is subsequently erased and all data is lost. Entities are then > re-created using _import-hive.sh_. With this approach, the entities are > created within Atlas but there is no easy way to associate classifications to > these entities. > *Solution and Approach Guidance* > # Before erasing Atlas database, create file with classifications and > entity-classification mapping. > # Erase the database. > # Create entities using appropriate means, say _import-hive.sh_. > # Read the file from step 1 and update Atlas. > The tool should: > * Use _AtlasClient_ REST APIs. > * External and can be executed against a known Atlas instance. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3107) update AtlasEntityDef with a field to capture attributes injected by relationship-defs
[ https://issues.apache.org/jira/browse/ATLAS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3107: -- Labels: (was: release-notes) > update AtlasEntityDef with a field to capture attributes injected by > relationship-defs > -- > > Key: ATLAS-3107 > URL: https://issues.apache.org/jira/browse/ATLAS-3107 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3107.patch > > > A relationship-def adds an attribute to entity-defs at each end of the > relationship. Entity instances include a field named > 'relationshipAttributes', to capture details of entities related to the > entity. Having entity-def include definitions of attributes added by > relationships will be helpful, for applications like UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3170) UI: Advanced Search does not allow saving of searches unless search is performed once.
[ https://issues.apache.org/jira/browse/ATLAS-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3170: -- Labels: (was: release-notes) > UI: Advanced Search does not allow saving of searches unless search is > performed once. > -- > > Key: ATLAS-3170 > URL: https://issues.apache.org/jira/browse/ATLAS-3170 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Keval Bhatt >Priority: Minor > Fix For: 1.2.0, 2.0.0 > > > Steps: > In Advanced Search column > # Enter value for "Search By Type" > # Enter value for "Search By Query" > # Click on "Save As" > Expected result: The "Create your favorite search" should appear. > Actual result : We get the message "Please select at least one filter" > However, if you execute the search with the values from steps 1 and 2, and > then click on "Save As" the expected result is achieved. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2827) Unable to persist vertex when indexed string attribute is really long
[ https://issues.apache.org/jira/browse/ATLAS-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2827: -- Labels: (was: release-notes) > Unable to persist vertex when indexed string attribute is really long > - > > Key: ATLAS-2827 > URL: https://issues.apache.org/jira/browse/ATLAS-2827 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.8.1, 0.8.2, 1.0.0, trunk >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 0.8.3, 1.1.0, 2.0.0 > > > Titan/Janus creates an inverted index key which exceeds the row length > restriction imposed by HBase hence the vertex fails to persist with backend > exception. > > Solution: > In the entity graph mapping, before persisting the vertex we need to trim > down the value (although it'll cause data loss) to avoid Atlas becoming non > functional for such edge cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2907) UI: Generate lineage information for process entities
[ https://issues.apache.org/jira/browse/ATLAS-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2907: -- Labels: (was: release-notes) > UI: Generate lineage information for process entities > - > > Key: ATLAS-2907 > URL: https://issues.apache.org/jira/browse/ATLAS-2907 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8.2, 1.0.0 >Reporter: Abhishek Kadam >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2907.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3139) basic search enhancement to include relationship attributes as well in the result
[
https://issues.apache.org/jira/browse/ATLAS-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carol Drummond updated ATLAS-3139:
--
Labels: (was: release-notes)
> basic search enhancement to include relationship attributes as well in the
> result
> -
>
> Key: ATLAS-3139
> URL: https://issues.apache.org/jira/browse/ATLAS-3139
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-3139.patch
>
>
> Basic-search results should include list of attributes specified in the
> search-request. This works for attributes that are directly defined in the
> given entity-type; if an attribute is a relationship attribute (for example:
> attribute 'table' in type 'hive_column'), its value is not included in the
> result.
> Request:
> {noformat}
> POST api/atlas/v2/search/basic
> { "typeName":"hive_column", "limit":2, "attributes":[ "table", "position" ]}
> {noformat}
> Response:
> {noformat}
> {
> "queryType": "BASIC",
> "searchParameters": {
> "typeName": "hive_column",
> "limit": 2,
> "attributes": [ "position", "table" ]
> }
> "entities": [
> {
> "guid":"464d3a2b-b1e0-4731-a924-4286b9e578ba",
> "typeName":"hive_column",
> "displayText": "dob",
> "status": "ACTIVE",
> "attributes": {
> "name": "dob",
> "owner": "madhan",
> "position": 2,
> "qualifiedName": "testdb.testtable.dob@cl1"
> }
> },
> {
> "guid":"1684e785-9200-41d0-843e-e79167a4a6e0",
> "typeName":"hive_column",
> "displayText": "name",
> "status": "ACTIVE",
> "attributes": {
> "name": "name",
> "owner": "madhan",
> "position": 1,
> "qualifiedName": "testdb.testtable.name@cl1"
> }
> }
> ]
> }
> {noformat}
> Expected Response:
> {noformat}
> {
> "queryType": "BASIC",
> "searchParameters": {
> "typeName": "hive_column",
> "limit": 2,
> "attributes": [ "position", "table" ]
> },
> "entities": [
> {
> "guid":"464d3a2b-b1e0-4731-a924-4286b9e578ba",
> "typeName":"hive_column",
> "displayText": "dob",
> "status": "ACTIVE",
> "attributes": {
> "name": "dob",
> "owner": "madhan",
> "position": 2,
> "qualifiedName": "testdb.testtable.dob@cl1",
> "table": {
> "guid": "3b29c9ae-d765-485d-bdba-bde1f9cc6794",
> "typeName": "hive_table",
> "uniqueAttributes": {
> "qualifiedName": "testdb.testtable@cl1"
> }
> }
> }
> },
> {
> "guid":"1684e785-9200-41d0-843e-e79167a4a6e0",
> "typeName":"hive_column",
> "displayText": "name",
> "status": "ACTIVE",
> "attributes": {
> "name": "name",
> "owner": "madhan",
> "position": 1,
> "qualifiedName": "testdb.testtable.name@cl1",
> "table": {
> "guid": "3b29c9ae-d765-485d-bdba-bde1f9cc6794",
> "typeName": "hive_table",
> "uniqueAttributes": {
> "qualifiedName": "testdb.testtable@cl1"
> }
> }
> }
> }
> ],
> "referredEntities": {
> "3b29c9ae-d765-485d-bdba-bde1f9cc6794": {
> "guid":"3b29c9ae-d765-485d-bdba-bde1f9cc6794",
> "typeName":"hive_table",
> "status": "ACTIVE",
> "displayText": "testtable",
> "attributes": {
> "createTime":155523129,
> "name": "testtable",
> "owner": "madhan",
> "qualifiedName": "testdb.testtable@cl1"
> }
> }
> }
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-2856) add utility method to find earliest active request in Atlas server
[ https://issues.apache.org/jira/browse/ATLAS-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2856: -- Labels: (was: release-notes) > add utility method to find earliest active request in Atlas server > -- > > Key: ATLAS-2856 > URL: https://issues.apache.org/jira/browse/ATLAS-2856 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 0.8.3, 1.2.0, 2.0.0 > > Attachments: ATLAS-2856.patch > > > RequestContext class captures context for the current request (i.e. REST API > call, Notification processing) in a thread-local. An utility method is needed > in this class to find the earliest active request - to be used in incremental > export feature. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3018) UI - classification search table shows then Basic search text with loader which is incorrect
[ https://issues.apache.org/jira/browse/ATLAS-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3018: -- Labels: (was: release-notes) > UI - classification search table shows then Basic search text with loader > which is incorrect > > > Key: ATLAS-3018 > URL: https://issues.apache.org/jira/browse/ATLAS-3018 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8.4, 1.2.0, 2.0.0 >Reporter: Tejas Rawool >Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-3018-branch-0.8.patch, ATLAS-3018.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3055) fix entity create/update to handle relationship attributes consistently
[ https://issues.apache.org/jira/browse/ATLAS-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3055: -- Labels: (was: release-notes) > fix entity create/update to handle relationship attributes consistently > --- > > Key: ATLAS-3055 > URL: https://issues.apache.org/jira/browse/ATLAS-3055 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.0.0, 1.1.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3055.patch > > > Currently an AtlasEntity can have relationship-attributes either in > 'attributes' or 'relationshipAttribute'. When a relationship attribute is > present in both, Atlas removes the attribute from 'attributes' and continues > processing the value in relationshipAttribute. However, if the attribute is > present only in 'attributes', Atlas doesn't move this value to > 'relationshipAttribute' - which can result in the attribute to be ignored if > no first-class attribute with the same name is present in the entity-def. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2920) Update JanusGraph Solr clients to use all zookeeper entries
[ https://issues.apache.org/jira/browse/ATLAS-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2920: -- Labels: (was: release-notes) > Update JanusGraph Solr clients to use all zookeeper entries > --- > > Key: ATLAS-2920 > URL: https://issues.apache.org/jira/browse/ATLAS-2920 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.1.0, 2.0.0 > > > Update JanusGraph Solr clients to use all zookeeper entries -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2926) ZipSink: Very Large Entities Cause Out Of Memory Exception
[
https://issues.apache.org/jira/browse/ATLAS-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carol Drummond updated ATLAS-2926:
--
Labels: (was: release-notes)
> ZipSink: Very Large Entities Cause Out Of Memory Exception
> --
>
> Key: ATLAS-2926
> URL: https://issues.apache.org/jira/browse/ATLAS-2926
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8.2, 0.8.3, trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0
>
> Attachments: ATLAS-2926-ZipSink-OOM.patch
>
>
> *Steps to Duplicate*
> # Setup Atlas with very large data. Atlas one entity should be about 300 MB
> in size.
> # Perform export with parameters that will include the large entity.
> Following error will be encountered:
> {code:java}
> java.lang.OutOfMemoryError: Requested array size exceeds VM limit at
> java.lang.StringCoding$StringEncoder.encode(StringCoding.java:300) at
> java.lang.StringCoding.encode(StringCoding.java:344) at
> java.lang.StringCoding.encode(StringCoding.java:387) at
> java.lang.String.getBytes(String.java:958) at
> org.apache.atlas.repository.impexp.ZipSink.addToZipStream(ZipSink.java:106)
> at org.apache.atlas.repository.impexp.ZipSink.saveToZip(ZipSink.java:95)
> at org.apache.atlas.repository.impexp.ZipSink.add(ZipSink.java:55) at
> org.apache.atlas.repository.impexp.ExportService.addEntity(ExportService.java:467)
> {code}
> *Additional Information*
> During conversion of entity string to bytes, a known JDK error is encountered.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-2943) Export: Operation Fails if No Options are Specified
[
https://issues.apache.org/jira/browse/ATLAS-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carol Drummond updated ATLAS-2943:
--
Labels: (was: release-notes)
> Export: Operation Fails if No Options are Specified
> ---
>
> Key: ATLAS-2943
> URL: https://issues.apache.org/jira/browse/ATLAS-2943
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8.2, 0.8.3, trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 0.8.3, 1.2.0, 2.0.0, trunk
>
> Attachments: ATLAS-2943-Export-options-null-check-added.patch
>
>
> *Pre-requisites*
> * Create database (say stocks), tables from beeline.
> *Steps to Duplicate*
> Attempt an export using these parameters:
> {code:java}
> { "itemsToExport": [ { "typeName": "hive_db", "uniqueAttributes": {
> "qualifiedName": "stocks@cl1" }} ] }
> {code}
> *Expected results*: Export should succeed with default options.
> *Actual results:* Export fails with the following exception:
> {code:java}
> 2018-10-28 16:03:54,311 ERROR - [pool-2-thread-9 -
> e63a2ebe-2480-4a60-b5f8-12595effdd9d:hrt_qa:POST/api/atlas/admin/export] ~
> Operation failed: (ExportService:116)
> java.lang.NullPointerException
> at
> org.apache.atlas.repository.impexp.AuditsWriter.isReplicationOptionSet(AuditsWriter.java:74)
> at
> org.apache.atlas.repository.impexp.AuditsWriter.access$200(AuditsWriter.java:44)
> at
> org.apache.atlas.repository.impexp.AuditsWriter$ExportAudits.add(AuditsWriter.java:150)
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-2897) Import Process: Handle Import of Empty Zip Elegantly
[ https://issues.apache.org/jira/browse/ATLAS-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2897: -- Labels: (was: release-notes) > Import Process: Handle Import of Empty Zip Elegantly > > > Key: ATLAS-2897 > URL: https://issues.apache.org/jira/browse/ATLAS-2897 > Project: Atlas > Issue Type: Improvement >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-2897-Better-handling-of-empty-zip-files.3.patch, > ATLAS-2897-Elegant-handling-of-empty-zip-files.patch > > > *Background* > Existing implementation of _ZipSource_ always assumes that the zip that is > being passed has valid data. It starts serializing the data and that is where > it encounters serialization error. This case can be handled in a more elegant > way. > *Approach Guidance* > * In _ZipSource_ ctor, detect case for empty file, throw error message > accordingly. > * Handle the case where requested _ZipEntry_ is not found. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3093) UI : Add missing tooltips to lineage page.
[ https://issues.apache.org/jira/browse/ATLAS-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3093: -- Labels: (was: release-notes) > UI : Add missing tooltips to lineage page. > -- > > Key: ATLAS-3093 > URL: https://issues.apache.org/jira/browse/ATLAS-3093 > Project: Atlas > Issue Type: Improvement >Reporter: Binit Gutka >Assignee: Binit Gutka >Priority: Trivial > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3093.patch > > > Add missing tooltips to the lineage page. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2832) Replace Titan with JanusGraph in the architecture diagram
[ https://issues.apache.org/jira/browse/ATLAS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2832: -- Labels: (was: release-notes) > Replace Titan with JanusGraph in the architecture diagram > - > > Key: ATLAS-2832 > URL: https://issues.apache.org/jira/browse/ATLAS-2832 > Project: Atlas > Issue Type: Task >Reporter: Jerry He >Assignee: Abhishek Kadam >Priority: Minor > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2832.patch > > > In Atlas 1.0, the graph backend is JanusGraph. We should replace Titan with > JanusGraph in this diagram https://atlas.apache.org/Architecture.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3058) Saving of favorite-search fails
[
https://issues.apache.org/jira/browse/ATLAS-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carol Drummond updated ATLAS-3058:
--
Labels: (was: release-notes)
> Saving of favorite-search fails
> ---
>
> Key: ATLAS-3058
> URL: https://issues.apache.org/jira/browse/ATLAS-3058
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 1.2.0, 2.0.0
>Reporter: Ayub Pathan
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments: ATLAS-3058.patch
>
>
> After recent changes in handling of relationship-attributes during entity
> create/update (ATLAS-3055), saving of favorite-seacrh fails with the
> following error:
> {noformat}
> 2019-02-26 22:59:35,462 ERROR - [pool-2-thread-10 -
> 05ba0035-4b16-417c-94ed-c2a73c53350a:hrt_qa:POST/api/atlas/v2/search/saved] ~
> addSavedSearch(AtlasUserSavedSearch{guid=-18693143454067265,...})
> (EntityDiscoveryService:827)
> org.apache.atlas.exception.AtlasBaseException: Referenced entity
> AtlasObjectId{guid='null', typeName='__AtlasUserProfile',
> uniqueAttributes={name:testuser1}} is not found
> at
> org.apache.atlas.repository.store.graph.v2.UniqAttrBasedEntityResolver.resolveEntityReferences(UniqAttrBasedEntityResolver.java:68)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasEntityGraphDiscoveryV2.resolveReferences(AtlasEntityGraphDiscoveryV2.java:181)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasEntityGraphDiscoveryV2.discoverEntities(AtlasEntityGraphDiscoveryV2.java:74)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.preCreateOrUpdate(AtlasEntityStoreV2.java:848)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:715)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:250)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$FastClassBySpringCGLIB$$6861dca9.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
> at
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:80)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671)
> at
> org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$EnhancerBySpringCGLIB$$ad28ea29.createOrUpdate()
> at
> org.apache.atlas.repository.ogm.DataAccess.saveNoLoad(DataAccess.java:73)
> at org.apache.atlas.repository.ogm.DataAccess.save(DataAccess.java:56)
> at
> org.apache.atlas.repository.userprofile.UserProfileService.addSavedSearch(UserProfileService.java:70)
> at
> org.apache.atlas.discovery.EntityDiscoveryService.addSavedSearch(EntityDiscoveryService.java:825)
> at
> org.apache.atlas.discovery.EntityDiscoveryService$$FastClassBySpringCGLIB$$1af2cf1f.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:667)
> at
> org.apache.atlas.discovery.EntityDiscoveryService$$EnhancerBySpringCGLIB$$efb3fb4b.addSavedSearch()
> at
> org.apache.atlas.web.rest.DiscoveryREST.addSavedSearch(DiscoveryREST.java:401)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-2777) Enhance advanced search (DSL) to support classification search on _CLASSIFIED or _NOT_CLASSIFIED keyword
[ https://issues.apache.org/jira/browse/ATLAS-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2777: -- Labels: (was: release-notes) > Enhance advanced search (DSL) to support classification search on _CLASSIFIED > or _NOT_CLASSIFIED keyword > > > Key: ATLAS-2777 > URL: https://issues.apache.org/jira/browse/ATLAS-2777 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.1.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: > 0001-ATLAS-2777-Enhance-advanced-search-DSL-to-support-cl.patch > > > ATLAS-2775 introduced keywords - _CLASSIFIED and __NOT__CLASSIFIED on basic > search to search on entities with ANY classifications or NO classifications. > This JIRA supports the same keywords in advanced search (DSL). > e.g: > * `_CLASSIFIED`, > * `_NOT_CLASSIFIED` > * hive_table isa _CLASSIFIED > * hive_column isa _NOT__CLASSIFIED -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3034) Perf enhancement to avoid unnecessary lookup when creating new relationships
[ https://issues.apache.org/jira/browse/ATLAS-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3034: -- Labels: (was: release-notes) > Perf enhancement to avoid unnecessary lookup when creating new relationships > > > Key: ATLAS-3034 > URL: https://issues.apache.org/jira/browse/ATLAS-3034 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.2.0, 2.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.2.0, 2.0.0 > > > Perf enhancement to avoid unnecessary lookup when creating new relationships -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-1070) UI: make lineage query only if entity type extends DataSet
[ https://issues.apache.org/jira/browse/ATLAS-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-1070: -- Labels: (was: release-notes) > UI: make lineage query only if entity type extends DataSet > -- > > Key: ATLAS-1070 > URL: https://issues.apache.org/jira/browse/ATLAS-1070 > Project: Atlas > Issue Type: Bug >Reporter: Shwetha GS >Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > > Currently, UI makes lineage query in entity details page always which looks > confusing in UI and shows error on server. UI should make lineage query only > if entity type contains 'DataSet' in supertypes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2803) Additions to AtlasEnumDef and AtlasRelationshipDef toString() methods
[ https://issues.apache.org/jira/browse/ATLAS-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2803: -- Labels: (was: release-notes) > Additions to AtlasEnumDef and AtlasRelationshipDef toString() methods > - > > Key: ATLAS-2803 > URL: https://issues.apache.org/jira/browse/ATLAS-2803 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Minor > Fix For: 2.0.0 > > Attachments: ATLAS-2803-2012-08-02.patch > > > The AtlasEnumDef toString() does not include the defaultValue of the enum. > The AtlasRelationshipDef toString() does not validate ends before > dereferencing them - causes NPEs in test scenarios -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2862) Export Service: Incremental Export: Next Increment Should Consider All Existing Request Contexts
[ https://issues.apache.org/jira/browse/ATLAS-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2862: -- Labels: (was: release-notes) > Export Service: Incremental Export: Next Increment Should Consider All > Existing Request Contexts > > > Key: ATLAS-2862 > URL: https://issues.apache.org/jira/browse/ATLAS-2862 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8.3 >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 0.8.3, 1.2.0, 2.0.0 > > > *Background* > When performing incremental Export, the existing implementation computes the > next increment timestamp by finding the maximum value of exported entities' > _modificationTimestamp_. This may work for majority of cases, however it has > a drawback. > Consider a scenario where export is in progress and one of the entities that > has already been written to the zip stream is modified by another request, > this will be missed from the the subsequent export operation. > *Solution Approach* > * Compute timestamps by enumerating all the requests in progress and finding > the earliest request. If no requests in progress, return current timestamp. > * Use the timestamp from step above for the change timestamp in > _AtlasExportResult_. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2785) Import Hive script should handle table name with database in -t option
[ https://issues.apache.org/jira/browse/ATLAS-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2785: -- Labels: (was: release-notes) > Import Hive script should handle table name with database in -t option > -- > > Key: ATLAS-2785 > URL: https://issues.apache.org/jira/browse/ATLAS-2785 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.1.0, trunk >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 1.1.0, 2.0.0 > > > Import Hive script should handle table name with database in -t > option.Currently if database name is there in table name for - t or > tablename option , it imports all the table. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2936) Enable Atlas to store provenance type information
[ https://issues.apache.org/jira/browse/ATLAS-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2936: -- Labels: (was: release-notes) > Enable Atlas to store provenance type information > - > > Key: ATLAS-2936 > URL: https://issues.apache.org/jira/browse/ATLAS-2936 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Major > Fix For: 1.2.0, 2.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3019) Handle NPE while transform and replicatedTo in import-export
[ https://issues.apache.org/jira/browse/ATLAS-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3019: -- Labels: (was: release-notes) > Handle NPE while transform and replicatedTo in import-export > > > Key: ATLAS-3019 > URL: https://issues.apache.org/jira/browse/ATLAS-3019 > Project: Atlas > Issue Type: Bug >Reporter: Kapildeo Nayak >Assignee: Kapildeo Nayak >Priority: Minor > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: > 0001-ATLAS-3019-Handle-NPE-while-transform-and-replicated.patch > > > 1) Export fails on setting replicatedTo value to null in export JSON > 2) Using transforms (replace) with both supertype and subtype fails with NPE > during import -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3090) PC Framework: Improve Existing Producer Consumer Framework
[ https://issues.apache.org/jira/browse/ATLAS-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3090: -- Labels: (was: release-notes) > PC Framework: Improve Existing Producer Consumer Framework > -- > > Key: ATLAS-3090 > URL: https://issues.apache.org/jira/browse/ATLAS-3090 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 2.0.0, trunk > > Attachments: ATLAS-3090-Improvements-to-PC-framework.patch > > > *Background* > Existing producer-consumer (PC) framework lacks: > * Restarting tasks. > * Results accumulation. > * Waiting for all tasks to complete. > *Solution Guidance* > Additional methods to include: > * _drain_: Complete execution of existing tasks. > * _submit_: Resubmit tasks. > * _checkAndSubmit_: Check if tasks are available before submissions. > * _getResults_: Get accumulated results. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2872) add an option to periodically clear cache in Hive hook
[ https://issues.apache.org/jira/browse/ATLAS-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2872: -- Labels: (was: release-notes) > add an option to periodically clear cache in Hive hook > -- > > Key: ATLAS-2872 > URL: https://issues.apache.org/jira/browse/ATLAS-2872 > Project: Atlas > Issue Type: Improvement > Components: atlas-intg >Affects Versions: 0.8.2, 1.0.0, 1.1.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-2872-branch-0.8.patch > > > Hive hook caches names of databases and tables which were sent in earlier > notifications, to avoid sending the same details in subsequent notifications. > This is a lru cache and keeps the number of names cached to a limit. This > caching should be updated with an option to periodically clear the names, so > that the details will be send again when the hook encounters these > databases/tables again. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2747) UI : Tag attributes of type array are displayed with an extra ">" character.
[ https://issues.apache.org/jira/browse/ATLAS-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2747: -- Labels: (was: release-notes) > UI : Tag attributes of type array are displayed with an extra ">" character. > > > Key: ATLAS-2747 > URL: https://issues.apache.org/jira/browse/ATLAS-2747 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Abhishek Kadam >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2747.patch > > > !Tag attribute of data type array.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3103) UI : Render Schema Table from relationship attributes node in the entity API
[ https://issues.apache.org/jira/browse/ATLAS-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3103: -- Labels: (was: release-notes) > UI : Render Schema Table from relationship attributes node in the entity API > > > Key: ATLAS-3103 > URL: https://issues.apache.org/jira/browse/ATLAS-3103 > Project: Atlas > Issue Type: Improvement >Reporter: Binit Gutka >Assignee: Binit Gutka >Priority: Major > Fix For: 2.0.0, trunk > > Attachments: ATLAS-3103.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2988) Replace title with the Bootstrap tooltip
[ https://issues.apache.org/jira/browse/ATLAS-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2988: -- Labels: (was: release-notes) > Replace title with the Bootstrap tooltip > > > Key: ATLAS-2988 > URL: https://issues.apache.org/jira/browse/ATLAS-2988 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-2988-branch-0.8.patch, ATLAS-2988.patch > > > Default title HTML attribute is taking few secs to show the tooltip. it will > be good to have a bootstrap tooltip (Example: > https://getbootstrap.com/docs/3.3/javascript/#tooltips) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2793) Enhance AtlasClient to use UGI's authentication method to initialize URL connection handler
[ https://issues.apache.org/jira/browse/ATLAS-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2793: -- Labels: (was: release-notes) > Enhance AtlasClient to use UGI's authentication method to initialize URL > connection handler > > > Key: ATLAS-2793 > URL: https://issues.apache.org/jira/browse/ATLAS-2793 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 0.8.2, 1.0.0 >Reporter: Sarath Subramanian >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: ATLAS-2793.patch > > > Currently the atlas client checks if kerberos authentication is enabled using > a property - *atlas.authentication.method.kerberos=true* > The client needs to be updated to inspect the UGI's authentication method > (SIMPLE or KERBEROS) and initialize the right URL Connection Handler if the > above property is not set. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2814) Export & Import Process: Add Data to AtlasCluster About Last Successful Import
[ https://issues.apache.org/jira/browse/ATLAS-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2814: -- Labels: (was: release-notes) > Export & Import Process: Add Data to AtlasCluster About Last Successful Import > -- > > Key: ATLAS-2814 > URL: https://issues.apache.org/jira/browse/ATLAS-2814 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 0.8.3 >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 0.8.3, 1.2.0, 2.0.0 > > Attachments: ATLAS-2814-Cluster-stores-replication-details.patch > > > *Background* > Scenario: Couple of Atlas clusters are setup such that incremental export and > import is setup via some custom program. Example, Cluster _cl1_ exports does > incremental export and the output is imported into cluster _cl2_. > It may be worth while to maintain some information about the last successful > import. This way the next incremental export will have correct parameters for > its export. > *Approach Guidance* > * Create a new model, say _AtlasSyncInfo_, that stores information about top > level entity used for export and the timestamp that should be used for > subsequent incremental export. > * Utilize _AtlasCluster_'s _additionalInfo_ fields to store serialized > version of _AtlasSyncInfo_. > * Provide REST APIs for retrieval of this information. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3113) Use index query to search for active entities and better logging in java patch framework
[ https://issues.apache.org/jira/browse/ATLAS-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3113: -- Labels: (was: release-notes) > Use index query to search for active entities and better logging in java > patch framework > > > Key: ATLAS-3113 > URL: https://issues.apache.org/jira/browse/ATLAS-3113 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.1.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 2.0.0 > > > In java patch framework - Unique attribute patch handler - to retrieve all > active entities graph query is used, graph query is expensive when number of > entities are large. This Jira updates the graph query to use index query and > also logging enhancements. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2869) Export Service: Hdfs Path Export Should Optionally Create Requested Entity and then Proceed With Export
[ https://issues.apache.org/jira/browse/ATLAS-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2869: -- Labels: (was: release-notes) > Export Service: Hdfs Path Export Should Optionally Create Requested Entity > and then Proceed With Export > --- > > Key: ATLAS-2869 > URL: https://issues.apache.org/jira/browse/ATLAS-2869 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 0.8.3 >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 0.8.2, 1.2.0, 2.0.0 > > Attachments: > ATLAS-2869-Hdfs_path-if-requested-are-created-and-th.patch > > > *Background* > Attempting to export entities of type _hdfs_path_, often fails since entities > need to be created manually. It would help the user if these requested > entities are created and then exported. > *Approach* > * Detect the request type. > * Create _hdfs_path_ entity. > * Proceed with regular export. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3048) API: Retrieve Audits for Classification Operations: Add support for Entities Not Derived from Referenceable
[ https://issues.apache.org/jira/browse/ATLAS-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3048: -- Labels: (was: release-notes) > API: Retrieve Audits for Classification Operations: Add support for Entities > Not Derived from Referenceable > --- > > Key: ATLAS-3048 > URL: https://issues.apache.org/jira/browse/ATLAS-3048 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.1.0 >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 2.0.0, trunk > > Attachments: ATLAS-3048-Remove-use-of-hard-coded-qualifiedName.patch > > > **Support entities not derived from _Referencable_. Get unique attribute from > the entity type. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3063) Update entity create/update to specify relationship-type for attributes
[ https://issues.apache.org/jira/browse/ATLAS-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3063: -- Labels: (was: release-notes) > Update entity create/update to specify relationship-type for attributes > --- > > Key: ATLAS-3063 > URL: https://issues.apache.org/jira/browse/ATLAS-3063 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.2.0, 2.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3063.patch > > > A relationship attribute can be referenced in more than one relationships. > For example attribute table in hive_column is referenced in relationships > hive_table_columns and hive_table_partitionKeys, which enables a hive_column > entity to participate in one of these relationships (columns or > partitionKeys) with a hive_table entity. > While create/update of an entity having such an attribute, it should be > possible to explicitly specify the relationship-type to use. For example, > while creating a hive_column entity, it should be possible to specify > relationship-type=hive_table_partitionKeys, so that this column will be added > to 'partitionKeys' of hive_table, instead of 'columns'. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2745) Atlas EnumDefStore does not remember default value
[ https://issues.apache.org/jira/browse/ATLAS-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2745: -- Labels: (was: release-notes) > Atlas EnumDefStore does not remember default value > -- > > Key: ATLAS-2745 > URL: https://issues.apache.org/jira/browse/ATLAS-2745 > Project: Atlas > Issue Type: Bug >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Minor > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: ATLAS-2745-2018-06-07.patch > > > If an enum def has a default value it is not remembered when the enum is > stored. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2995) Term Entity disassociation doesn't happen via knox proxy
[ https://issues.apache.org/jira/browse/ATLAS-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2995: -- Labels: (was: release-notes) > Term Entity disassociation doesn't happen via knox proxy > > > Key: ATLAS-2995 > URL: https://issues.apache.org/jira/browse/ATLAS-2995 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 1.1.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-2995.patch > > > *ISSUE:* > Request to disassociate a term from an entity via knox proxy succeeds , but > the disassociation doesn't happen. > *Cause:* > Knox Proxy Gateway does not support DELETE method api with body. > *Solution Recommended:-* > Come up with another API with PUT method with body or **DELETE method without > body with data in queryParamters. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2741) Deleted entities : DSL search with tag doesn't list the deleted entities to which that tag is associated
[ https://issues.apache.org/jira/browse/ATLAS-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2741: -- Labels: (was: release-notes) > Deleted entities : DSL search with tag doesn't list the deleted entities to > which that tag is associated > > > Key: ATLAS-2741 > URL: https://issues.apache.org/jira/browse/ATLAS-2741 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: > 0001-ATLAS-2741-Deleted-entities-DSL-search-with-tag-does.patch > > > 1.Create an hive_table employee and add tag1 to it. > 2.Drop the table. > 3. DSL search : hive_table where name="employee" lists the DELETED table. > 4. Basic search with tag1 and excludeDeletedEntities set to False lists the > DELETED table. > 3. But, DSL search "hive_table isa tag1" doesn't list the DELETED table. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3029) API: Retrieve Classification Events from Audits
[ https://issues.apache.org/jira/browse/ATLAS-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3029: -- Labels: (was: release-notes) > API: Retrieve Classification Events from Audits > --- > > Key: ATLAS-3029 > URL: https://issues.apache.org/jira/browse/ATLAS-3029 > Project: Atlas > Issue Type: Improvement > Components: atlas-core, atlas-intg >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: > ATLAS-3020-Audit-APIs-for-classification-updates-master.patch > > > *Use Cases* > 1. In the case where user looses data within Atlas, they can get it ingested > by using tool like _import-hive_. With this approach, the user does not get > the classifications and the entities associated with them. > 2. In case where classifications were inadvertently removed from entities. > *Solution* > In the scenarios above, currently there isn't a way to know the > classification operations performed. > A REST API that would get this information from Atlas' Audit tables would > benefit the user. > *Approach Guidance* > * REST endpoint: Use Atlas' Audit Repository to fetch the audit events. This > API should accept a timestamp range so that useful audit events can be > fetched. > * REST endpoint: Re-play the audit events to update Atlas. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3151) incorrect return type for AtlasClientV2.getRelationshipByGuid()
[ https://issues.apache.org/jira/browse/ATLAS-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3151: -- Labels: (was: release-notes) > incorrect return type for AtlasClientV2.getRelationshipByGuid() > --- > > Key: ATLAS-3151 > URL: https://issues.apache.org/jira/browse/ATLAS-3151 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 1.1.0, 2.0.0 >Reporter: Madhan Neethiraj >Priority: Major > Fix For: 1.2.0, 2.0.0 > > > Reported by jxzhao via [https://github.com/apache/atlas/pull/42.] > AtlasClientV2.getRelationshipByGuid() method returns AtlasRelationship; > however the REST API from Atlas server returns AtlasRelationshipWithExtInfo. > The client should be updated to match the server API. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2958) Exceptions other than NotificationException are not logged
[ https://issues.apache.org/jira/browse/ATLAS-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2958: -- Labels: logging (was: logging release-notes) > Exceptions other than NotificationException are not logged > -- > > Key: ATLAS-2958 > URL: https://issues.apache.org/jira/browse/ATLAS-2958 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0, 1.1.0, 1.2.0 >Reporter: Maxim Neaga >Priority: Minor > Labels: logging > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: 17.patch > > > Currently, exceptions such as "Failed to construct kafka producer" are not > logged, because they are an instance of KafkaException (see screenshot for an > example). > The following pull requests address the issue: > https://github.com/apache/atlas/pull/18 > https://github.com/apache/atlas/pull/17 > [!https://user-images.githubusercontent.com/3027370/47596715-0da5c400-d93d-11e8-9197-a6f1ce1c96b8.png!|https://user-images.githubusercontent.com/3027370/47596715-0da5c400-d93d-11e8-9197-a6f1ce1c96b8.png] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2764) Time Bound classification : Few timezones throw "Invalid timezone exception"
[ https://issues.apache.org/jira/browse/ATLAS-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2764: -- Labels: (was: release-notes) > Time Bound classification : Few timezones throw "Invalid timezone exception" > > > Key: ATLAS-2764 > URL: https://issues.apache.org/jira/browse/ATLAS-2764 > 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-2764.patch > > > Folllowing timezones from UI are missing in java timezone and throw INVALID > timezone exception > America/Punta_Arenas > Asia/Atyrau > Asia/Famagusta > Asia/Yangon > Europe/Saratov > ROC > It would be good to load timezone TimeZone.getAvailableIDs() on UI. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2938) Enable EntityGraphMapper to update entity version
[ https://issues.apache.org/jira/browse/ATLAS-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2938: -- Labels: (was: release-notes) > Enable EntityGraphMapper to update entity version > -- > > Key: ATLAS-2938 > URL: https://issues.apache.org/jira/browse/ATLAS-2938 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Major > Fix For: 1.2.0, 2.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3092) Atlas Plugin ClassLoader Doesn't Restore Thread ClassLoader
[ https://issues.apache.org/jira/browse/ATLAS-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3092: -- Labels: (was: release-notes) > Atlas Plugin ClassLoader Doesn't Restore Thread ClassLoader > --- > > Key: ATLAS-3092 > URL: https://issues.apache.org/jira/browse/ATLAS-3092 > Project: Atlas > Issue Type: Bug >Reporter: Shawn Weeks >Assignee: Ramesh Mani >Priority: Minor > Fix For: 2.0.0, trunk > > Attachments: > 0001-ATLAS-3092-Atlas-Plugin-ClassLoader-Doesn-t-Restore-.patch > > Time Spent: 1h > Remaining Estimate: 0h > > Currently when the AtlasPluginClassLoader is deactivated it sets the current > threads class loader to class loader that was active when the class was > instantiated. In applications like Hive where a single thread may be shared > among multiple sessions each with its own class loader this is breaking class > loading for UDFs. The deactivate method should set the current threads class > loader back to the class loader that was set when activate was called. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2979) Added service type dropdown to filter entitydef type.
[ https://issues.apache.org/jira/browse/ATLAS-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2979: -- Labels: (was: release-notes) > Added service type dropdown to filter entitydef type. > - > > Key: ATLAS-2979 > URL: https://issues.apache.org/jira/browse/ATLAS-2979 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 2.0.0 >Reporter: Abhishek Kadam >Assignee: Abhishek Kadam >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-2979.patch, ATLAS-2979_1.patch, > ATLAS-2979_FINAL.patch, ATLAS-2979_FINAL.patch, > ATLAS-2979_UI_Improvement.patch, return-serviceType-in-api-header.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3145) UI :Entity showing Active even if the relationshipStatus is Deleted
[ https://issues.apache.org/jira/browse/ATLAS-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3145: -- Labels: (was: release-notes) > UI :Entity showing Active even if the relationshipStatus is Deleted > --- > > Key: ATLAS-3145 > URL: https://issues.apache.org/jira/browse/ATLAS-3145 > Project: Atlas > Issue Type: Bug >Reporter: Binit Gutka >Assignee: Binit Gutka >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-3145_3.patch, active_entity.png, > image-2019-04-17-15-37-49-735.png, relationship_deleted.png, response.png > > > In the Relationship graph view, when an entity is deleted, the entity is > still shown as active. > All the deleted entities should be shown as deleted. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3129) Truststore reloader thread from AtlasBaseClient.
[ https://issues.apache.org/jira/browse/ATLAS-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3129: -- Labels: (was: release-notes) > Truststore reloader thread from AtlasBaseClient. > > > Key: ATLAS-3129 > URL: https://issues.apache.org/jira/browse/ATLAS-3129 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.1.0 >Reporter: Rajkumar Singh >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-3129-2.patch > > > AtlasBaseClient uses Hadoop's SSLFactory to create the > ReloadingX509TrustManager > https://github.com/apache/atlas/blob/b919d3d0964efbe1eda40724545d5fa506100a02/client/common/src/main/java/org/apache/atlas/security/SecureClientUtils.java#L143 > currently, there is no way to stop/destroy method of the > ReloadingX509TrustManager, this creates "Truststore reloader thread" leak in > hiveserver2 if the user is running any HOOK/UDF which uses the AtlasClient. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2890) Fix intermittent UT and IT failures for atlas in apache CI
[ https://issues.apache.org/jira/browse/ATLAS-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2890: -- Labels: (was: release-notes) > Fix intermittent UT and IT failures for atlas in apache CI > -- > > Key: ATLAS-2890 > URL: https://issues.apache.org/jira/browse/ATLAS-2890 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 0.8.2, 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: > 0001-ATLAS-2890-Fix-intermittent-UT-and-IT-failures-for-a.patch > > > We see intermittent test failures in > [https://builds.apache.org/view/A/view/Atlas/] > This Jira addresses fixes for these intermittent failures in branch-0.8, > branch-1.0 and master -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3091) AtlasGraphProvider: Allow for Creation of JanusGraph DB Connection Initialized with Batch Loading Enabled
[ https://issues.apache.org/jira/browse/ATLAS-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3091: -- Labels: (was: release-notes) > AtlasGraphProvider: Allow for Creation of JanusGraph DB Connection > Initialized with Batch Loading Enabled > - > > Key: ATLAS-3091 > URL: https://issues.apache.org/jira/browse/ATLAS-3091 > Project: Atlas > Issue Type: Improvement >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 2.0.0, trunk > > Attachments: > ATLAS-3091-AtlasGraphProvider-supports-graph-with-ba.patch > > > *Background* > _JanusGraph_ provides improved performance when _batch-loading_. This mode > provides improved performance when large amounts of data has to be written to > the database. > *Solution Guidance* > Use the existing _AtlasJanusGraphDatabase.getBulkLoadingGraphInstance_ to be > returned via _AtlasGraphProvider_. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2771) Add option to exclude internal types when using GET all types using getAllTypeDefs()
[ https://issues.apache.org/jira/browse/ATLAS-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2771: -- Labels: (was: release-notes) > Add option to exclude internal types when using GET all types using > getAllTypeDefs() > > > Key: ATLAS-2771 > URL: https://issues.apache.org/jira/browse/ATLAS-2771 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: > 0001-ATLAS-2771-Add-option-to-exclude-internal-types-when.patch > > > Add option to exclude internal types when using GET all types using > getAllTypeDefs() -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2980) fix HBaseBasedAuditRepository.putEventsV2() to store entity-json string
[ https://issues.apache.org/jira/browse/ATLAS-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2980: -- Labels: (was: release-notes) > fix HBaseBasedAuditRepository.putEventsV2() to store entity-json string > > > Key: ATLAS-2980 > URL: https://issues.apache.org/jira/browse/ATLAS-2980 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.0.0, 1.1.0 >Reporter: Madhan Neethiraj >Assignee: Sizhong Du >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-2980.patch > > > HBaseBasedAuditRepository.putEventsV2() currently stores entity.toString() > value in audit record field 'definition'. This should be fixed to store JSON > string of the entity, since the listEventsV2() API interprets the > 'definition' field value as JSON to convert into AtlasEntity. > Issue was reported and patch provided via pull request > https://github.com/apache/atlas/pull/19/commits, by TomDu. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2797) Atlas Cluster Entity
[ https://issues.apache.org/jira/browse/ATLAS-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2797: -- Labels: (was: release-notes) > Atlas Cluster Entity > > > Key: ATLAS-2797 > URL: https://issues.apache.org/jira/browse/ATLAS-2797 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 0.8.3 >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 0.8.3, 1.2.0, 2.0.0 > > Attachments: ATLAS-2797-Atlas-Cluster.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Background > > In cases where Atlas data is synchronized to other Atlas clusters, it is > necessary to store some information about the nature of operation. > > REST APIs to access this entity should be available as these can be used to > fetch data about the cluster entity. > > Use cases: > * Scenario: Data generated by Export operation on one cluster (say cl1) can > be used to Import into another cluster (say cl2). This operation will result > in data such at AtlasImportResult that can be used later for performing > subsequent operations or for audits. The AtlasCluster entity will be a good > home for this data. REST APIs on AtlasCluster can be used for retrieveing > this data. > > Approach guidance: > * Create AtlasCluster entity. > * Create ClusterService that will use the OGM framework within Atlas to aid > with save and load operations -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2905) Generate lineage information for process entities
[ https://issues.apache.org/jira/browse/ATLAS-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2905: -- Labels: (was: release-notes) > Generate lineage information for process entities > - > > Key: ATLAS-2905 > URL: https://issues.apache.org/jira/browse/ATLAS-2905 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 0.8.2, 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: > 0001-ATLAS-2905-Generate-lineage-information-for-process.1-branch-0.8.patch, > 0001-ATLAS-2905-Generate-lineage-information-for-process.1.patch > > > Currently lineage information is generated only for DataSet entities and its > derivatives. Lineage information should also be generated for Process > entities and in UI lineage tab should be enabled for any process entities and > lineage rendered. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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 ] Carol Drummond updated ATLAS-2708: -- Labels: (was: release-notes) > 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, 2.0.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 (v8.3.4#803005)
[jira] [Updated] (ATLAS-2927) Update lineage query for Process entities
[ https://issues.apache.org/jira/browse/ATLAS-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2927: -- Labels: (was: release-notes) > Update lineage query for Process entities > - > > Key: ATLAS-2927 > URL: https://issues.apache.org/jira/browse/ATLAS-2927 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: > 0001-ATLAS-2927-Update-lineage-query-for-Process-entities-branch-0.8.patch > > > Currently lineage query for process entities generates lineage based on the > number of hops on process entities. Lineage should be generated based on the > hops on DataSet entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3146) UI : Toggle N/A values in relationship and property tables.
[ https://issues.apache.org/jira/browse/ATLAS-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3146: -- Labels: (was: release-notes) > UI : Toggle N/A values in relationship and property tables. > --- > > Key: ATLAS-3146 > URL: https://issues.apache.org/jira/browse/ATLAS-3146 > Project: Atlas > Issue Type: Improvement >Reporter: Binit Gutka >Assignee: Binit Gutka >Priority: Trivial > Fix For: 2.0.0, trunk > > Attachments: ATLAS-3146.patch, ATLAS-3146_1.patch > > > In Property and Relationship tables: > Now the tables show all the data, which includes rows which have no values > and are represented by N/A. > From an end users point view the above values are not crucial. > > Acceptance Criteria: > Have a toggle button on both the tables which will toggle the views i.e. show > and hide the N/A values > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2942) Audit tab changes to display proper data on detail modal view
[ https://issues.apache.org/jira/browse/ATLAS-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2942: -- Labels: (was: release-notes) > Audit tab changes to display proper data on detail modal view > - > > Key: ATLAS-2942 > URL: https://issues.apache.org/jira/browse/ATLAS-2942 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8.2 >Reporter: Abhishek Kadam >Assignee: Abhishek Kadam >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-2942_Master.patch, ATLAS-2942_branch_0.8.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3097) Missing AtlasRelationshipDef constructors for serviceType
[ https://issues.apache.org/jira/browse/ATLAS-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3097: -- Labels: pull-request-available (was: pull-request-available release-notes) > Missing AtlasRelationshipDef constructors for serviceType > - > > Key: ATLAS-3097 > URL: https://issues.apache.org/jira/browse/ATLAS-3097 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 2.0.0 > Environment: All the OS >Reporter: Diego Marino Monetti >Priority: Major > Labels: pull-request-available > Fix For: 1.2.0, 2.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > As for AtlasEntityDef the AtlasRelationshipDef ctors for serviceType are > missing -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2957) Fix and enable disabled StormHook Integrations Tests
[ https://issues.apache.org/jira/browse/ATLAS-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2957: -- Labels: (was: release-notes) > Fix and enable disabled StormHook Integrations Tests > > > Key: ATLAS-2957 > URL: https://issues.apache.org/jira/browse/ATLAS-2957 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 1.2.0, trunk >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.2.0, 2.0.0, trunk > > > Fix and enable disabled StormHook Integrations Tests -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2941) Add schema rendering attribute for rdbms type
[ https://issues.apache.org/jira/browse/ATLAS-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2941: -- Labels: (was: release-notes) > Add schema rendering attribute for rdbms type > - > > Key: ATLAS-2941 > URL: https://issues.apache.org/jira/browse/ATLAS-2941 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-2941.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2780) Update AtlasAdminClient to accept username/password via cmdline
[ https://issues.apache.org/jira/browse/ATLAS-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2780: -- Labels: (was: release-notes) > Update AtlasAdminClient to accept username/password via cmdline > --- > > Key: ATLAS-2780 > URL: https://issues.apache.org/jira/browse/ATLAS-2780 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.1.0, 2.0.0 > > > Currently the code doesn't accept the username, password via cmdline options. > > This change will allow a user to specify the combo using -u : -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2843) Atlas Client Support for Export & Import APIs: Change Signature to Support Streams
[ https://issues.apache.org/jira/browse/ATLAS-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2843: -- Labels: (was: release-notes) > Atlas Client Support for Export & Import APIs: Change Signature to Support > Streams > -- > > Key: ATLAS-2843 > URL: https://issues.apache.org/jira/browse/ATLAS-2843 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8.3 >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 0.8.3, 1.2.0, 2.0.0 > > Attachments: > ATLAS-2843-AtlasClient-updates-for-exportData-and-im.patch > > > *Background* > Existing implementation of _AtlasClient.exportData and > AtlasClient.importData_ converts the stream returned by the REST APIs to > _byte_ array and then passes it on to the caller. > In case of _importData_ with absolute file path, it converts it to byte array > and then writes the bytes to the file. > This is inefficient from memory perspective and may cause problems on > client-side if the data is large. > *Solution* > * The APIs should return streams. > * The API that writes file, should implement a version that works with > streams. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (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:all-tabpanel ] Carol Drummond updated ATLAS-2744: -- Labels: (was: release-notes) > 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-4.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 (v8.3.4#803005)
[jira] [Updated] (ATLAS-2743) Create Entity UI renders Name and QualifiedName attribute textfield twice for Avrotype.
[ https://issues.apache.org/jira/browse/ATLAS-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2743: -- Labels: (was: release-notes) > Create Entity UI renders Name and QualifiedName attribute textfield twice for > Avrotype. > --- > > Key: ATLAS-2743 > URL: https://issues.apache.org/jira/browse/ATLAS-2743 > Project: Atlas > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Nixon Rodrigues >Assignee: Nixon Rodrigues >Priority: Major > Fix For: 1.2.0, 2.0.0 > > Attachments: ATLAS-2743.patch, Avro-Type.png > > > !Avro-Type.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2820) UI : Add replication audits tab for AtlasCluster entity to show Export & Import audit
[ https://issues.apache.org/jira/browse/ATLAS-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2820: -- Labels: (was: release-notes) > UI : Add replication audits tab for AtlasCluster entity to show Export & > Import audit > - > > Key: ATLAS-2820 > URL: https://issues.apache.org/jira/browse/ATLAS-2820 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.8.3 >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 0.8.3, 1.2.0, 2.0.0 > > Attachments: ATLAS-2820-1.patch, ATLAS-2820-WIP.patch, > ATLAS-2820-master.patch, ATLAS-2820.patch > > > Add Replication Audits tab in detail page if entity typename is > "*AtlasCluster*". > inside tab show list of audits in table structure using this new API. > /api/atlas/admin/expimp/audit?sourceClusterName= -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2906) Import Process: Transforms: Handling Custom Attributes Does Not Update
[
https://issues.apache.org/jira/browse/ATLAS-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carol Drummond updated ATLAS-2906:
--
Labels: (was: release-notes)
> Import Process: Transforms: Handling Custom Attributes Does Not Update
> --
>
> Key: ATLAS-2906
> URL: https://issues.apache.org/jira/browse/ATLAS-2906
> Project: Atlas
> Issue Type: Bug
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 1.2.0, 2.0.0
>
> Attachments:
> ATLAS-2906-Allow-transforms-to-be-applied-when-entit.patch
>
>
> *Background*
> The new transform framework looks at the entity holistically and computes
> attributes as it sees fit.
> Updating the _hive_storagedesc.location_ if entity-level transform is
> present, does not apply the transform.
> *Steps* *to Duplicate*
> * Attempt to import a zip file with the following transform.
> {code:java}
> { "options": { "transformers": "[{\"conditions\":{\"__entity\":\"topLevel:
> \"},\"action\":{\"__entity\":\"ADD_CLASSIFICATION:
> mycluster0_replicated\"}},{\"action\":{\"__entity.replicatedTo\":\"CLEAR:\",\"__entity.replicatedFrom\":\"CLEAR:\"}},{\"conditions\":{\"hive_db.clusterName\":\"EQUALS:
> mycluster0\"},\"action\":{\"hive_db.clusterName\":\"SET:
> mycluster1\"}},{\"conditions\":{\"hive_storagedesc.location\":\"STARTS_WITH_IGNORE_CASE:
>
> hdfs://localhost.localdomain\"},\"action\":{\"hive_storagedesc.location\":\"REPLACE_PREFIX:
> = :hdfs://localhost.localdomain=hdfs://mycluster1\"}}]", "replicatedFrom":
> "SFO$clx" } }
> {code}
> Locate any entity of type _hive_storagedesc_ and note the _location._ It does
> not apply the updated location.
> *Root Cause*
> * The new transform framework re-computes the location based on cached data.
> * Solution: Prevent caching of this attribute so that it honors the
> externally set transformation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-2754) UI - Atlas front end fail to show the input and output entity
[ https://issues.apache.org/jira/browse/ATLAS-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2754: -- Labels: (was: release-notes) > UI - Atlas front end fail to show the input and output entity > - > > Key: ATLAS-2754 > URL: https://issues.apache.org/jira/browse/ATLAS-2754 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Tejas Rawool >Assignee: Abhishek Kadam >Priority: Critical > Fix For: 1.1.0, 2.0.0 > > Attachments: ATLAS-2754.patch, ATLAS-2754_1.patch, Screen Shot > 2018-06-08 at 4.14.53 PM.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-2817) Update to JanusGraph 0.3.x
[ https://issues.apache.org/jira/browse/ATLAS-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-2817: -- Labels: (was: release-notes) > Update to JanusGraph 0.3.x > -- > > Key: ATLAS-2817 > URL: https://issues.apache.org/jira/browse/ATLAS-2817 > Project: Atlas > Issue Type: Improvement >Reporter: Apoorv Naik >Assignee: Apoorv Naik >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: 0001-Janusgraph-update-to-0.3.0.patch > > > There are couple of index related improvements in this version which helps > resolve the slowness in few of our DSL queries. This upgrade would speed up > DSL execution. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3044) Notifications are not sent for entities deleted during import
[ https://issues.apache.org/jira/browse/ATLAS-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carol Drummond updated ATLAS-3044: -- Labels: (was: release-notes) > Notifications are not sent for entities deleted during import > - > > Key: ATLAS-3044 > URL: https://issues.apache.org/jira/browse/ATLAS-3044 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.0.0, 0.8.3, 1.1.0, 2.0.0 >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 0.8.4, 1.2.0, 2.0.0 > > Attachments: ATLAS-3044-branch-0.8.patch, ATLAS-3044.patch > > > For entities marked as deleted in import file, the import process updates the > entity status as deleted; however, such entities are not taken through > entity-delete flow - which results in no notifications getting generated for > deleted entities. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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
]
Carol Drummond updated ATLAS-641:
-
Labels: (was: release-notes)
> 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
(v8.3.4#803005)
