[jira] [Resolved] (ATLAS-3749) Atlas UI Changes for Admin Audit
[ https://issues.apache.org/jira/browse/ATLAS-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt resolved ATLAS-3749. Resolution: Fixed > Atlas UI Changes for Admin Audit > - > > Key: ATLAS-3749 > URL: https://issues.apache.org/jira/browse/ATLAS-3749 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3749) Atlas UI Changes for Admin Audit
[ https://issues.apache.org/jira/browse/ATLAS-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3749: --- Fix Version/s: 3.0.0 2.1.0 > Atlas UI Changes for Admin Audit > - > > Key: ATLAS-3749 > URL: https://issues.apache.org/jira/browse/ATLAS-3749 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3761) UI: Show progress bar for migration page
[ https://issues.apache.org/jira/browse/ATLAS-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3761: --- Fix Version/s: (was: 2.1.0) > UI: Show progress bar for migration page > > > Key: ATLAS-3761 > URL: https://issues.apache.org/jira/browse/ATLAS-3761 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 3.0.0 > > Attachments: ATLAS-3761.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3761) UI: Show progress bar for migration page
[ https://issues.apache.org/jira/browse/ATLAS-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17095091#comment-17095091 ] ASF subversion and git services commented on ATLAS-3761: Commit b4246817251429ec986e9f4a37adca7cf334a2a4 in atlas's branch refs/heads/master from Keval Bhatt [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b424681 ] ATLAS-3761:- UI: Show progress bar for migration page > UI: Show progress bar for migration page > > > Key: ATLAS-3761 > URL: https://issues.apache.org/jira/browse/ATLAS-3761 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3761.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3762) Entity Creation: Improve Vertices and Edges Fetch Using Genuine Iterators
[ https://issues.apache.org/jira/browse/ATLAS-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3762: --- Description: *Background* One of the earlier commits replaced vertices and edges fetch with _StreamSupport.stream_. This uses _Collect(toList),_ which causes all contents to be fetched. Using this causes large amount of data to be fetched. *Solution* Switch to iterators that will use lazy loading. *Minor Refactoring* Change the _getEdge_ to iterate on smaller dataset. [~sidharthkmishra] Thanks for this simple but effective fix. was: *Background* One of the earlier commits replaced vertices and edges fetch with _StreamSupport.stream_. This uses _Collect(toList),_ which causes all contents to be fetched. Using this causes large amount of data to be fetched. *Solution* Switch to iterators that will use lazy loading. *Minor Refactoring* Change the _getEdge_ to iterate on smaller dataset. > Entity Creation: Improve Vertices and Edges Fetch Using Genuine Iterators > - > > Key: ATLAS-3762 > URL: https://issues.apache.org/jira/browse/ATLAS-3762 > Project: Atlas > Issue Type: Improvement >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: ATLAS-3762-iterators-improvement.patch > > > *Background* > One of the earlier commits replaced vertices and edges fetch with > _StreamSupport.stream_. This uses _Collect(toList),_ which causes all > contents to be fetched. > Using this causes large amount of data to be fetched. > *Solution* > Switch to iterators that will use lazy loading. > *Minor Refactoring* > Change the _getEdge_ to iterate on smaller dataset. > [~sidharthkmishra] Thanks for this simple but effective fix. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3759) altas can't updata Lineage image
[ https://issues.apache.org/jira/browse/ATLAS-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17094989#comment-17094989 ] lijialong commented on ATLAS-3759: -- [~kevalbhatt] how can I show you the API response？ > altas can't updata Lineage image > > > Key: ATLAS-3759 > URL: https://issues.apache.org/jira/browse/ATLAS-3759 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8.4 >Reporter: lijialong >Priority: Major > Fix For: 0.8.4 > > Attachments: image-2020-04-28-20-34-48-147.png > > > it always show like this, I use hive : Insert overwirte table a select xxx > from b > !image-2020-04-28-20-34-48-147.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Review Request 72446: Optimize FreeTextSearchProcessor to apply exclude deleted entity filter on solr side.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72446/#review220535 --- Ship it! @damian.warszaw...@gmail.com - the updates look good! Thanks for the patch. - Madhan Neethiraj On April 28, 2020, 9:25 p.m., Damian Warszawski wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/72446/ > --- > > (Updated April 28, 2020, 9:25 p.m.) > > > Review request for atlas, Ashutosh Mestry, Bolke de Bruin, madhan, and Sarath > Subramanian. > > > Repository: atlas > > > Description > --- > > Current implementation of FreeTextSearchProcessor applies filtering in memory > to exclude deleted entities. This introduces significant performance overhead > by generating redundant calls to solr index. The goal is to improve > performance of FreeTextSearchProcessor by applying filter in solr query. > > > Diffs > - > > > repository/src/main/java/org/apache/atlas/discovery/FreeTextSearchProcessor.java > 92b5eb4d2 > > > Diff: https://reviews.apache.org/r/72446/diff/1/ > > > Testing > --- > > Verified on our dev env and achieved 10x faster response for simple call to > atlas basic search with over 50k entities. > > > Thanks, > > Damian Warszawski > >
[jira] [Updated] (ATLAS-3762) Entity Creation: Improve Vertices and Edges Fetch Using Genuine Iterators
[ https://issues.apache.org/jira/browse/ATLAS-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3762: --- Attachment: ATLAS-3762-iterators-improvement.patch > Entity Creation: Improve Vertices and Edges Fetch Using Genuine Iterators > - > > Key: ATLAS-3762 > URL: https://issues.apache.org/jira/browse/ATLAS-3762 > Project: Atlas > Issue Type: Improvement >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: ATLAS-3762-iterators-improvement.patch > > > *Background* > One of the earlier commits replaced vertices and edges fetch with > _StreamSupport.stream_. This uses _Collect(toList),_ which causes all > contents to be fetched. > Using this causes large amount of data to be fetched. > *Solution* > Switch to iterators that will use lazy loading. > *Minor Refactoring* > Change the _getEdge_ to iterate on smaller dataset. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3762) Entity Creation: Improve Vertices and Edges Fetch Using Genuine Iterators
[ https://issues.apache.org/jira/browse/ATLAS-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3762: --- Summary: Entity Creation: Improve Vertices and Edges Fetch Using Genuine Iterators (was: Entity Creation: Improve Vertices and Edges Fetch Using Real Iterators) > Entity Creation: Improve Vertices and Edges Fetch Using Genuine Iterators > - > > Key: ATLAS-3762 > URL: https://issues.apache.org/jira/browse/ATLAS-3762 > Project: Atlas > Issue Type: Improvement >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > > *Background* > One of the earlier commits replaced vertices and edges fetch with > _StreamSupport.stream_. This uses _Collect(toList),_ which causes all > contents to be fetched. > Using this causes large amount of data to be fetched. > *Solution* > Switch to iterators that will use lazy loading. > *Minor Refactoring* > Change the _getEdge_ to iterate on smaller dataset. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3762) Entity Creation: Improve Vertices and Edges Fetch Using Real Iterators
Ashutosh Mestry created ATLAS-3762: -- Summary: Entity Creation: Improve Vertices and Edges Fetch Using Real Iterators Key: ATLAS-3762 URL: https://issues.apache.org/jira/browse/ATLAS-3762 Project: Atlas Issue Type: Improvement Reporter: Ashutosh Mestry Assignee: Ashutosh Mestry *Background* One of the earlier commits replaced vertices and edges fetch with _StreamSupport.stream_. This uses _Collect(toList),_ which causes all contents to be fetched. Using this causes large amount of data to be fetched. *Solution* Switch to iterators that will use lazy loading. *Minor Refactoring* Change the _getEdge_ to iterate on smaller dataset. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Review Request 72446: Optimize FreeTextSearchProcessor to apply exclude deleted entity filter on solr side.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72446/ --- Review request for atlas and Bolke de Bruin. Repository: atlas Description --- Current implementation of FreeTextSearchProcessor applies filtering in memory to exclude deleted entities. This introduces significant performance overhead by generating redundant calls to solr index. The goal is to improve performance of FreeTextSearchProcessor by applying filter in solr query. Diffs - repository/src/main/java/org/apache/atlas/discovery/FreeTextSearchProcessor.java 92b5eb4d2 Diff: https://reviews.apache.org/r/72446/diff/1/ Testing --- Verified on our dev env and achieved 10x faster response for simple call to atlas basic search with over 50k entities. Thanks, Damian Warszawski
[GitHub] [atlas] AmeerAssi commented on pull request #98: Today AWS scheme is missing the aws account id that contains the S3 bucket.
AmeerAssi commented on pull request #98: URL: https://github.com/apache/atlas/pull/98#issuecomment-620852203 So we are using Atlas models in our product. the product gives scan capabilities for customer's S3 in AWS. when scan result shown based on the model, it is missing for which account this bucket belongs. so it will be easy to access the account and review the scanned information by the customer. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: Review Request 72440: Support sort params for FreeTextSearchProcessor
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72440/ --- (Updated April 28, 2020, 8:59 p.m.) Review request for atlas, Ashutosh Mestry, Bolke de Bruin, Madhan Neethiraj, and Sarath Subramanian. Repository: atlas Description --- No way to sort results by specified attribute while freetext search is enabled. In our case we would like to enforce ordering by introducing custom attribute definition e.g. popularity score from https://github.com/dwarszawski/amundsen-atlas-types/blob/master/amundsenatlastypes/schema/01_2_table_schema.json Diffs - repository/src/main/java/org/apache/atlas/discovery/EntitySearchProcessor.java 1a7bf6b16 repository/src/main/java/org/apache/atlas/discovery/FreeTextSearchProcessor.java 92b5eb4d2 repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 11eb7ca49 Diff: https://reviews.apache.org/r/72440/diff/1/ Testing --- Patch was applied on our dev env with custom entity definitions and successfully verified if order is applied as specified in the search query. Thanks, Damian Warszawski
Re: Review Request 72441: Support solr in standalone (http) mode
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72441/ --- (Updated April 28, 2020, 8:58 p.m.) Review request for atlas, Ashutosh Mestry, Bolke de Bruin, madhan, and Sarath Subramanian. Repository: atlas Description --- Atlas does not support running Solr in standalone(http) mode. It is especially useful for testing purposes to make setup as simple as possible without Zookeeper. It also enables full integration with JanusGraph as it support both mode of running Solr `cloud` and `http` https://docs.janusgraph.org/index-backend/solr/. Additional benefit is to decouple hbase and solr while running embedded mode so that solr can be run in embbeded mode with external hbase. Proposed solution call solr V1 API while creating/updating request handlers in standalone solr update atlas start script to enable standalone embedded solr Diffs - distro/src/bin/atlas_config.py f09026ff9 graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusGraphIndexClient.java ba65f3d00 graphdb/janus/src/main/java/org/janusgraph/diskstorage/solr/Solr6Index.java 484c161f0 Diff: https://reviews.apache.org/r/72441/diff/1/ Testing --- Patch was applied and verified on our dev env with embedded solr and external hbase. Thanks, Damian Warszawski
[jira] [Updated] (ATLAS-3760) Optimize FreeTextSearchProcessor to apply exclude deleted entity filter on solr side.
[ https://issues.apache.org/jira/browse/ATLAS-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Warszawski updated ATLAS-3760: - Description: *Problem description* Current implementation of FreeTextSearchProcessor applies filtering in memory to exclude deleted entities. This introduces significant performance overhead by generating redundant calls to solr index. *Goals* Improve performance of FreeTextSearchProcessor by applying filter in solr query. *Proposed solution* * replace in-memory filtering with filter in solr query. > Optimize FreeTextSearchProcessor to apply exclude deleted entity filter on > solr side. > -- > > Key: ATLAS-3760 > URL: https://issues.apache.org/jira/browse/ATLAS-3760 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Damian Warszawski >Priority: Minor > Fix For: 3.0.0 > > > *Problem description* > Current implementation of FreeTextSearchProcessor applies filtering in memory > to exclude deleted entities. > This introduces significant performance overhead by generating redundant > calls to solr index. > *Goals* > Improve performance of FreeTextSearchProcessor by applying filter in solr > query. > *Proposed solution* > * replace in-memory filtering with filter in solr query. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [atlas] sidharthkmishra commented on pull request #98: Today AWS scheme is missing the aws account id that contains the S3 bucket.
sidharthkmishra commented on pull request #98: URL: https://github.com/apache/atlas/pull/98#issuecomment-620785613 As per my understanding accountId is used to construct ARN and it may be used at AWS to distinguish resources. Could you please explain how will this be useful as Atlas metadata and what is the use-case. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (ATLAS-3761) UI: Show progress bar for migration page
[ https://issues.apache.org/jira/browse/ATLAS-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17094718#comment-17094718 ] Nixon Rodrigues commented on ATLAS-3761: +1 for the patch, thanks [~kevalbhatt], will commit it shortly. > UI: Show progress bar for migration page > > > Key: ATLAS-3761 > URL: https://issues.apache.org/jira/browse/ATLAS-3761 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3761.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3761) UI: Show progress bar for migration page
[ https://issues.apache.org/jira/browse/ATLAS-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3761: --- Attachment: ATLAS-3761.patch > UI: Show progress bar for migration page > > > Key: ATLAS-3761 > URL: https://issues.apache.org/jira/browse/ATLAS-3761 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3761.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3761) UI: Show progress bar for migration page
[ https://issues.apache.org/jira/browse/ATLAS-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3761: --- Description: (was: When the migration is going on currently there is no way User would know the progress of the migration. This improvement would help the user to get a migration status details. +In progress Status:+ !image-2020-04-28-22-05-34-083.png|width=567,height=280! +Done Status:+ !image-2020-04-28-22-05-34-020.png|width=575,height=76!) > UI: Show progress bar for migration page > > > Key: ATLAS-3761 > URL: https://issues.apache.org/jira/browse/ATLAS-3761 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3761) UI: Show progress bar for migration page
[ https://issues.apache.org/jira/browse/ATLAS-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3761: --- Attachment: (was: image-2020-04-28-22-05-34-020.png) > UI: Show progress bar for migration page > > > Key: ATLAS-3761 > URL: https://issues.apache.org/jira/browse/ATLAS-3761 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3761) UI: Show progress bar for migration page
[ https://issues.apache.org/jira/browse/ATLAS-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3761: --- Attachment: (was: image-2020-04-28-22-05-34-083.png) > UI: Show progress bar for migration page > > > Key: ATLAS-3761 > URL: https://issues.apache.org/jira/browse/ATLAS-3761 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3761) UI: Show progress bar for migration page
[ https://issues.apache.org/jira/browse/ATLAS-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3761: --- Description: When the migration is going on currently there is no way User would know the progress of the migration. This improvement would help the user to get a migration status details. +In progress Status:+ !image-2020-04-28-22-05-34-083.png|width=567,height=280! +Done Status:+ !image-2020-04-28-22-05-34-020.png|width=575,height=76! > UI: Show progress bar for migration page > > > Key: ATLAS-3761 > URL: https://issues.apache.org/jira/browse/ATLAS-3761 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: image-2020-04-28-22-05-34-020.png, > image-2020-04-28-22-05-34-083.png > > > When the migration is going on currently there is no way User would know the > progress of the migration. > This improvement would help the user to get a migration status details. > +In progress Status:+ > !image-2020-04-28-22-05-34-083.png|width=567,height=280! > +Done Status:+ > !image-2020-04-28-22-05-34-020.png|width=575,height=76! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3761) UI: Show progress bar for migration page
[ https://issues.apache.org/jira/browse/ATLAS-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3761: --- Attachment: image-2020-04-28-22-05-34-020.png > UI: Show progress bar for migration page > > > Key: ATLAS-3761 > URL: https://issues.apache.org/jira/browse/ATLAS-3761 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: image-2020-04-28-22-05-34-020.png, > image-2020-04-28-22-05-34-083.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3761) UI: Show progress bar for migration page
[ https://issues.apache.org/jira/browse/ATLAS-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3761: --- Attachment: image-2020-04-28-22-05-34-083.png > UI: Show progress bar for migration page > > > Key: ATLAS-3761 > URL: https://issues.apache.org/jira/browse/ATLAS-3761 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: image-2020-04-28-22-05-34-020.png, > image-2020-04-28-22-05-34-083.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3761) UI: Show progress bar for migration page
Keval Bhatt created ATLAS-3761: -- Summary: UI: Show progress bar for migration page Key: ATLAS-3761 URL: https://issues.apache.org/jira/browse/ATLAS-3761 Project: Atlas Issue Type: Improvement Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 2.1.0, 3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-3759) altas can't updata Lineage image
[ https://issues.apache.org/jira/browse/ATLAS-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17094547#comment-17094547 ] Keval Bhatt edited comment on ATLAS-3759 at 4/28/20, 2:21 PM: -- [~lijialong] can you share the API response? These image are set based on the entity type. was (Author: kevalbhatt18): [~lijialong] can you share the API response? > altas can't updata Lineage image > > > Key: ATLAS-3759 > URL: https://issues.apache.org/jira/browse/ATLAS-3759 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8.4 >Reporter: lijialong >Priority: Major > Fix For: 0.8.4 > > Attachments: image-2020-04-28-20-34-48-147.png > > > it always show like this, I use hive : Insert overwirte table a select xxx > from b > !image-2020-04-28-20-34-48-147.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3760) Optimize FreeTextSearchProcessor to apply exclude deleted entity filter on solr side.
Damian Warszawski created ATLAS-3760: Summary: Optimize FreeTextSearchProcessor to apply exclude deleted entity filter on solr side. Key: ATLAS-3760 URL: https://issues.apache.org/jira/browse/ATLAS-3760 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Damian Warszawski Fix For: 3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3759) altas can't updata Lineage image
[ https://issues.apache.org/jira/browse/ATLAS-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17094547#comment-17094547 ] Keval Bhatt commented on ATLAS-3759: [~lijialong] can you share the API response? > altas can't updata Lineage image > > > Key: ATLAS-3759 > URL: https://issues.apache.org/jira/browse/ATLAS-3759 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8.4 >Reporter: lijialong >Priority: Major > Fix For: 0.8.4 > > Attachments: image-2020-04-28-20-34-48-147.png > > > it always show like this, I use hive : Insert overwirte table a select xxx > from b > !image-2020-04-28-20-34-48-147.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3759) altas can't updata Lineage image
[ https://issues.apache.org/jira/browse/ATLAS-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lijialong updated ATLAS-3759: - Description: it always show like this, I use hive : Insert overwirte table a select xxx from b !image-2020-04-28-20-27-27-271.png! was: it always show like this, I use hive : Insert overwirte table a select xxx from b !image-2020-04-28-20-27-27-271.png! > altas can't updata Lineage image > > > Key: ATLAS-3759 > URL: https://issues.apache.org/jira/browse/ATLAS-3759 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8.4 >Reporter: lijialong >Priority: Major > Fix For: 0.8.4 > > Attachments: image-2020-04-28-20-34-48-147.png > > > it always show like this, I use hive : Insert overwirte table a select xxx > from b > !image-2020-04-28-20-27-27-271.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3759) altas can't updata Lineage image
[ https://issues.apache.org/jira/browse/ATLAS-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lijialong updated ATLAS-3759: - Attachment: image-2020-04-28-20-34-48-147.png Description: it always show like this, I use hive : Insert overwirte table a select xxx from b !image-2020-04-28-20-34-48-147.png! was: it always show like this, I use hive : Insert overwirte table a select xxx from b !image-2020-04-28-20-27-27-271.png! > altas can't updata Lineage image > > > Key: ATLAS-3759 > URL: https://issues.apache.org/jira/browse/ATLAS-3759 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8.4 >Reporter: lijialong >Priority: Major > Fix For: 0.8.4 > > Attachments: image-2020-04-28-20-34-48-147.png > > > it always show like this, I use hive : Insert overwirte table a select xxx > from b > !image-2020-04-28-20-34-48-147.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3759) altas can't updata Lineage image
lijialong created ATLAS-3759: Summary: altas can't updata Lineage image Key: ATLAS-3759 URL: https://issues.apache.org/jira/browse/ATLAS-3759 Project: Atlas Issue Type: Bug Affects Versions: 0.8.4 Reporter: lijialong Fix For: 0.8.4 it always show like this, I use hive : Insert overwirte table a select xxx from b !image-2020-04-28-20-27-27-271.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
