[jira] [Assigned] (ATLAS-2077) UI Regression : Search using entity and tag filters : filters are not removed on pressing "clear" button
[
https://issues.apache.org/jira/browse/ATLAS-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt reassigned ATLAS-2077:
--
Assignee: Keval Bhatt
> UI Regression : Search using entity and tag filters : filters are not removed
> on pressing "clear" button
> -
>
> Key: ATLAS-2077
> URL: https://issues.apache.org/jira/browse/ATLAS-2077
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>
> 1.Created a hive table.
> 2.Searched the hive_table, with type name = hive_table , filter name =
> table_1. Result table showed the hive_table.
> 3.Clicked clear button which cleared the type name . Now made a query : query
> = table_1.
> 4.This search failed with
> {code}
> {"errorCode":"ATLAS-400-00-029","errorMessage":"EntityFilters specified
> without Type name"}
> {code}
> 5.Same happens with tag filters.
> On clicking clear button , only type name/classification is cleared.
> entity/tag filters are still present and throws exception on next query. As a
> user , I had to search for the same typename , remove the filter and then
> proceed further to not encounter the exception.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Re: Review Request 61825: [ATLAS-2079]: Fix IT failures introduced by ATLAS-2062
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61825/#review183571 --- Ship it! Ship It! - Madhan Neethiraj On Aug. 22, 2017, 10:22 p.m., Sarath Subramanian wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/61825/ > --- > > (Updated Aug. 22, 2017, 10:22 p.m.) > > > Review request for atlas. > > > Bugs: ATLAS-2079 > https://issues.apache.org/jira/browse/ATLAS-2079 > > > Repository: atlas > > > Description > --- > > Fix the following IT failures: > Failed tests: > NotificationHookConsumerIT.testDeleteByQualifiedName:184->BaseResourceIT.waitFor:621 > » AtlasService > NotificationHookConsumerIT.testUpdateEntityPartial:127->BaseResourceIT.waitFor:626 > » > EntityJerseyResourceIT.testPartialUpdate:881 expected:<1> but was:<3> > MetadataDiscoveryJerseyResourceIT.testSearchUsingGremlin:153 » AtlasService > Me... > > > Diffs > - > > > intg/src/main/java/org/apache/atlas/model/instance/EntityMutationResponse.java > 70784363 > intg/src/main/java/org/apache/atlas/type/AtlasEntityType.java 2cb8e274 > pom.xml f127774d > repository/src/main/java/org/apache/atlas/repository/graph/GraphHelper.java > 1ec5a72e > typesystem/src/test/resources/atlas-application.properties 7967b761 > > webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerIT.java > 9c5597ef > > webapp/src/test/java/org/apache/atlas/web/integration/EntityJerseyResourceIT.java > 660f05e1 > > > Diff: https://reviews.apache.org/r/61825/diff/2/ > > > Testing > --- > > The ITs works fine for webapp module. > > > Thanks, > > Sarath Subramanian > >
Re: Review Request 61824: [ATLAS-2078]: Updating types using v1 API doesn't route to createUpdateTypesDef in v2 API
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61824/#review183570 --- Ship it! Ship It! - Madhan Neethiraj On Aug. 22, 2017, 10:09 p.m., Sarath Subramanian wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/61824/ > --- > > (Updated Aug. 22, 2017, 10:09 p.m.) > > > Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, and > Nixon Rodrigues. > > > Bugs: ATLAS-2078 > https://issues.apache.org/jira/browse/ATLAS-2078 > > > Repository: atlas > > > Description > --- > > When updating types using v1 API, if type doesn't exist we create missing > types. Currently this API maps to v2 API's update method and doesn't create > missing types. > > > Diffs > - > > intg/src/main/java/org/apache/atlas/store/AtlasTypeDefStore.java e1c5a7f5 > > repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasTypeDefGraphStore.java > 7a0bbca1 > webapp/src/main/java/org/apache/atlas/web/resources/TypesResource.java > f70593a3 > > > Diff: https://reviews.apache.org/r/61824/diff/1/ > > > Testing > --- > > validated using POSTMAN REST client. > > > Thanks, > > Sarath Subramanian > >
[jira] [Updated] (ATLAS-2079) Fix IT failures introduced by ATLAS-2062
[ https://issues.apache.org/jira/browse/ATLAS-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-2079: -- Attachment: ATLAS-2079.1.patch > Fix IT failures introduced by ATLAS-2062 > > > Key: ATLAS-2079 > URL: https://issues.apache.org/jira/browse/ATLAS-2079 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.9-incubating, 0.8.1-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Minor > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-2079.1.patch > > > Fix for coverity scan issues and following IT failures: > Failed tests: > > NotificationHookConsumerIT.testDeleteByQualifiedName:184->BaseResourceIT.waitFor:621 > » AtlasService > > NotificationHookConsumerIT.testUpdateEntityPartial:127->BaseResourceIT.waitFor:626 > » > EntityJerseyResourceIT.testPartialUpdate:881 expected:<1> but was:<3> > MetadataDiscoveryJerseyResourceIT.testSearchUsingGremlin:153 » > AtlasService Me... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2079) Fix IT failures introduced by ATLAS-2062
[ https://issues.apache.org/jira/browse/ATLAS-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-2079: -- Description: Fix for coverity scan issues and following IT failures: Failed tests: NotificationHookConsumerIT.testDeleteByQualifiedName:184->BaseResourceIT.waitFor:621 » AtlasService NotificationHookConsumerIT.testUpdateEntityPartial:127->BaseResourceIT.waitFor:626 » EntityJerseyResourceIT.testPartialUpdate:881 expected:<1> but was:<3> MetadataDiscoveryJerseyResourceIT.testSearchUsingGremlin:153 » AtlasService Me... was: Fix the following IT failures: Failed tests: NotificationHookConsumerIT.testDeleteByQualifiedName:184->BaseResourceIT.waitFor:621 » AtlasService NotificationHookConsumerIT.testUpdateEntityPartial:127->BaseResourceIT.waitFor:626 » EntityJerseyResourceIT.testPartialUpdate:881 expected:<1> but was:<3> MetadataDiscoveryJerseyResourceIT.testSearchUsingGremlin:153 » AtlasService Me... > Fix IT failures introduced by ATLAS-2062 > > > Key: ATLAS-2079 > URL: https://issues.apache.org/jira/browse/ATLAS-2079 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.9-incubating, 0.8.1-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Minor > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-2079.1.patch > > > Fix for coverity scan issues and following IT failures: > Failed tests: > > NotificationHookConsumerIT.testDeleteByQualifiedName:184->BaseResourceIT.waitFor:621 > » AtlasService > > NotificationHookConsumerIT.testUpdateEntityPartial:127->BaseResourceIT.waitFor:626 > » > EntityJerseyResourceIT.testPartialUpdate:881 expected:<1> but was:<3> > MetadataDiscoveryJerseyResourceIT.testSearchUsingGremlin:153 » > AtlasService Me... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-2079) Fix IT failures introduced by ATLAS-2062
[ https://issues.apache.org/jira/browse/ATLAS-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-2079: -- Attachment: (was: ATLAS-2079.1.patch) > Fix IT failures introduced by ATLAS-2062 > > > Key: ATLAS-2079 > URL: https://issues.apache.org/jira/browse/ATLAS-2079 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.9-incubating, 0.8.1-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Minor > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-2079.1.patch > > > Fix for coverity scan issues and following IT failures: > Failed tests: > > NotificationHookConsumerIT.testDeleteByQualifiedName:184->BaseResourceIT.waitFor:621 > » AtlasService > > NotificationHookConsumerIT.testUpdateEntityPartial:127->BaseResourceIT.waitFor:626 > » > EntityJerseyResourceIT.testPartialUpdate:881 expected:<1> but was:<3> > MetadataDiscoveryJerseyResourceIT.testSearchUsingGremlin:153 » > AtlasService Me... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-1859) Add validation checking around relationshipDefs
[ https://issues.apache.org/jira/browse/ATLAS-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian resolved ATLAS-1859. --- Resolution: Duplicate > Add validation checking around relationshipDefs > --- > > Key: ATLAS-1859 > URL: https://issues.apache.org/jira/browse/ATLAS-1859 > Project: Atlas > Issue Type: Sub-task >Reporter: David Radley >Assignee: Sarath Subramanian > > When a relationshipDef creation request is attempted, Atlas needs to check: > - does the endpoint name in the relationship already exist in another active > relationshipdef that applies to that type > - does the endpoint name in the relationship already exist in another > attributedef that applies to that type > The above needs to account for any attributeDefs and relationshipdefs that > apply due to type inheritance. > There is also the case that for supplied models like Hive, there may need to > be some mechanism to allow the old forms of composition relationships - that > Gremlin queries might relay on. The old forms of relationship instances are > implemented by 2 edges - the new form is one edge. > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-1857) Fix unit test failure in jenkins server
[ https://issues.apache.org/jira/browse/ATLAS-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian resolved ATLAS-1857. --- Resolution: Cannot Reproduce > Fix unit test failure in jenkins server > --- > > Key: ATLAS-1857 > URL: https://issues.apache.org/jira/browse/ATLAS-1857 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: trunk, 0.9-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > > Fix unit test failure for the following test: > EntityDiscoveryServiceTest.getSubTypeForTypeWithSubTypes_ReturnsOrClause in > the nightly jenkins server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ATLAS-1856) Relationship instance API Java & REST implementation
[ https://issues.apache.org/jira/browse/ATLAS-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian resolved ATLAS-1856. --- Resolution: Fixed Committed to master: https://git1-us-west.apache.org/repos/asf?p=atlas.git;a=commit;h=242b5585c97a9565ac35641d8a1ed8ee3a8fd883 > Relationship instance API Java & REST implementation > > > Key: ATLAS-1856 > URL: https://issues.apache.org/jira/browse/ATLAS-1856 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: trunk, 0.9-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > Attachments: ATLAS-1856.2.patch, curl_create_new_relationDef, > curl_create_new_relationInstance > > > Based on the relationDef implementation in ATLAS-1852. Implement instance API > and REST for entity relationships -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1979) Update storm model relationship category and fix for UT and Coverity scan issues
[ https://issues.apache.org/jira/browse/ATLAS-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137550#comment-16137550 ] Sarath Subramanian commented on ATLAS-1979: --- committed to master: https://git1-us-west.apache.org/repos/asf?p=atlas.git;a=commit;h=13ba156f1d76caaa969e2f6fd93e2387307ae7c7 > Update storm model relationship category and fix for UT and Coverity scan > issues > > > Key: ATLAS-1979 > URL: https://issues.apache.org/jira/browse/ATLAS-1979 > Project: Atlas > Issue Type: Bug >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > Attachments: ATLAS-1979.1.patch > > > * Update storm_topology_nodes relationshipCategory from ASSOCIATION to > AGGREGATION > * Fix the following UT failures: > _Failed tests: > > AtlasRelationshipStoreHardDeleteV1Test>AtlasRelationshipStoreV1Test.testDepartmentEmployeeEntitiesUsingRelationship:172 > expected: but was:<[]> > > AtlasRelationshipStoreSoftDeleteV1Test>AtlasRelationshipStoreV1Test.testDepartmentEmployeeEntitiesUsingRelationship:172 > expected: but was:<[]>_ > * Fix coverity scan issues flagged in last report related to ATLAS-1959 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1959) Enhance relationship attributes to support different cardinality mappings
[ https://issues.apache.org/jira/browse/ATLAS-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137551#comment-16137551 ] Sarath Subramanian commented on ATLAS-1959: --- Committed to master: https://git1-us-west.apache.org/repos/asf?p=atlas.git;a=commit;h=02e4e86b5adeb52044ba09a978c8ccbb2200d67d > Enhance relationship attributes to support different cardinality mappings > - > > Key: ATLAS-1959 > URL: https://issues.apache.org/jira/browse/ATLAS-1959 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: trunk, 0.9-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > Attachments: ATLAS-1959.1.patch > > > 1. Improve relationship model to support create/update operations and the > following cardinalities (previously supported using inverseReference): > * 1 to 1 > * 1 to many > * many to 1 > * many to many > 2. Change legacyLabel flag in AtlasRelationshipEndDef to boolean flag. > 3. Add unit tests for the above cases. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1943) Fix IT failure, lineage due to incorrect inverse reference check using relationship
[ https://issues.apache.org/jira/browse/ATLAS-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137545#comment-16137545 ] Sarath Subramanian commented on ATLAS-1943: --- Committed to master: https://github.com/apache/atlas/commit/c3808cf1f9010467801a0a1567d60a407fed4f79 > Fix IT failure, lineage due to incorrect inverse reference check using > relationship > --- > > Key: ATLAS-1943 > URL: https://issues.apache.org/jira/browse/ATLAS-1943 > Project: Atlas > Issue Type: Bug >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Critical > Attachments: ATLAS-1943.1.patch > > > Fix the following IT failures due to > Failed tests: > EntityJerseyResourceIT.testCompleteUpdate:952 » AtlasService Metadata > service ... > EntityJerseyResourceIT.testPartialUpdate:877 » AtlasService Metadata > service A... > After creating a relationship for inverse reference attribute, call is made > to create relationship for ownedRef attribute. But relationship for ownedRef > has already been created and we see exception in log - “relationship already > exists”. > For e.g.: after creating a relationship for hive_storagedesc.table, a new > relationship to create hive_table.sd is attempted – but fails since > relationship already exists (already created). Added a new method > getOrCreate(relationship) - If a relationship already exists between two > entities on an attribute retrieve it, if not create one. Validated the patch > by creating hive_table, views – lineage are rendered fine. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (ATLAS-2062) Add flag to disable v1 gremlin search API using atlas-application property
[ https://issues.apache.org/jira/browse/ATLAS-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136982#comment-16136982 ] Sarath Subramanian edited comment on ATLAS-2062 at 8/22/17 10:26 PM: - [~nixonrodrigues] Created JIRA (ATLAS-2079) to fix IT failures. was (Author: sarath.ku...@gmail.com): [~nixonrodrigues] yes I'm addressing this in a separate patch with other IT fixes, testing the patch. Will send out a review when ready. > Add flag to disable v1 gremlin search API using atlas-application property > -- > > Key: ATLAS-2062 > URL: https://issues.apache.org/jira/browse/ATLAS-2062 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 0.8-incubating, 0.9-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Minor > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-2062.1.patch > > > Add *atlas.search.gremlin.enable* property in atlas-application.properties to > disable gremlin search API. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Review Request 61825: [ATLAS-2079]: Fix IT failures introduced by ATLAS-2062
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61825/ --- Review request for atlas. Bugs: ATLAS-2079 https://issues.apache.org/jira/browse/ATLAS-2079 Repository: atlas Description --- Fix the following IT failures: Failed tests: NotificationHookConsumerIT.testDeleteByQualifiedName:184->BaseResourceIT.waitFor:621 » AtlasService NotificationHookConsumerIT.testUpdateEntityPartial:127->BaseResourceIT.waitFor:626 » EntityJerseyResourceIT.testPartialUpdate:881 expected:<1> but was:<3> MetadataDiscoveryJerseyResourceIT.testSearchUsingGremlin:153 » AtlasService Me... Diffs - intg/src/main/java/org/apache/atlas/model/instance/EntityMutationResponse.java 70784363 pom.xml f127774d typesystem/src/test/resources/atlas-application.properties 7967b761 webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerIT.java 9c5597ef webapp/src/test/java/org/apache/atlas/web/integration/EntityJerseyResourceIT.java 660f05e1 Diff: https://reviews.apache.org/r/61825/diff/1/ Testing --- The ITs works fine for webapp module. Thanks, Sarath Subramanian
Review Request 61824: [ATLAS-2078]: Updating types using v1 API doesn't route to createUpdateTypesDef in v2 API
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/61824/ --- Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, and Nixon Rodrigues. Bugs: ATLAS-2078 https://issues.apache.org/jira/browse/ATLAS-2078 Repository: atlas Description --- When updating types using v1 API, if type doesn't exist we create missing types. Currently this API maps to v2 API's update method and doesn't create missing types. Diffs - intg/src/main/java/org/apache/atlas/store/AtlasTypeDefStore.java e1c5a7f5 repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasTypeDefGraphStore.java 7a0bbca1 webapp/src/main/java/org/apache/atlas/web/resources/TypesResource.java f70593a3 Diff: https://reviews.apache.org/r/61824/diff/1/ Testing --- validated using POSTMAN REST client. Thanks, Sarath Subramanian
[jira] [Updated] (ATLAS-2078) Updating a type using v1 API doesn't route to createUpdateTypesDef in v2 API
[ https://issues.apache.org/jira/browse/ATLAS-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-2078: -- Attachment: ATLAS-2078.1.patch > Updating a type using v1 API doesn't route to createUpdateTypesDef in v2 API > > > Key: ATLAS-2078 > URL: https://issues.apache.org/jira/browse/ATLAS-2078 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.9-incubating, 0.8.1-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Critical > Fix For: 0.9-incubating, 0.8.1-incubating > > Attachments: ATLAS-2078.1.patch > > > When updating types using v1 API, if type doesn't exist we create missing > types. Currently this API maps to v2 API's update method and doesn't create > missing types. > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2078) Updating a type using v1 API doesn't route to createUpdateTypesDef in v2 API
Sarath Subramanian created ATLAS-2078: - Summary: Updating a type using v1 API doesn't route to createUpdateTypesDef in v2 API Key: ATLAS-2078 URL: https://issues.apache.org/jira/browse/ATLAS-2078 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 0.9-incubating, 0.8.1-incubating Reporter: Sarath Subramanian Assignee: Sarath Subramanian Priority: Critical Fix For: 0.9-incubating, 0.8.1-incubating When updating types using v1 API, if type doesn't exist we create missing types. Currently this API maps to v2 API's update method and doesn't create missing types. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1955) Validation for Attributes
[ https://issues.apache.org/jira/browse/ATLAS-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137157#comment-16137157 ] Richard Ding commented on ATLAS-1955: - [~davidrad] and [~mandy_chessell] suggested using _PrimitiveDefs_ instead of _attributeTypeDefs_. I think it is a better name for custom data types. > Validation for Attributes > - > > Key: ATLAS-1955 > URL: https://issues.apache.org/jira/browse/ATLAS-1955 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 0.9-incubating >Reporter: Israel Varea >Assignee: Richard Ding > Fix For: 0.9-incubating > > > It would be very nice that Atlas model could contain a way to represent > attribute validation. > A simple example is that we would like to model a Person, with attributes > Name, Email and Country. Now we would like to specify that Email has to > follow a specific regular expression, so it would be nice if we could set > Email -> hasValidation -> EmailRegex, with EmailRegex having: > Name: Email Regular Expresion > Expression: /[0-9a-z]+@[0-9a-z]+.[0-9a-z]+/ > For more complex types of validation, e.g. checking card number validity, it > could be added some external validator function/service. > Name: Credit Card Number Validator > Validator: org.apache.atlas.validators.creditcard or > https://host:port/creditCardValidator > For validations from a reference table, for example a country name, it could > be: > Name: Country Name Ref Validator > Reference Column: > where would be an instance of type Hive_Column or > HBase_Column. > Since this is a kind of Standarization, it could be placed in [Area > 5|https://cwiki.apache.org/confluence/display/ATLAS/Area+5+-+Standards]. > A similar approach is followed in software > [Kylo|https://github.com/Teradata/kylo/tree/master/integrations/spark/spark-validate-cleanse] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2077) UI Regression : Search using entity and tag filters : filters are not removed on pressing "clear" button
Sharmadha Sainath created ATLAS-2077:
Summary: UI Regression : Search using entity and tag filters :
filters are not removed on pressing "clear" button
Key: ATLAS-2077
URL: https://issues.apache.org/jira/browse/ATLAS-2077
Project: Atlas
Issue Type: Bug
Components: atlas-webui
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
1.Created a hive table.
2.Searched the hive_table, with type name = hive_table , filter name = table_1.
Result table showed the hive_table.
3.Clicked clear button which cleared the type name . Now made a query : query =
table_1.
4.This search failed with
{code}
{"errorCode":"ATLAS-400-00-029","errorMessage":"EntityFilters specified without
Type name"}
{code}
5.Same happens with tag filters.
On clicking clear button , only type name/classification is cleared. entity/tag
filters are still present and throws exception on next query. As a user , I had
to search for the same typename , remove the filter and then proceed further to
not encounter the exception.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (ATLAS-2062) Add flag to disable v1 gremlin search API using atlas-application property
[ https://issues.apache.org/jira/browse/ATLAS-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues reopened ATLAS-2062: > Add flag to disable v1 gremlin search API using atlas-application property > -- > > Key: ATLAS-2062 > URL: https://issues.apache.org/jira/browse/ATLAS-2062 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 0.8-incubating, 0.9-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Minor > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-2062.1.patch > > > Add *atlas.search.gremlin.enable* property in atlas-application.properties to > disable gremlin search API. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2062) Add flag to disable v1 gremlin search API using atlas-application property
[
https://issues.apache.org/jira/browse/ATLAS-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136489#comment-16136489
]
Nixon Rodrigues commented on ATLAS-2062:
https://builds.apache.org/job/Atlas-0.8-IntegrationTests/20/display/redirect?page=changes
{code}
testSearchUsingGremlin(org.apache.atlas.web.integration.MetadataDiscoveryJerseyResourceIT)
Time elapsed: 0.006 sec <<< FAILURE!
org.apache.atlas.AtlasServiceException: Metadata service API
org.apache.atlas.AtlasBaseClient$APIInfo@3a5fe7dc failed with status 400 (Bad
Request) Response Body ({"error":"Gremlin search is not enabled."})
at
org.apache.atlas.web.integration.MetadataDiscoveryJerseyResourceIT.testSearchUsingGremlin(MetadataDiscoveryJerseyResourceIT.java:153)
{code}
[~sarath.ku...@gmail.com], found test case failure to this new config
*atlas.search.gremlin.enable* , can you add this new property to
atlas-application.properties for integration test env to fix this issue
> Add flag to disable v1 gremlin search API using atlas-application property
> --
>
> Key: ATLAS-2062
> URL: https://issues.apache.org/jira/browse/ATLAS-2062
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 0.8-incubating, 0.9-incubating
>
> Attachments: ATLAS-2062.1.patch
>
>
> Add *atlas.search.gremlin.enable* property in atlas-application.properties to
> disable gremlin search API.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-1805) Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136381#comment-16136381 ] Ramesh Mani commented on ATLAS-1805: [~nixonrodrigues] Attached the rebased patch. Thanks. > Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to > Atlas > --- > > Key: ATLAS-1805 > URL: https://issues.apache.org/jira/browse/ATLAS-1805 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: Ramesh Mani >Assignee: Ramesh Mani > Attachments: > 0001-ATLAS-1805-Provide-an-Atlas-hook-to-send-Hbase-Names.patch > > > Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to > Atlas -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1805) Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated ATLAS-1805: --- Attachment: (was: 0001-ATLAS-1805-Provide-an-Atlas-hook-to-send-Hbase-Names.patch) > Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to > Atlas > --- > > Key: ATLAS-1805 > URL: https://issues.apache.org/jira/browse/ATLAS-1805 > Project: Atlas > Issue Type: Bug > Components: atlas-intg >Reporter: Ramesh Mani >Assignee: Ramesh Mani > > Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to > Atlas -- This message was sent by Atlassian JIRA (v6.4.14#64029)
