[jira] [Resolved] (ATLAS-3086) Regression : Atlas Hive Hook doesn't capture insert into table values() queries
[ https://issues.apache.org/jira/browse/ATLAS-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-3086. - Resolution: Fixed > Regression : Atlas Hive Hook doesn't capture insert into table values() > queries > --- > > Key: ATLAS-3086 > URL: https://issues.apache.org/jira/browse/ATLAS-3086 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Sharmadha Sainath >Priority: Major > Fix For: trunk > > > Atlas Hive Hook doesn't capture the query "insert into table values()" . This > is a regression as this event was captured in 0.8 > Other queries like > "from table1 a insert overwrite table bkp_table select a.id", > "insert into tableB select c1,c2 from tableA" , information is captured and > lineage is created in 1.0 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (ATLAS-3396) ZipSource: Usage of In-memory Maps Limits the Size of Imports Performed
[ https://issues.apache.org/jira/browse/ATLAS-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928885#comment-16928885 ] ASF subversion and git services commented on ATLAS-3396: Commit e6b9e9ad25b3b0538c0f864ab534cd16e9dd91b9 in atlas's branch refs/heads/master from Ashutosh Mestry [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e6b9e9a ] ATLAS-3396: ZipSourceWithBackingStore implementation. Empty ZIP unit test fix. > ZipSource: Usage of In-memory Maps Limits the Size of Imports Performed > --- > > Key: ATLAS-3396 > URL: https://issues.apache.org/jira/browse/ATLAS-3396 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8.4 >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 0.8.4, trunk > > Attachments: > ATLAS-3396-ZipSource-Memory-usage-improvement-for-la-branch-0.8.patch, > ATLAS-3396-ZipSourceWithBackingDirectory-Implementat-master.patch > > > *Background* > _ZipSource_ is the container for working with Atlas-exported ZIP files. The > current implementation fetches the contents of the entire ZIP file in memory. > This greatly limits the size of ZIP files that can be imported. > *Solution Guidance* > New class _ZipSourceWIthBackingDirectory_, this will use a user-specified (or > default) temporary directory to preserve the contents of the ZIP file. This > will reduce the memory burden and large ZIP files can be imported. > Minor refactoring to _ImportService_ will be necessary to support the new > variation of _EntityImportStream._ > -- This message was sent by Atlassian Jira (v8.3.2#803003)
Re: [DRAFT] Board report for Apache Atlas: September 2019
Nixon - thanks for reviewing the report and the suggestion. I will update the report to include keycloak authentication support. Thanks, Madhan On 9/12/19, 2:40 AM, "Nixon Rodrigues" wrote: Thanks Madhan for putting this together. Can you review and add ( ATLAS-3153 :- Add Keycloak authentication method to Atlas.) Looks good to me, +1 for the draft. Regards, Nixon On Thu, Sep 12, 2019 at 7:48 AM Madhan Neethiraj wrote: > Atlas team, > > Please review the draft board report below and send your feedback/comments. > > Thanks, > Madhan > > > ## Description: > Apache Atlas is a scalable and extensible set of core foundational > governance services that enables enterprises to effectively and > efficiently > meet their compliance requirements within Hadoop and allows integration > with > the complete enterprise data ecosystem > > ## Issues: > There are no issues requiring board attention at this time. > > ## Activity: > - released 0.8.4 maintenance version > - added quick-search functionality, for a simpler search interface > - enhanced notification processing to handle multiple Kafka topics > - updated hook and bridges to replace object-type attributes with > relationships > - added support for dynamic attributes, whose value is derived from > value of other attribute(s) > - enhancements to handle references to non-existing entities during > notification processing > - performance improvements in import/export functionality > - working on upgrading JanusGraph version to the most recent release, > 0.4.0 > > ## Health report: > - 3 new contributors added in last 3 months: Bolke, Sameer, SJQ > > ## PMC changes: > - Currently 34 PMC members > - Last addition to PMC role was on 5/13/2019 > > ## Committer base changes: > - Currently 38 committers > - No new committers added in last 3 months > - Last addition to committer role was on 10/15/2018 > > ## Releases: > 0.8.4was released on 06/21/2019 > 1.2.0was released on 06/12/2019 > 2.0.0was released on 05/14/2019 > 0.8.3was released on 10/31/2018 > 1.1.0was released on 09/17/2018 > 1.0.0was released on 06/02/2018 > 0.8.2was released on 02/05/2018 > 1.0.0-alpha was released on 01/25/2018 > 0.8.1was released on 08/29/2017 > 0.8-incubating was released on 03/16/2017 > 0.7.1-incubating was released on 01/26/2017 > 0.7-incubating was released on 07/09/2016 > 0.6-incubating was released on 12/31/2015 > 0.5-incubating was released on 07/11/2015 > > > > > > > >
Fwd: Outstanding review requests (patches!)
Ping! I wonder what to do to grab some attention, because I see there is even some duplication of effort going on now - ATLAS-3399 is partially duplicated ATLAS-3378 which did receive reviews quickly? Do I need to add reviewers? I do think the added functionality is worthwhile and will benefit others too, but please let me know if those patches don’t make sense. Thanks for responding. Bolke On 4 September 2019 at 14:47:41, Bolke de Bruin (bdbr...@gmail.com) wrote: Hello Team! I have some outstanding review requests and I would appreciate feedback or (duh) merging. Can someone take a look: * Add order by (sort) to basic search : https://reviews.apache.org/r/71431/ * Use fulltext indices for dsl search : https://reviews.apache.org/r/71344/ (Received one “ship it!”, no further action) * Expose total count of index searches : https://reviews.apache.org/r/71282/ * Set log level to warn for relationships without relationship definition : https://reviews.apache.org/r/71278/. (This one is under review) Thanks! Bolke
[jira] [Commented] (ATLAS-3409) Remove the duplicate code in Solr6Index.
[ https://issues.apache.org/jira/browse/ATLAS-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928633#comment-16928633 ] Bolke de Bruin commented on ATLAS-3409: --- This is a duplicate of atlas-3397 > Remove the duplicate code in Solr6Index. > > > Key: ATLAS-3409 > URL: https://issues.apache.org/jira/browse/ATLAS-3409 > Project: Atlas > Issue Type: Improvement >Reporter: Sridhar >Assignee: Sridhar >Priority: Major > > Historically, we made a copy of SolrIndex from Janus graph and referred to it > as Solr6Index. Over time, SolrIndex in janus graph has mode enough progress > w.r.t Kerberos support etc. So, we should remove the duplicate code > Solr6Index. > This ticket should be done after ATLAS-3378 is completed. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (ATLAS-3403) Term assigned to historical entity is not visible in Search results page.
[ https://issues.apache.org/jira/browse/ATLAS-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-3403: -- Assignee: (was: Keval Bhatt) > Term assigned to historical entity is not visible in Search results page. > - > > Key: ATLAS-3403 > URL: https://issues.apache.org/jira/browse/ATLAS-3403 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Minor > > Let us consider that a classification and a term has been assigned to an > entity. > If that entity is deleted, and then when the "Show Historical Entities" > filter is enabled on the search results page for that entity, the > classification is displayed but not the term. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (ATLAS-3403) Term assigned to historical entity is not visible in Search results page.
[ https://issues.apache.org/jira/browse/ATLAS-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-3403: -- Assignee: Keval Bhatt > Term assigned to historical entity is not visible in Search results page. > - > > Key: ATLAS-3403 > URL: https://issues.apache.org/jira/browse/ATLAS-3403 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Keval Bhatt >Priority: Minor > > Let us consider that a classification and a term has been assigned to an > entity. > If that entity is deleted, and then when the "Show Historical Entities" > filter is enabled on the search results page for that entity, the > classification is displayed but not the term. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (ATLAS-3403) Term assigned to historical entity is not visible in Search results page.
[ https://issues.apache.org/jira/browse/ATLAS-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3403: --- Summary: Term assigned to historical entity is not visible in Search results page. (was: UI: Term assigned to historical entity is not visible in Search results page.) > Term assigned to historical entity is not visible in Search results page. > - > > Key: ATLAS-3403 > URL: https://issues.apache.org/jira/browse/ATLAS-3403 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Keval Bhatt >Priority: Minor > > Let us consider that a classification and a term has been assigned to an > entity. > If that entity is deleted, and then when the "Show Historical Entities" > filter is enabled on the search results page for that entity, the > classification is displayed but not the term. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (ATLAS-3410) Term assigned to historical entity is not visible in Details page.
[ https://issues.apache.org/jira/browse/ATLAS-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-3410: -- Assignee: Keval Bhatt > Term assigned to historical entity is not visible in Details page. > -- > > Key: ATLAS-3410 > URL: https://issues.apache.org/jira/browse/ATLAS-3410 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Keval Bhatt >Priority: Minor > > This issue is related to an earlier one (ATLAS-3403). When a entity with a > term associated to it is deleted, and if you navigate to the Details page for > that entity, the classification is displayed but not the term. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (ATLAS-3411) Relationships : Having multiple relationships on the same attribute
[ https://issues.apache.org/jira/browse/ATLAS-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928399#comment-16928399 ] Mandar Ambawane commented on ATLAS-3411: 1.Created 2 association relationships between 2 types using the same attribute "rel_attribute". 2.Created entities with the first relationship . Relationship is created successfully. 3. In the entitydef of entity1 , "rel_attribute" is not found in both relatedAttributes / attributes. But in entitydef of entity2 "rel_attribute" is found which contains entity1 information. This happens only when multiple relations are created on the same attribute. Repro steps (Attached the payloads) : 1. Create types by posting multi_entity_types.json (to create entity types) and multi_relationships.json (to create relationship typedefs) to v2/types/typedefs 2. Create entities by POSTing multi_entities.json to /v2/entity/bulk 3.Create relationship between the entities by POSTing the multi_relationship_instance.json to /v2/relationship (entity guids to be modified) In entity1's entitydef, it can be seen that "rel_attirbute" is not present at all though the relationship guid is defined between entity1 and entity2. > Relationships : Having multiple relationships on the same attribute > --- > > Key: ATLAS-3411 > URL: https://issues.apache.org/jira/browse/ATLAS-3411 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (ATLAS-3411) Relationships : Having multiple relationships on the same attribute
Mandar Ambawane created ATLAS-3411: -- Summary: Relationships : Having multiple relationships on the same attribute Key: ATLAS-3411 URL: https://issues.apache.org/jira/browse/ATLAS-3411 Project: Atlas Issue Type: Bug Reporter: Mandar Ambawane Assignee: Mandar Ambawane -- This message was sent by Atlassian Jira (v8.3.2#803003)
