[jira] [Created] (ATLAS-3580) Search on __customAttributes doesn't return right results.
Le Ma created ATLAS-3580: Summary: Search on __customAttributes doesn't return right results. Key: ATLAS-3580 URL: https://issues.apache.org/jira/browse/ATLAS-3580 Project: Atlas Issue Type: Bug Reporter: Le Ma Assignee: Le Ma -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3542) _ALL_CLASSIFICATION_TYPES without filters should behave as _CLASSIFIED
[ https://issues.apache.org/jira/browse/ATLAS-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3542: - Description: With _ALL_CLASSIFICATION_TYPES selected in the UI and no attribute filter, currently, the search result is empty. it should be the same as _CLASSIFIED. > _ALL_CLASSIFICATION_TYPES without filters should behave as _CLASSIFIED > --- > > Key: ATLAS-3542 > URL: https://issues.apache.org/jira/browse/ATLAS-3542 > Project: Atlas > Issue Type: Improvement >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > > With _ALL_CLASSIFICATION_TYPES selected in the UI and no attribute filter, > currently, the search result is empty. > it should be the same as _CLASSIFIED. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3542) _ALL_CLASSIFICATION_TYPES without filters should behave as _CLASSIFIED
Le Ma created ATLAS-3542: Summary: _ALL_CLASSIFICATION_TYPES without filters should behave as _CLASSIFIED Key: ATLAS-3542 URL: https://issues.apache.org/jira/browse/ATLAS-3542 Project: Atlas Issue Type: Improvement Reporter: Le Ma Assignee: Le Ma -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3541) Change System Attributes Type to Enable Integration at Front-end
[ https://issues.apache.org/jira/browse/ATLAS-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma resolved ATLAS-3541. -- Resolution: Fixed > Change System Attributes Type to Enable Integration at Front-end > > > Key: ATLAS-3541 > URL: https://issues.apache.org/jira/browse/ATLAS-3541 > Project: Atlas > Issue Type: Improvement >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > > __timestamp and __modificationTimestamp are currently Long type, change it > to Date so that Front-end could integrate it with date-picker. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3533) Regression : Search with term and tag doesn't return right results
[ https://issues.apache.org/jira/browse/ATLAS-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984066#comment-16984066 ] Le Ma commented on ATLAS-3533: -- rb : [https://reviews.apache.org/r/71822/] Pc : [https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1569/] > Regression : Search with term and tag doesn't return right results > -- > > Key: ATLAS-3533 > URL: https://issues.apache.org/jira/browse/ATLAS-3533 > Project: Atlas > Issue Type: Bug >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > > 1.Create a term - term1 under glossary1 > 2.Create tags - tag1, tag2 > 3.Associate entity e1 to tag1 , term1@glossary1 > Fire Search with term = term1@glossary1 , classification = tag1 , entity e1 > is returned which is expected > Fire Search with term = term1@glossary1 , classification = tag2 , still e1 > is returned , which is not expected. > Any tag like tag1 , * , __CLASSIFIED,_ __NOT__CLASSIFIED are not considered > when term is present in search. > Other param like type is considered only classification is not considered. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3533) Regression : Search with term and tag doesn't return right results
[ https://issues.apache.org/jira/browse/ATLAS-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma resolved ATLAS-3533. -- Resolution: Fixed > Regression : Search with term and tag doesn't return right results > -- > > Key: ATLAS-3533 > URL: https://issues.apache.org/jira/browse/ATLAS-3533 > Project: Atlas > Issue Type: Bug >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > > 1.Create a term - term1 under glossary1 > 2.Create tags - tag1, tag2 > 3.Associate entity e1 to tag1 , term1@glossary1 > Fire Search with term = term1@glossary1 , classification = tag1 , entity e1 > is returned which is expected > Fire Search with term = term1@glossary1 , classification = tag2 , still e1 > is returned , which is not expected. > Any tag like tag1 , * , __CLASSIFIED,_ __NOT__CLASSIFIED are not considered > when term is present in search. > Other param like type is considered only classification is not considered. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3541) Change System Attributes Type to Enable Integration at Front-end
[ https://issues.apache.org/jira/browse/ATLAS-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984065#comment-16984065 ] Le Ma commented on ATLAS-3541: -- rb : [https://reviews.apache.org/r/71842/] > Change System Attributes Type to Enable Integration at Front-end > > > Key: ATLAS-3541 > URL: https://issues.apache.org/jira/browse/ATLAS-3541 > Project: Atlas > Issue Type: Improvement >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > > __timestamp and __modificationTimestamp are currently Long type, change it > to Date so that Front-end could integrate it with date-picker. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3541) Change System Attributes Type to Enable Integration at Front-end
Le Ma created ATLAS-3541: Summary: Change System Attributes Type to Enable Integration at Front-end Key: ATLAS-3541 URL: https://issues.apache.org/jira/browse/ATLAS-3541 Project: Atlas Issue Type: Improvement Reporter: Le Ma Assignee: Le Ma __timestamp and __modificationTimestamp are currently Long type, change it to Date so that Front-end could integrate it with date-picker. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3538) Search on system attribute IS_INCOMPLETE_PROPERTY_KEY doesn't return results
Le Ma created ATLAS-3538: Summary: Search on system attribute IS_INCOMPLETE_PROPERTY_KEY doesn't return results Key: ATLAS-3538 URL: https://issues.apache.org/jira/browse/ATLAS-3538 Project: Atlas Issue Type: Bug Reporter: Le Ma Assignee: Le Ma -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3533) Regression : Search with term and tag doesn't return right results
Le Ma created ATLAS-3533: Summary: Regression : Search with term and tag doesn't return right results Key: ATLAS-3533 URL: https://issues.apache.org/jira/browse/ATLAS-3533 Project: Atlas Issue Type: Bug Reporter: Le Ma Assignee: Le Ma 1.Create a term - term1 under glossary1 2.Create tags - tag1, tag2 3.Associate entity e1 to tag1 , term1@glossary1 Fire Search with term = term1@glossary1 , classification = tag1 , entity e1 is returned which is expected Fire Search with term = term1@glossary1 , classification = tag2 , still e1 is returned , which is not expected. Any tag like tag1 , * , __CLASSIFIED,_ __NOT__CLASSIFIED are not considered when term is present in search. Other param like type is considered only classification is not considered. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3482) Enhance basic search to enable search on entity system attributes
[
https://issues.apache.org/jira/browse/ATLAS-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Le Ma updated ATLAS-3482:
-
Description:
System attributes are enabled for entity search via basic search.
System attributes for both entity and classification:
__typeName, __state, __createdBy, __modifiedBy, __timestamp,
__modificationTimestamp
System attributes only for entity:
__guid, __historicalGuids, __labels, __customAttributes, __classificationsText,
__classificationNames, __propagatedClassificationNames, __isIncomplete
Specific entity type (typeName) can either be present or not. These system
attributes will work just like normal entity attributes, present in the
entityFilters. System attributes can be used to search across entity
types("__ALL_ENTITY_TYPES" should be the value of typeName), note, entity
attributes should not be included in this case, otherwise, an exception will be
thrown.
> Enhance basic search to enable search on entity system attributes
> -
>
> Key: ATLAS-3482
> URL: https://issues.apache.org/jira/browse/ATLAS-3482
> Project: Atlas
> Issue Type: New Feature
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Le Ma
>Assignee: Le Ma
>Priority: Major
> Fix For: 2.1.0
>
>
> System attributes are enabled for entity search via basic search.
> System attributes for both entity and classification:
> __typeName, __state, __createdBy, __modifiedBy, __timestamp,
> __modificationTimestamp
>
> System attributes only for entity:
> __guid, __historicalGuids, __labels, __customAttributes,
> __classificationsText,
> __classificationNames, __propagatedClassificationNames, __isIncomplete
>
> Specific entity type (typeName) can either be present or not. These system
> attributes will work just like normal entity attributes, present in the
> entityFilters. System attributes can be used to search across entity
> types("__ALL_ENTITY_TYPES" should be the value of typeName), note, entity
> attributes should not be included in this case, otherwise, an exception will
> be thrown.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-3482) Enhance basic search to enable search on entity system attributes
[ https://issues.apache.org/jira/browse/ATLAS-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976945#comment-16976945 ] Le Ma commented on ATLAS-3482: -- Pre-commit job succeeds. https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1540/ > Enhance basic search to enable search on entity system attributes > - > > Key: ATLAS-3482 > URL: https://issues.apache.org/jira/browse/ATLAS-3482 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3497) Add audit entry for adding/setting/removing labels
[ https://issues.apache.org/jira/browse/ATLAS-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16967891#comment-16967891 ] Le Ma commented on ATLAS-3497: -- Pre-commit job succeeded : [https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1527/] > Add audit entry for adding/setting/removing labels > -- > > Key: ATLAS-3497 > URL: https://issues.apache.org/jira/browse/ATLAS-3497 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > > TLAS-3483 https://issues.apache.org/jira/browse/ATLAS-3483 added > adding/removing labels, it would be good to add audit entry for these > operations: classification added / classification deleted. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-3497) Add audit entry for adding/setting/removing labels
[ https://issues.apache.org/jira/browse/ATLAS-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16967891#comment-16967891 ] Le Ma edited comment on ATLAS-3497 at 11/5/19 9:41 PM: --- Pre-commit job succeeded: [https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1527/] was (Author: lma): Pre-commit job succeeded : [https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1527/] > Add audit entry for adding/setting/removing labels > -- > > Key: ATLAS-3497 > URL: https://issues.apache.org/jira/browse/ATLAS-3497 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > > TLAS-3483 https://issues.apache.org/jira/browse/ATLAS-3483 added > adding/removing labels, it would be good to add audit entry for these > operations: classification added / classification deleted. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3497) Add audit entry for adding/setting/removing labels
[ https://issues.apache.org/jira/browse/ATLAS-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3497: - CR : [https://reviews.apache.org/r/71710/] > Add audit entry for adding/setting/removing labels > -- > > Key: ATLAS-3497 > URL: https://issues.apache.org/jira/browse/ATLAS-3497 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > > TLAS-3483 https://issues.apache.org/jira/browse/ATLAS-3483 added > adding/removing labels, it would be good to add audit entry for these > operations: classification added / classification deleted. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3497) Add audit entry for adding/setting/removing labels
[ https://issues.apache.org/jira/browse/ATLAS-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3497: - Description: TLAS-3483 https://issues.apache.org/jira/browse/ATLAS-3483 added adding/removing labels, it would be good to add audit entry for these operations: classification added / classification deleted. (was: TLAS-3483 added adding/removing labels, it would be good to add audit entry for these operations: classification added / classification deleted) > Add audit entry for adding/setting/removing labels > -- > > Key: ATLAS-3497 > URL: https://issues.apache.org/jira/browse/ATLAS-3497 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > > TLAS-3483 https://issues.apache.org/jira/browse/ATLAS-3483 added > adding/removing labels, it would be good to add audit entry for these > operations: classification added / classification deleted. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3497) Add audit entry for adding/setting/removing labels
[ https://issues.apache.org/jira/browse/ATLAS-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3497: - Description: TLAS-3483 added adding/removing labels, it would be good to add audit entry for these operations: classification added / classification deleted > Add audit entry for adding/setting/removing labels > -- > > Key: ATLAS-3497 > URL: https://issues.apache.org/jira/browse/ATLAS-3497 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > > TLAS-3483 added adding/removing labels, it would be good to add audit entry > for these operations: classification added / classification deleted -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3497) Add audit entry for adding/setting/removing labels
Le Ma created ATLAS-3497: Summary: Add audit entry for adding/setting/removing labels Key: ATLAS-3497 URL: https://issues.apache.org/jira/browse/ATLAS-3497 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Le Ma Assignee: Le Ma -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3496) UI : Support multi-classification search without attributes
Le Ma created ATLAS-3496: Summary: UI : Support multi-classification search without attributes Key: ATLAS-3496 URL: https://issues.apache.org/jira/browse/ATLAS-3496 Project: Atlas Issue Type: Improvement Components: atlas-webui Reporter: Le Ma ATLAS-3457 https://issues.apache.org/jira/browse/ATLAS-3457 will enable multi-classification search without attributes. It will reuse tagFilters to pass in multi-classifications. attributeName has to be "__typeName" attributeVal will be classification name. validation is inside the ATLAS-3457 PATCH. if classification under searchParamter is present, any values in tagFilters will be treated as attributes of given classification. When classification under searchParamter is not present, any values in tagFilters will be treated as multi-classification names. Any further questions, please comment on this Jira. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3495) UI : support entity search on system attributes
Le Ma created ATLAS-3495: Summary: UI : support entity search on system attributes Key: ATLAS-3495 URL: https://issues.apache.org/jira/browse/ATLAS-3495 Project: Atlas Issue Type: Improvement Components: atlas-webui Reporter: Le Ma ATLAS-3482 https://issues.apache.org/jira/browse/ATLAS-3482 will allow entity search on system attributes when entity type is not present. And only system attributes search is allowed when entity type is missing, search on any other entity attributes will cause errors. System atrributes are sent using EntityFilters(filterCriterion). AttributeName inside filterCriterion has to be one of the system attributes. Front-end need the corresponding change. Any details/questions, please comment on this Jira. Thanks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3482) Enhance basic search to enable search on entity system attributes
[ https://issues.apache.org/jira/browse/ATLAS-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3482: - Component/s: atlas-core Issue Type: New Feature (was: Bug) > Enhance basic search to enable search on entity system attributes > - > > Key: ATLAS-3482 > URL: https://issues.apache.org/jira/browse/ATLAS-3482 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3480) atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 / Authentication failed when Atlas 2.0 uses kerberos-enabled solr as index backend
[ https://issues.apache.org/jira/browse/ATLAS-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3480: - Description: 当我使用 atlas2.0 版本 ，底层使用开启kerberos认证的solr 作为atlas的搜索引擎时，atlas无法通过solr的kerberos的认证。solr 用的是cdh的7.4版本。 已经测试过账号没有问题。 后台solr http 响应的是401. 是否可以提供一份正确的atlas-application.properties 配置文件 When Atlas 2.0 uses Kerberos-enabled solr as index engine, atlas fails the Kerberos authentication. cdh 7.4 is used for solr. Account/credentials is working. 401 error is returned from the backend. If it is possible for the community to provide a correct atlas-application.properties config. Thanks. was: 当我使用 atlas2.0 版本 ，底层使用开启kerberos认证的solr 作为atlas的搜索引擎时，atlas无法通过solr的kerberos的认证。solr 用的是cdh的7.4版本。 已经测试过账号没有问题。 后台solr http 响应的是401. 是否可以提供一份正确的atlas-application.properties 配置文件 > atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 / Authentication failed when Atlas 2.0 > uses kerberos-enabled solr as index backend > - > > Key: ATLAS-3480 > URL: https://issues.apache.org/jira/browse/ATLAS-3480 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: youtakeoff >Priority: Major > > 当我使用 atlas2.0 版本 ，底层使用开启kerberos认证的solr > 作为atlas的搜索引擎时，atlas无法通过solr的kerberos的认证。solr 用的是cdh的7.4版本。 > 已经测试过账号没有问题。 > 后台solr http 响应的是401. > 是否可以提供一份正确的atlas-application.properties 配置文件 > > When Atlas 2.0 uses Kerberos-enabled solr as index engine, atlas fails the > Kerberos authentication. cdh 7.4 is used for solr. > Account/credentials is working. > 401 error is returned from the backend. > If it is possible for the community to provide a correct > atlas-application.properties config. > Thanks. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3480) atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 Authentication failed when Atlas uses kerberos-enabled solr as index backend
[ https://issues.apache.org/jira/browse/ATLAS-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3480: - Summary: atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 Authentication failed when Atlas uses kerberos-enabled solr as index backend (was: atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 Authentication failed when Atlas uses kerberos-enabled solr as index backend ) > atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 >Authentication failed when Atlas uses kerberos-enabled solr as > index backend > -- > > Key: ATLAS-3480 > URL: https://issues.apache.org/jira/browse/ATLAS-3480 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: youtakeoff >Priority: Major > > 当我使用 atlas2.0 版本 ，底层使用开启kerberos认证的solr > 作为atlas的搜索引擎时，atlas无法通过solr的kerberos的认证。solr 用的是cdh的7.4版本。 > 已经测试过账号没有问题。 > 后台solr http 响应的是401. > 是否可以提供一份正确的atlas-application.properties 配置文件 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3480) atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 Authentication failed when Atlas uses kerberos-enabled solr as index backend
[ https://issues.apache.org/jira/browse/ATLAS-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3480: - Summary: atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 Authentication failed when Atlas uses kerberos-enabled solr as index backend (was: atlas2.0 版本集成开启kerberos认证的solr ，认证不通过) > atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 Authentication failed when Atlas uses > kerberos-enabled solr as index backend > --- > > Key: ATLAS-3480 > URL: https://issues.apache.org/jira/browse/ATLAS-3480 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: youtakeoff >Priority: Major > > 当我使用 atlas2.0 版本 ，底层使用开启kerberos认证的solr > 作为atlas的搜索引擎时，atlas无法通过solr的kerberos的认证。solr 用的是cdh的7.4版本。 > 已经测试过账号没有问题。 > 后台solr http 响应的是401. > 是否可以提供一份正确的atlas-application.properties 配置文件 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3480) atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 / Authentication failed when Atlas 2.0 uses kerberos-enabled solr as index backend
[ https://issues.apache.org/jira/browse/ATLAS-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3480: - Summary: atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 / Authentication failed when Atlas 2.0 uses kerberos-enabled solr as index backend (was: atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 / Authentication failed when Atlas uses kerberos-enabled solr as index backend ) > atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 / Authentication failed when Atlas 2.0 > uses kerberos-enabled solr as index backend > - > > Key: ATLAS-3480 > URL: https://issues.apache.org/jira/browse/ATLAS-3480 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: youtakeoff >Priority: Major > > 当我使用 atlas2.0 版本 ，底层使用开启kerberos认证的solr > 作为atlas的搜索引擎时，atlas无法通过solr的kerberos的认证。solr 用的是cdh的7.4版本。 > 已经测试过账号没有问题。 > 后台solr http 响应的是401. > 是否可以提供一份正确的atlas-application.properties 配置文件 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3480) atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 / Authentication failed when Atlas uses kerberos-enabled solr as index backend
[ https://issues.apache.org/jira/browse/ATLAS-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3480: - Summary: atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 / Authentication failed when Atlas uses kerberos-enabled solr as index backend (was: atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 Authentication failed when Atlas uses kerberos-enabled solr as index backend ) > atlas2.0 版本集成开启kerberos认证的solr ，认证不通过 / Authentication failed when Atlas uses > kerberos-enabled solr as index backend > - > > Key: ATLAS-3480 > URL: https://issues.apache.org/jira/browse/ATLAS-3480 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: youtakeoff >Priority: Major > > 当我使用 atlas2.0 版本 ，底层使用开启kerberos认证的solr > 作为atlas的搜索引擎时，atlas无法通过solr的kerberos的认证。solr 用的是cdh的7.4版本。 > 已经测试过账号没有问题。 > 后台solr http 响应的是401. > 是否可以提供一份正确的atlas-application.properties 配置文件 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3491) Regression : Search on parent tag with includeSubclassifications:True doesn't return entities associated to its child tag
Le Ma created ATLAS-3491: Summary: Regression : Search on parent tag with includeSubclassifications:True doesn't return entities associated to its child tag Key: ATLAS-3491 URL: https://issues.apache.org/jira/browse/ATLAS-3491 Project: Atlas Issue Type: Bug Reporter: Le Ma Assignee: Le Ma -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3491) Regression : Search on parent tag with includeSubclassifications:True doesn't return entities associated to its child tag
[ https://issues.apache.org/jira/browse/ATLAS-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3491: - Description: # Create tag parent_tag # Create child_tag with parent tag as parent_tag # Associate child_tag to entity e1. # Perform search with parent_tag with includeSubclassifications set to True. Expected result is e1 but no entities are returned. No exceptions seen in application logs If an entity is directly associated to parent_tag , then search on parent_tag results in that entity > Regression : Search on parent tag with includeSubclassifications:True doesn't > return entities associated to its child tag > - > > Key: ATLAS-3491 > URL: https://issues.apache.org/jira/browse/ATLAS-3491 > Project: Atlas > Issue Type: Bug >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > > # Create tag parent_tag > # Create child_tag with parent tag as parent_tag > # Associate child_tag to entity e1. > # Perform search with parent_tag with includeSubclassifications set to True. > Expected result is e1 but no entities are returned. No exceptions seen in > application logs > If an entity is directly associated to parent_tag , then search on parent_tag > results in that entity -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3482) Enhance basic search to enable search on entity system attributes
[ https://issues.apache.org/jira/browse/ATLAS-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3482: - Summary: Enhance basic search to enable search on entity system attributes (was: Support search by system attributes for entity ) > Enhance basic search to enable search on entity system attributes > - > > Key: ATLAS-3482 > URL: https://issues.apache.org/jira/browse/ATLAS-3482 > Project: Atlas > Issue Type: Bug >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3483) Support adding/deleting labels
Le Ma created ATLAS-3483: Summary: Support adding/deleting labels Key: ATLAS-3483 URL: https://issues.apache.org/jira/browse/ATLAS-3483 Project: Atlas Issue Type: Improvement Reporter: Le Ma Assignee: Le Ma The current implementation of label only exposes setLabel endpoint to users. setLabel will replace the existing labels with labels passed in with function. It would be nice to have the enhancement to support add labels to existing label and, delete label. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3482) Support search by system attributes for entity
Le Ma created ATLAS-3482: Summary: Support search by system attributes for entity Key: ATLAS-3482 URL: https://issues.apache.org/jira/browse/ATLAS-3482 Project: Atlas Issue Type: Bug Reporter: Le Ma Assignee: Le Ma -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3447) Basic Search API does not return child classifications
[ https://issues.apache.org/jira/browse/ATLAS-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3447: - Attachment: before deletion - parent.png before deletion - child.png after deletion - parent.png > Basic Search API does not return child classifications > -- > > Key: ATLAS-3447 > URL: https://issues.apache.org/jira/browse/ATLAS-3447 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Le Ma >Priority: Major > Attachments: after deletion - parent.png, before deletion - > child.png, before deletion - parent.png, > child_classification_does_not_appear_after_parent_classification_is_reapplied.webm, > > childclassification_vanishes_after_parent_classification_association_is_empty.webm > > > Detailed explanation of the issue along with an additional related issue(with > videos attached). > Scenario I: > [^childclassification_vanishes_after_parent_classification_association_is_empty.webm] > Entity E1 is associated with classification 'Parent' and entity E2 is > associated with classification 'Child' where 'Child' is subclassification of > 'Parent'. > * In the 'Parent' classification details page, E1 and E2 are visible. > * 'Parent' classification is removed from E1. > * When we view Parent classification details, E1 no longer appears, but even > E2 is removed, which is incorrect as the 'Child' is a subclassification of > 'Parent' and should be visible on the page as the option "Exclude > subclassifications" is not selected. > > Scenario II: > [^child_classification_does_not_appear_after_parent_classification_is_reapplied.webm] > After performing steps from scenario I, > * Reassign 'Parent' classification to E1 > * Navigate to 'Parent' classification details page. > * E1 is still the only entity visible, even E2 should also be visible as per > step 1 in Scenario I. > * Now, remove 'Child' classification from E2 and then reapply 'Child' to E2. > * Navigate again to 'Parent' classification details page. > * You will see that now E1 and E2 appear as expected. This seems to be a > result of a stale connection. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3447) Basic Search API does not return child classifications
[ https://issues.apache.org/jira/browse/ATLAS-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3447: - Attachment: (was: Screen Shot 2019-10-18 at 3.31.55 PM.png) > Basic Search API does not return child classifications > -- > > Key: ATLAS-3447 > URL: https://issues.apache.org/jira/browse/ATLAS-3447 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Le Ma >Priority: Major > Attachments: > child_classification_does_not_appear_after_parent_classification_is_reapplied.webm, > > childclassification_vanishes_after_parent_classification_association_is_empty.webm > > > Detailed explanation of the issue along with an additional related issue(with > videos attached). > Scenario I: > [^childclassification_vanishes_after_parent_classification_association_is_empty.webm] > Entity E1 is associated with classification 'Parent' and entity E2 is > associated with classification 'Child' where 'Child' is subclassification of > 'Parent'. > * In the 'Parent' classification details page, E1 and E2 are visible. > * 'Parent' classification is removed from E1. > * When we view Parent classification details, E1 no longer appears, but even > E2 is removed, which is incorrect as the 'Child' is a subclassification of > 'Parent' and should be visible on the page as the option "Exclude > subclassifications" is not selected. > > Scenario II: > [^child_classification_does_not_appear_after_parent_classification_is_reapplied.webm] > After performing steps from scenario I, > * Reassign 'Parent' classification to E1 > * Navigate to 'Parent' classification details page. > * E1 is still the only entity visible, even E2 should also be visible as per > step 1 in Scenario I. > * Now, remove 'Child' classification from E2 and then reapply 'Child' to E2. > * Navigate again to 'Parent' classification details page. > * You will see that now E1 and E2 appear as expected. This seems to be a > result of a stale connection. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3447) Basic Search API does not return child classifications
[ https://issues.apache.org/jira/browse/ATLAS-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3447: - Attachment: (was: Screen Shot 2019-10-18 at 3.31.42 PM.png) > Basic Search API does not return child classifications > -- > > Key: ATLAS-3447 > URL: https://issues.apache.org/jira/browse/ATLAS-3447 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Le Ma >Priority: Major > Attachments: > child_classification_does_not_appear_after_parent_classification_is_reapplied.webm, > > childclassification_vanishes_after_parent_classification_association_is_empty.webm > > > Detailed explanation of the issue along with an additional related issue(with > videos attached). > Scenario I: > [^childclassification_vanishes_after_parent_classification_association_is_empty.webm] > Entity E1 is associated with classification 'Parent' and entity E2 is > associated with classification 'Child' where 'Child' is subclassification of > 'Parent'. > * In the 'Parent' classification details page, E1 and E2 are visible. > * 'Parent' classification is removed from E1. > * When we view Parent classification details, E1 no longer appears, but even > E2 is removed, which is incorrect as the 'Child' is a subclassification of > 'Parent' and should be visible on the page as the option "Exclude > subclassifications" is not selected. > > Scenario II: > [^child_classification_does_not_appear_after_parent_classification_is_reapplied.webm] > After performing steps from scenario I, > * Reassign 'Parent' classification to E1 > * Navigate to 'Parent' classification details page. > * E1 is still the only entity visible, even E2 should also be visible as per > step 1 in Scenario I. > * Now, remove 'Child' classification from E2 and then reapply 'Child' to E2. > * Navigate again to 'Parent' classification details page. > * You will see that now E1 and E2 appear as expected. This seems to be a > result of a stale connection. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3447) Basic Search API does not return child classifications
[ https://issues.apache.org/jira/browse/ATLAS-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3447: - Attachment: (was: Screen Shot 2019-10-18 at 3.31.34 PM.png) > Basic Search API does not return child classifications > -- > > Key: ATLAS-3447 > URL: https://issues.apache.org/jira/browse/ATLAS-3447 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Le Ma >Priority: Major > Attachments: > child_classification_does_not_appear_after_parent_classification_is_reapplied.webm, > > childclassification_vanishes_after_parent_classification_association_is_empty.webm > > > Detailed explanation of the issue along with an additional related issue(with > videos attached). > Scenario I: > [^childclassification_vanishes_after_parent_classification_association_is_empty.webm] > Entity E1 is associated with classification 'Parent' and entity E2 is > associated with classification 'Child' where 'Child' is subclassification of > 'Parent'. > * In the 'Parent' classification details page, E1 and E2 are visible. > * 'Parent' classification is removed from E1. > * When we view Parent classification details, E1 no longer appears, but even > E2 is removed, which is incorrect as the 'Child' is a subclassification of > 'Parent' and should be visible on the page as the option "Exclude > subclassifications" is not selected. > > Scenario II: > [^child_classification_does_not_appear_after_parent_classification_is_reapplied.webm] > After performing steps from scenario I, > * Reassign 'Parent' classification to E1 > * Navigate to 'Parent' classification details page. > * E1 is still the only entity visible, even E2 should also be visible as per > step 1 in Scenario I. > * Now, remove 'Child' classification from E2 and then reapply 'Child' to E2. > * Navigate again to 'Parent' classification details page. > * You will see that now E1 and E2 appear as expected. This seems to be a > result of a stale connection. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3447) Basic Search API does not return child classifications
[ https://issues.apache.org/jira/browse/ATLAS-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3447: - Attachment: Screen Shot 2019-10-18 at 3.31.55 PM.png Screen Shot 2019-10-18 at 3.31.42 PM.png Screen Shot 2019-10-18 at 3.31.34 PM.png > Basic Search API does not return child classifications > -- > > Key: ATLAS-3447 > URL: https://issues.apache.org/jira/browse/ATLAS-3447 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Le Ma >Priority: Major > Attachments: Screen Shot 2019-10-18 at 3.31.34 PM.png, Screen Shot > 2019-10-18 at 3.31.42 PM.png, Screen Shot 2019-10-18 at 3.31.55 PM.png, > child_classification_does_not_appear_after_parent_classification_is_reapplied.webm, > > childclassification_vanishes_after_parent_classification_association_is_empty.webm > > > Detailed explanation of the issue along with an additional related issue(with > videos attached). > Scenario I: > [^childclassification_vanishes_after_parent_classification_association_is_empty.webm] > Entity E1 is associated with classification 'Parent' and entity E2 is > associated with classification 'Child' where 'Child' is subclassification of > 'Parent'. > * In the 'Parent' classification details page, E1 and E2 are visible. > * 'Parent' classification is removed from E1. > * When we view Parent classification details, E1 no longer appears, but even > E2 is removed, which is incorrect as the 'Child' is a subclassification of > 'Parent' and should be visible on the page as the option "Exclude > subclassifications" is not selected. > > Scenario II: > [^child_classification_does_not_appear_after_parent_classification_is_reapplied.webm] > After performing steps from scenario I, > * Reassign 'Parent' classification to E1 > * Navigate to 'Parent' classification details page. > * E1 is still the only entity visible, even E2 should also be visible as per > step 1 in Scenario I. > * Now, remove 'Child' classification from E2 and then reapply 'Child' to E2. > * Navigate again to 'Parent' classification details page. > * You will see that now E1 and E2 appear as expected. This seems to be a > result of a stale connection. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3447) Basic Search API does not return child classifications
[ https://issues.apache.org/jira/browse/ATLAS-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954996#comment-16954996 ] Le Ma commented on ATLAS-3447: -- Hello [~kevalbhatt], thanks for this detailed description. I did the test on the master branch, however, I could not reproduce the issue. Do you mind share your version number? Attached is the test that I did. Thanks. > Basic Search API does not return child classifications > -- > > Key: ATLAS-3447 > URL: https://issues.apache.org/jira/browse/ATLAS-3447 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Le Ma >Priority: Major > Attachments: > child_classification_does_not_appear_after_parent_classification_is_reapplied.webm, > > childclassification_vanishes_after_parent_classification_association_is_empty.webm > > > Detailed explanation of the issue along with an additional related issue(with > videos attached). > Scenario I: > [^childclassification_vanishes_after_parent_classification_association_is_empty.webm] > Entity E1 is associated with classification 'Parent' and entity E2 is > associated with classification 'Child' where 'Child' is subclassification of > 'Parent'. > * In the 'Parent' classification details page, E1 and E2 are visible. > * 'Parent' classification is removed from E1. > * When we view Parent classification details, E1 no longer appears, but even > E2 is removed, which is incorrect as the 'Child' is a subclassification of > 'Parent' and should be visible on the page as the option "Exclude > subclassifications" is not selected. > > Scenario II: > [^child_classification_does_not_appear_after_parent_classification_is_reapplied.webm] > After performing steps from scenario I, > * Reassign 'Parent' classification to E1 > * Navigate to 'Parent' classification details page. > * E1 is still the only entity visible, even E2 should also be visible as per > step 1 in Scenario I. > * Now, remove 'Child' classification from E2 and then reapply 'Child' to E2. > * Navigate again to 'Parent' classification details page. > * You will see that now E1 and E2 appear as expected. This seems to be a > result of a stale connection. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3447) Basic Search API does not return child classifications
[ https://issues.apache.org/jira/browse/ATLAS-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma reassigned ATLAS-3447: Assignee: Le Ma > Basic Search API does not return child classifications > -- > > Key: ATLAS-3447 > URL: https://issues.apache.org/jira/browse/ATLAS-3447 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Le Ma >Priority: Major > Attachments: > child_classification_does_not_appear_after_parent_classification_is_reapplied.webm, > > childclassification_vanishes_after_parent_classification_association_is_empty.webm > > > Detailed explanation of the issue along with an additional related issue(with > videos attached). > Scenario I: > [^childclassification_vanishes_after_parent_classification_association_is_empty.webm] > Entity E1 is associated with classification 'Parent' and entity E2 is > associated with classification 'Child' where 'Child' is subclassification of > 'Parent'. > * In the 'Parent' classification details page, E1 and E2 are visible. > * 'Parent' classification is removed from E1. > * When we view Parent classification details, E1 no longer appears, but even > E2 is removed, which is incorrect as the 'Child' is a subclassification of > 'Parent' and should be visible on the page as the option "Exclude > subclassifications" is not selected. > > Scenario II: > [^child_classification_does_not_appear_after_parent_classification_is_reapplied.webm] > After performing steps from scenario I, > * Reassign 'Parent' classification to E1 > * Navigate to 'Parent' classification details page. > * E1 is still the only entity visible, even E2 should also be visible as per > step 1 in Scenario I. > * Now, remove 'Child' classification from E2 and then reapply 'Child' to E2. > * Navigate again to 'Parent' classification details page. > * You will see that now E1 and E2 appear as expected. This seems to be a > result of a stale connection. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3467) Regression : Tag filters (begins_with , ends_with , contains) and space fetches incorrect results
[ https://issues.apache.org/jira/browse/ATLAS-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954001#comment-16954001 ] Le Ma commented on ATLAS-3467: -- RC : [https://reviews.apache.org/r/71625/] > Regression : Tag filters (begins_with , ends_with , contains) and space > fetches incorrect results > - > > Key: ATLAS-3467 > URL: https://issues.apache.org/jira/browse/ATLAS-3467 > Project: Atlas > Issue Type: Bug >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > > 1. Create a tag `tag1` with attribute `attr1`. > 2. Associate `tag1` to an entity with value `value1` for `attr1` > 3. Fire basic search for tag1 with filters: > "attr1" contains "new comment" > > Entity is returned , though "value1" is not related to "new comment" at all. > > Happens with contains/begins_with/ends_with filters and not with =/!= > Happens with filters with space (ex : new comment and not with newcomment or > new_comment) > Happens only with tag filters and not with entity filters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3425) gremlin Script Execution Failed
[ https://issues.apache.org/jira/browse/ATLAS-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953998#comment-16953998 ] Le Ma commented on ATLAS-3425: -- RC : [https://reviews.apache.org/r/71624/] > gremlin Script Execution Failed > --- > > Key: ATLAS-3425 > URL: https://issues.apache.org/jira/browse/ATLAS-3425 > Project: Atlas > Issue Type: Bug >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Attachments: error log, image.png > > > In basic search, query parameters are: > * typeName: > * classificationName > * tag attribute is boolean. > * fulltext query is tag attribute name > No results is found. below error message is found in the backend log > Please check the attached image for basic seach parameters. > javax.script.ScriptException: javax.script.ScriptException: > groovy.lang.MissingPropertyException: No such property: in for class: > org.apache.tinkerpop.gremlin.structure.T at > org.apache.tinkerpop.gremlin.groovy.jsr223.GremlinGroovyScriptEngine.eval(GremlinGroovyScriptEngine.java:378) > at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:233) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.executeGremlinScript(AtlasJanusGraph.java:368) > at > org.apache.atlas.discovery.ClassificationSearchProcessor.filter(ClassificationSearchProcessor.java:339) > at > org.apache.atlas.discovery.SearchProcessor.filter(SearchProcessor.java:156) > at > org.apache.atlas.discovery.FreeTextSearchProcessor.execute(FreeTextSearchProcessor.java:156) > at > org.apache.atlas.discovery.EntityDiscoveryService.searchWithSearchContext(EntityDiscoveryService.java:471) > at > org.apache.atlas.discovery.EntityDiscoveryService.searchWithParameters(EntityDiscoveryService.java:458) > 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$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) > at > org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:82) > 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.discovery.EntityDiscoveryService$$EnhancerBySpringCGLIB$$95d844c8.searchWithParameters() > at > org.apache.atlas.web.rest.DiscoveryREST.searchWithParameters(DiscoveryREST.java:342) > at sun.reflect.GeneratedMethodAccessor181.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1712) > at
[jira] [Commented] (ATLAS-3457) Support Multi-Classification search without attributes
[ https://issues.apache.org/jira/browse/ATLAS-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953999#comment-16953999 ] Le Ma commented on ATLAS-3457: -- RC : [https://reviews.apache.org/r/71612/] > Support Multi-Classification search without attributes > -- > > Key: ATLAS-3457 > URL: https://issues.apache.org/jira/browse/ATLAS-3457 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3476) Regression : Case insensitivity in tag filters in search
Le Ma created ATLAS-3476: Summary: Regression : Case insensitivity in tag filters in search Key: ATLAS-3476 URL: https://issues.apache.org/jira/browse/ATLAS-3476 Project: Atlas Issue Type: Bug Reporter: Le Ma Assignee: Le Ma 1. Create a tag `tag1` with attribute `attr1`. 2. Associate `tag1` to an entity with value `value1` fo `attr1` 3. Fire basic search for tag1 with filters attr1 = VALUE1 Entity is returned though there is case mismatch. This doesn't happen with entity filters. for example , for hive_table sample_08 , basic search : type = hive_table, filters , name = SAMPLE_08 doesn't fetch the entity. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3467) Regression : Tag filters (begins_with , ends_with , contains) and space fetches incorrect results
Le Ma created ATLAS-3467: Summary: Regression : Tag filters (begins_with , ends_with , contains) and space fetches incorrect results Key: ATLAS-3467 URL: https://issues.apache.org/jira/browse/ATLAS-3467 Project: Atlas Issue Type: Bug Reporter: Le Ma Assignee: Le Ma 1. Create a tag `tag1` with attribute `attr1`. 2. Associate `tag1` to an entity with value `value1` for `attr1` 3. Fire basic search for tag1 with filters: "attr1" contains "new comment" Entity is returned , though "value1" is not related to "new comment" at all. Happens with contains/begins_with/ends_with filters and not with =/!= Happens with filters with space (ex : new comment and not with newcomment or new_comment) Happens only with tag filters and not with entity filters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3462) Redundant patch file in github repo
[ https://issues.apache.org/jira/browse/ATLAS-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3462: - Description: [ATLAS-3439-1.patch|https://github.com/apache/atlas/blob/master/ATLAS-3439-1.patch] is inside atlas github repo. We should remove it. > Redundant patch file in github repo > --- > > Key: ATLAS-3462 > URL: https://issues.apache.org/jira/browse/ATLAS-3462 > Project: Atlas > Issue Type: Bug >Reporter: Le Ma >Priority: Major > Attachments: Screen Shot 2019-10-14 at 4.06.04 PM.png > > > [ATLAS-3439-1.patch|https://github.com/apache/atlas/blob/master/ATLAS-3439-1.patch] > is inside atlas github repo. We should remove it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3462) Redundant patch file in github repo
[ https://issues.apache.org/jira/browse/ATLAS-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3462: - Attachment: Screen Shot 2019-10-14 at 4.06.04 PM.png > Redundant patch file in github repo > --- > > Key: ATLAS-3462 > URL: https://issues.apache.org/jira/browse/ATLAS-3462 > Project: Atlas > Issue Type: Bug >Reporter: Le Ma >Priority: Major > Attachments: Screen Shot 2019-10-14 at 4.06.04 PM.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3462) Redundant patch file in github repo
Le Ma created ATLAS-3462: Summary: Redundant patch file in github repo Key: ATLAS-3462 URL: https://issues.apache.org/jira/browse/ATLAS-3462 Project: Atlas Issue Type: Bug Reporter: Le Ma -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3457) Support Multiple Classification search without attributes
Le Ma created ATLAS-3457: Summary: Support Multiple Classification search without attributes Key: ATLAS-3457 URL: https://issues.apache.org/jira/browse/ATLAS-3457 Project: Atlas Issue Type: New Feature Reporter: Le Ma Assignee: Le Ma -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3457) Support Multi-Classification search without attributes
[ https://issues.apache.org/jira/browse/ATLAS-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3457: - Summary: Support Multi-Classification search without attributes (was: Support Multiple Classification search without attributes) > Support Multi-Classification search without attributes > -- > > Key: ATLAS-3457 > URL: https://issues.apache.org/jira/browse/ATLAS-3457 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3425) gremlin Script Execution Failed
[ https://issues.apache.org/jira/browse/ATLAS-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma reassigned ATLAS-3425: Assignee: Le Ma > gremlin Script Execution Failed > --- > > Key: ATLAS-3425 > URL: https://issues.apache.org/jira/browse/ATLAS-3425 > Project: Atlas > Issue Type: Bug >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Attachments: error log, image.png > > > In basic search, query parameters are: > * typeName: > * classificationName > * tag attribute is boolean. > * fulltext query is tag attribute name > No results is found. below error message is found in the backend log > Please check the attached image for basic seach parameters. > javax.script.ScriptException: javax.script.ScriptException: > groovy.lang.MissingPropertyException: No such property: in for class: > org.apache.tinkerpop.gremlin.structure.T at > org.apache.tinkerpop.gremlin.groovy.jsr223.GremlinGroovyScriptEngine.eval(GremlinGroovyScriptEngine.java:378) > at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:233) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.executeGremlinScript(AtlasJanusGraph.java:368) > at > org.apache.atlas.discovery.ClassificationSearchProcessor.filter(ClassificationSearchProcessor.java:339) > at > org.apache.atlas.discovery.SearchProcessor.filter(SearchProcessor.java:156) > at > org.apache.atlas.discovery.FreeTextSearchProcessor.execute(FreeTextSearchProcessor.java:156) > at > org.apache.atlas.discovery.EntityDiscoveryService.searchWithSearchContext(EntityDiscoveryService.java:471) > at > org.apache.atlas.discovery.EntityDiscoveryService.searchWithParameters(EntityDiscoveryService.java:458) > 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$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) > at > org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:82) > 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.discovery.EntityDiscoveryService$$EnhancerBySpringCGLIB$$95d844c8.searchWithParameters() > at > org.apache.atlas.web.rest.DiscoveryREST.searchWithParameters(DiscoveryREST.java:342) > at sun.reflect.GeneratedMethodAccessor181.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1712) > at
[jira] [Updated] (ATLAS-3444) Change Impala DDL qualifiedName and name to behave the same with Hive
[ https://issues.apache.org/jira/browse/ATLAS-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3444: - Description: CR : [https://reviews.apache.org/r/71594/] > Change Impala DDL qualifiedName and name to behave the same with Hive > - > > Key: ATLAS-3444 > URL: https://issues.apache.org/jira/browse/ATLAS-3444 > Project: Atlas > Issue Type: Improvement >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > > CR : [https://reviews.apache.org/r/71594/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3444) Change Impala DDL qualifiedName and name to behave the same with Hive
Le Ma created ATLAS-3444: Summary: Change Impala DDL qualifiedName and name to behave the same with Hive Key: ATLAS-3444 URL: https://issues.apache.org/jira/browse/ATLAS-3444 Project: Atlas Issue Type: Improvement Reporter: Le Ma Assignee: Le Ma -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3425) gremlin Script Execution Failed
[ https://issues.apache.org/jira/browse/ATLAS-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3425: - Description: In basic search, query parameters are: * typeName: * classificationName * tag attribute is boolean. * fulltext query is tag attribute name No results is found. below error message is found in the backend log Please check the attached image for basic seach parameters. javax.script.ScriptException: javax.script.ScriptException: groovy.lang.MissingPropertyException: No such property: in for class: org.apache.tinkerpop.gremlin.structure.T at org.apache.tinkerpop.gremlin.groovy.jsr223.GremlinGroovyScriptEngine.eval(GremlinGroovyScriptEngine.java:378) at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:233) at org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.executeGremlinScript(AtlasJanusGraph.java:368) at org.apache.atlas.discovery.ClassificationSearchProcessor.filter(ClassificationSearchProcessor.java:339) at org.apache.atlas.discovery.SearchProcessor.filter(SearchProcessor.java:156) at org.apache.atlas.discovery.FreeTextSearchProcessor.execute(FreeTextSearchProcessor.java:156) at org.apache.atlas.discovery.EntityDiscoveryService.searchWithSearchContext(EntityDiscoveryService.java:471) at org.apache.atlas.discovery.EntityDiscoveryService.searchWithParameters(EntityDiscoveryService.java:458) 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$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) at org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:82) 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.discovery.EntityDiscoveryService$$EnhancerBySpringCGLIB$$95d844c8.searchWithParameters() at org.apache.atlas.web.rest.DiscoveryREST.searchWithParameters(DiscoveryREST.java:342) at sun.reflect.GeneratedMethodAccessor181.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1712) at org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:104) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1699) was: - tag attribute is boolean. - error msg javax.script.ScriptException: javax.script.ScriptException: groovy.lang.MissingPropertyException: No such property: in for class: org.apache.tinkerpop.gremlin.structure.T at org.apache.tinkerpop.gremlin.groovy.jsr223.GremlinGroovyScriptEngine.eval(GremlinGroovyScriptEngine.java:378) at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:233) at
[jira] [Updated] (ATLAS-3425) gremlin Script Execution Failed
[ https://issues.apache.org/jira/browse/ATLAS-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3425: - Attachment: error log > gremlin Script Execution Failed > --- > > Key: ATLAS-3425 > URL: https://issues.apache.org/jira/browse/ATLAS-3425 > Project: Atlas > Issue Type: Bug >Reporter: Le Ma >Priority: Major > Attachments: error log, image.png > > > - tag attribute is boolean. > - error msg > javax.script.ScriptException: javax.script.ScriptException: > groovy.lang.MissingPropertyException: No such property: in for class: > org.apache.tinkerpop.gremlin.structure.T > at > org.apache.tinkerpop.gremlin.groovy.jsr223.GremlinGroovyScriptEngine.eval(GremlinGroovyScriptEngine.java:378) > at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:233) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.executeGremlinScript(AtlasJanusGraph.java:368) > at > org.apache.atlas.discovery.ClassificationSearchProcessor.filter(ClassificationSearchProcessor.java:339) > at org.apache.atlas.discovery.SearchProcessor.filter(SearchProcessor.java:156) > at > org.apache.atlas.discovery.FreeTextSearchProcessor.execute(FreeTextSearchProcessor.java:156) > at > org.apache.atlas.discovery.EntityDiscoveryService.searchWithSearchContext(EntityDiscoveryService.java:471) > at > org.apache.atlas.discovery.EntityDiscoveryService.searchWithParameters(EntityDiscoveryService.java:458) > 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$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) > at > org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:82) > 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.discovery.EntityDiscoveryService$$EnhancerBySpringCGLIB$$95d844c8.searchWithParameters() > at > org.apache.atlas.web.rest.DiscoveryREST.searchWithParameters(DiscoveryREST.java:342) > at sun.reflect.GeneratedMethodAccessor181.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1712) > at org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:104) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1699) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3425) gremlin Script Execution Failed
[ https://issues.apache.org/jira/browse/ATLAS-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3425: - Attachment: image.png > gremlin Script Execution Failed > --- > > Key: ATLAS-3425 > URL: https://issues.apache.org/jira/browse/ATLAS-3425 > Project: Atlas > Issue Type: Bug >Reporter: Le Ma >Priority: Major > Attachments: image.png > > > - tag attribute is boolean. > - error msg > javax.script.ScriptException: javax.script.ScriptException: > groovy.lang.MissingPropertyException: No such property: in for class: > org.apache.tinkerpop.gremlin.structure.T > at > org.apache.tinkerpop.gremlin.groovy.jsr223.GremlinGroovyScriptEngine.eval(GremlinGroovyScriptEngine.java:378) > at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:233) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.executeGremlinScript(AtlasJanusGraph.java:368) > at > org.apache.atlas.discovery.ClassificationSearchProcessor.filter(ClassificationSearchProcessor.java:339) > at org.apache.atlas.discovery.SearchProcessor.filter(SearchProcessor.java:156) > at > org.apache.atlas.discovery.FreeTextSearchProcessor.execute(FreeTextSearchProcessor.java:156) > at > org.apache.atlas.discovery.EntityDiscoveryService.searchWithSearchContext(EntityDiscoveryService.java:471) > at > org.apache.atlas.discovery.EntityDiscoveryService.searchWithParameters(EntityDiscoveryService.java:458) > 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$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) > at > org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:82) > 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.discovery.EntityDiscoveryService$$EnhancerBySpringCGLIB$$95d844c8.searchWithParameters() > at > org.apache.atlas.web.rest.DiscoveryREST.searchWithParameters(DiscoveryREST.java:342) > at sun.reflect.GeneratedMethodAccessor181.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1712) > at org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:104) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1699) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3425) gremlin Script Execution Failed
Le Ma created ATLAS-3425: Summary: gremlin Script Execution Failed Key: ATLAS-3425 URL: https://issues.apache.org/jira/browse/ATLAS-3425 Project: Atlas Issue Type: Bug Reporter: Le Ma Attachments: image.png - tag attribute is boolean. - error msg javax.script.ScriptException: javax.script.ScriptException: groovy.lang.MissingPropertyException: No such property: in for class: org.apache.tinkerpop.gremlin.structure.T at org.apache.tinkerpop.gremlin.groovy.jsr223.GremlinGroovyScriptEngine.eval(GremlinGroovyScriptEngine.java:378) at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:233) at org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.executeGremlinScript(AtlasJanusGraph.java:368) at org.apache.atlas.discovery.ClassificationSearchProcessor.filter(ClassificationSearchProcessor.java:339) at org.apache.atlas.discovery.SearchProcessor.filter(SearchProcessor.java:156) at org.apache.atlas.discovery.FreeTextSearchProcessor.execute(FreeTextSearchProcessor.java:156) at org.apache.atlas.discovery.EntityDiscoveryService.searchWithSearchContext(EntityDiscoveryService.java:471) at org.apache.atlas.discovery.EntityDiscoveryService.searchWithParameters(EntityDiscoveryService.java:458) 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$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) at org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:82) 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.discovery.EntityDiscoveryService$$EnhancerBySpringCGLIB$$95d844c8.searchWithParameters() at org.apache.atlas.web.rest.DiscoveryREST.searchWithParameters(DiscoveryREST.java:342) at sun.reflect.GeneratedMethodAccessor181.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1712) at org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:104) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1699) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3257) Enable atlas search classification with wildcard character *
[ https://issues.apache.org/jira/browse/ATLAS-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3257: - Description: As of now we can search by classification with full name only, atlas should provide wildcard character support. Review board link : [https://reviews.apache.org/r/71320/] was:As of now we can search by classification with full name only, atlas should provide wildcard character support. > Enable atlas search classification with wildcard character * > > > Key: ATLAS-3257 > URL: https://issues.apache.org/jira/browse/ATLAS-3257 > Project: Atlas > Issue Type: New Feature >Reporter: Weixia Xu >Assignee: Le Ma >Priority: Major > > As of now we can search by classification with full name only, atlas should > provide wildcard character support. > > Review board link : [https://reviews.apache.org/r/71320/] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (ATLAS-3327) Create internal vertex property for classification names and propagated classification names
[ https://issues.apache.org/jira/browse/ATLAS-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3327: - Description: CR: https://reviews.apache.org/r/71234/ > Create internal vertex property for classification names and propagated > classification names > > > Key: ATLAS-3327 > URL: https://issues.apache.org/jira/browse/ATLAS-3327 > Project: Atlas > Issue Type: Sub-task >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Attachments: ATLAS-3327-6.patch > > > CR: https://reviews.apache.org/r/71234/ -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (ATLAS-3327) Create internal vertex property for classification names and propagated classification names
[ https://issues.apache.org/jira/browse/ATLAS-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3327: - External issue URL: https://reviews.apache.org/r/71085/ (was: https://reviews.apache.org/r/71085/,) > Create internal vertex property for classification names and propagated > classification names > > > Key: ATLAS-3327 > URL: https://issues.apache.org/jira/browse/ATLAS-3327 > Project: Atlas > Issue Type: Sub-task >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Attachments: ATLAS-3327-6.patch > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (ATLAS-3327) Create internal vertex property for classification names and propagated classification names
[ https://issues.apache.org/jira/browse/ATLAS-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3327: - External issue URL: https://reviews.apache.org/r/71085/, > Create internal vertex property for classification names and propagated > classification names > > > Key: ATLAS-3327 > URL: https://issues.apache.org/jira/browse/ATLAS-3327 > Project: Atlas > Issue Type: Sub-task >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Attachments: ATLAS-3327-6.patch > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (ATLAS-3327) Create internal vertex property for classification names and propagated classification names
Le Ma created ATLAS-3327: Summary: Create internal vertex property for classification names and propagated classification names Key: ATLAS-3327 URL: https://issues.apache.org/jira/browse/ATLAS-3327 Project: Atlas Issue Type: Sub-task Reporter: Le Ma Assignee: Le Ma -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-3257) Enable atlas search classification with wildcard character *
[ https://issues.apache.org/jira/browse/ATLAS-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma reassigned ATLAS-3257: Assignee: Le Ma > Enable atlas search classification with wildcard character * > > > Key: ATLAS-3257 > URL: https://issues.apache.org/jira/browse/ATLAS-3257 > Project: Atlas > Issue Type: New Feature >Reporter: Weixia Xu >Assignee: Le Ma >Priority: Major > > As of now we can search by classification with full name only, atlas should > provide wildcard character support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3292) Remove legacy Attributes
[ https://issues.apache.org/jira/browse/ATLAS-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869772#comment-16869772 ] Le Ma commented on ATLAS-3292: -- Pre-commit job succeed : [https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1216/] > Remove legacy Attributes > > > Key: ATLAS-3292 > URL: https://issues.apache.org/jira/browse/ATLAS-3292 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Attachments: ATLAS-3292.patch, ATLAS-3292.patch > > > After introducing relationship attributes, legacy attributes should be > removed from the models. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3292) Remove legacy Attributes
[ https://issues.apache.org/jira/browse/ATLAS-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868838#comment-16868838 ] Le Ma commented on ATLAS-3292: -- Review board link : [https://reviews.apache.org/r/70909/] > Remove legacy Attributes > > > Key: ATLAS-3292 > URL: https://issues.apache.org/jira/browse/ATLAS-3292 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Attachments: ATLAS-3292.patch > > > After introducing relationship attributes, legacy attributes should be > removed from the models. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3292) Remove legacy Attributes
Le Ma created ATLAS-3292: Summary: Remove legacy Attributes Key: ATLAS-3292 URL: https://issues.apache.org/jira/browse/ATLAS-3292 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Le Ma Assignee: Le Ma After introducing relationship attributes, legacy attributes should be removed from the models. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3274) Updating relationship instance with a wrong guid throws 500 , expected is 400
[ https://issues.apache.org/jira/browse/ATLAS-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860293#comment-16860293 ] Le Ma commented on ATLAS-3274: -- review board - [https://reviews.apache.org/r/70823/] > Updating relationship instance with a wrong guid throws 500 , expected is 400 > - > > Key: ATLAS-3274 > URL: https://issues.apache.org/jira/browse/ATLAS-3274 > Project: Atlas > Issue Type: Bug >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Attachments: ATLAS-3274.patch > > > 1. Create 3 entities. > 2. Create a relationship between the 2 entities entity1 and entity2. > 3. Update the relationship and modify the end2 's guid to entity3's guid . > 4. Request throws 500 Internal server exception instead of 400 Bad request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3274) Updating relationship instance with a wrong guid throws 500 , expected is 400
Le Ma created ATLAS-3274: Summary: Updating relationship instance with a wrong guid throws 500 , expected is 400 Key: ATLAS-3274 URL: https://issues.apache.org/jira/browse/ATLAS-3274 Project: Atlas Issue Type: Bug Reporter: Le Ma Assignee: Le Ma 1. Create 3 entities. 2. Create a relationship between the 2 entities entity1 and entity2. 3. Update the relationship and modify the end2 's guid to entity3's guid . 4. Request throws 500 Internal server exception instead of 400 Bad request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3229) DDL should not capture dml queries
[ https://issues.apache.org/jira/browse/ATLAS-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3229: - External issue URL: https://reviews.apache.org/r/70720/ > DDL should not capture dml queries > -- > > Key: ATLAS-3229 > URL: https://issues.apache.org/jira/browse/ATLAS-3229 > Project: Atlas > Issue Type: Bug >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Attachments: ATLAS-3229.patch, Screenshot 2019-05-24 at 8.46.02 AM.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3229) DDL should not capture dml queries
[ https://issues.apache.org/jira/browse/ATLAS-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853298#comment-16853298 ] Le Ma commented on ATLAS-3229: -- Pre-commit job succeed - [https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1149/] > DDL should not capture dml queries > -- > > Key: ATLAS-3229 > URL: https://issues.apache.org/jira/browse/ATLAS-3229 > Project: Atlas > Issue Type: Bug >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Attachments: ATLAS-3229.patch, Screenshot 2019-05-24 at 8.46.02 AM.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3229) DDL should not capture dml queries
Le Ma created ATLAS-3229: Summary: DDL should not capture dml queries Key: ATLAS-3229 URL: https://issues.apache.org/jira/browse/ATLAS-3229 Project: Atlas Issue Type: Bug Reporter: Le Ma Assignee: Le Ma -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3220) Change hiveDDL Name and QualifiedName
Le Ma created ATLAS-3220: Summary: Change hiveDDL Name and QualifiedName Key: ATLAS-3220 URL: https://issues.apache.org/jira/browse/ATLAS-3220 Project: Atlas Issue Type: Bug Reporter: Le Ma Assignee: Le Ma Current hiveDDL entity use queryText as both name and qualifiedName, which make info duplicated in the UI page of hiveDDL entity. This change uses db/table 's qualifiedName and it timestamp as its new qualifiedName. We could keep queryText as its name, which shows up at the relationship tab of either table or db, users can easily find out queryText without clicking into the hiveDDL entity ui page. If the queryText is too long, I hope front-end could do some truncation/beautify. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-3208) Handle process/process_exec creation for HMS hook
[ https://issues.apache.org/jira/browse/ATLAS-3208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma resolved ATLAS-3208. -- Resolution: Fixed > Handle process/process_exec creation for HMS hook > - > > Key: ATLAS-3208 > URL: https://issues.apache.org/jira/browse/ATLAS-3208 > Project: Atlas > Issue Type: Bug >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3204) HMS hook fails to process create_table event due to ATLAS-3197
[
https://issues.apache.org/jira/browse/ATLAS-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Le Ma updated ATLAS-3204:
-
Attachment: ATLAS-3204-1.patch
> HMS hook fails to process create_table event due to ATLAS-3197
> --
>
> Key: ATLAS-3204
> URL: https://issues.apache.org/jira/browse/ATLAS-3204
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Na Li
>Assignee: Le Ma
>Priority: Major
> Attachments: ATLAS-3204-1.patch, ATLAS-3204.001.patch
>
>
> ATLAS-3197 creates Hive DDL entity even in HMS hook when processing
> create_table event, where the HiveContext is null. That causes
> NullPointerException.
> The fix should generate AtlasEntity based on its in HiveHook or HMS hook.
> {code}
> 2019-05-09 23:15:37,936 ERROR - [main:] ~
> HiveMetastoreHook.handleEvent(org.apache.hadoop.hive.metastore.events.CreateTableEvent@1850f2da):
> failed to process operation {} (HiveMetastoreHookImpl$HiveMetastoreHook:169)
> java.lang.NullPointerException
> at
> org.apache.atlas.hive.hook.events.BaseHiveEvent.createHiveDDLEntity(BaseHiveEvent.java:692)
> at
> org.apache.atlas.hive.hook.events.BaseHiveEvent.createHiveDDLEntity(BaseHiveEvent.java:671)
> at
> org.apache.atlas.hive.hook.events.CreateTable.processTable(CreateTable.java:153)
> at
> org.apache.atlas.hive.hook.events.CreateTable.getHiveMetastoreEntities(CreateTable.java:77)
> at
> org.apache.atlas.hive.hook.events.CreateTable.getNotificationMessages(CreateTable.java:52)
> at
> org.apache.atlas.hive.hook.HiveMetastoreHookImpl$HiveMetastoreHook.handleEvent(HiveMetastoreHookImpl.java:166)
> at
> org.apache.atlas.hive.hook.HiveMetastoreHookImpl.onCreateTable(HiveMetastoreHookImpl.java:77)
> at
> org.apache.hadoop.hive.metastore.MetaStoreListenerNotifier$20.notify(MetaStoreListenerNotifier.java:92)
> at
> org.apache.hadoop.hive.metastore.MetaStoreListenerNotifier.notifyEvent(MetaStoreListenerNotifier.java:267)
> at
> org.apache.hadoop.hive.metastore.MetaStoreListenerNotifier.notifyEvent(MetaStoreListenerNotifier.java:329)
> at
> org.apache.hadoop.hive.metastore.MetaStoreListenerNotifier.notifyEvent(MetaStoreListenerNotifier.java:367)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_core(HiveMetaStore.java:1999)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_core(HiveMetaStore.java:1786)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_with_environment_context(HiveMetaStore.java:2035)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:147)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:108)
> at com.sun.proxy.$Proxy28.create_table_with_environment_context(Unknown
> Source)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.create_table_with_environment_context(HiveMetaStoreClient.java:2867)
> at
> org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient.create_table_with_environment_context(SessionHiveMetaStoreClient.java:121)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:837)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:822)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.invoke(RetryingMetaStoreClient.java:212)
> at com.sun.proxy.$Proxy29.createTable(Unknown Source)
> at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:921)
> at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:937)
> at org.apache.hadoop.hive.ql.exec.DDLTask.createTable(DDLTask.java:4954)
> at org.apache.hadoop.hive.ql.exec.DDLTask.execute(DDLTask.java:428)
> at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:205)
> at
> org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:97)
> at
[jira] [Updated] (ATLAS-3197) Add QueryText for hive_table and hive_db
[ https://issues.apache.org/jira/browse/ATLAS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3197: - Attachment: (was: ATLAS-3197-1.patch) > Add QueryText for hive_table and hive_db > > > Key: ATLAS-3197 > URL: https://issues.apache.org/jira/browse/ATLAS-3197 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3197.patch > > > This patch introduced a model called Hive_table_ddl and hive_db_ddl which are > used to track commands that are executed either on a table entity or bd > entity. DDL entities will be added to a table/db entity through > relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when > a new command is executed, a new ddl entity will be created, it will append > to the existing ddlQueries field if a table/db has already been created. Once > a table/db is deleted, all these relationship attributes will be deleted as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3197) Add QueryText for hive_table and hive_db
[ https://issues.apache.org/jira/browse/ATLAS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838731#comment-16838731 ] Le Ma commented on ATLAS-3197: -- [https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1103/] pre-commit job succeed for ATLAS-3197-1.patch > Add QueryText for hive_table and hive_db > > > Key: ATLAS-3197 > URL: https://issues.apache.org/jira/browse/ATLAS-3197 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3197-1.patch, ATLAS-3197.patch > > > This patch introduced a model called Hive_table_ddl and hive_db_ddl which are > used to track commands that are executed either on a table entity or bd > entity. DDL entities will be added to a table/db entity through > relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when > a new command is executed, a new ddl entity will be created, it will append > to the existing ddlQueries field if a table/db has already been created. Once > a table/db is deleted, all these relationship attributes will be deleted as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3197) Add QueryText for hive_table and hive_db
[ https://issues.apache.org/jira/browse/ATLAS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3197: - Attachment: ATLAS-3197-1.patch > Add QueryText for hive_table and hive_db > > > Key: ATLAS-3197 > URL: https://issues.apache.org/jira/browse/ATLAS-3197 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3197-1.patch, ATLAS-3197.patch > > > This patch introduced a model called Hive_table_ddl and hive_db_ddl which are > used to track commands that are executed either on a table entity or bd > entity. DDL entities will be added to a table/db entity through > relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when > a new command is executed, a new ddl entity will be created, it will append > to the existing ddlQueries field if a table/db has already been created. Once > a table/db is deleted, all these relationship attributes will be deleted as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3204) HMS hook fails to process create_table event due to ATLAS-3197
[
https://issues.apache.org/jira/browse/ATLAS-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16837643#comment-16837643
]
Le Ma commented on ATLAS-3204:
--
[~LinaAtAustin] Thanks for tracking down the issue. I am working on it right
now. will update the Jira as soon as i am done with the testing.
Thanks,
Le
> HMS hook fails to process create_table event due to ATLAS-3197
> --
>
> Key: ATLAS-3204
> URL: https://issues.apache.org/jira/browse/ATLAS-3204
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Na Li
>Assignee: Le Ma
>Priority: Major
> Attachments: ATLAS-3204.001.patch
>
>
> ATLAS-3197 creates Hive DDL entity even in HMS hook when processing
> create_table event, where the HiveContext is null. That causes
> NullPointerException.
> The fix should generate AtlasEntity based on its in HiveHook or HMS hook.
> {code}
> 2019-05-09 23:15:37,936 ERROR - [main:] ~
> HiveMetastoreHook.handleEvent(org.apache.hadoop.hive.metastore.events.CreateTableEvent@1850f2da):
> failed to process operation {} (HiveMetastoreHookImpl$HiveMetastoreHook:169)
> java.lang.NullPointerException
> at
> org.apache.atlas.hive.hook.events.BaseHiveEvent.createHiveDDLEntity(BaseHiveEvent.java:692)
> at
> org.apache.atlas.hive.hook.events.BaseHiveEvent.createHiveDDLEntity(BaseHiveEvent.java:671)
> at
> org.apache.atlas.hive.hook.events.CreateTable.processTable(CreateTable.java:153)
> at
> org.apache.atlas.hive.hook.events.CreateTable.getHiveMetastoreEntities(CreateTable.java:77)
> at
> org.apache.atlas.hive.hook.events.CreateTable.getNotificationMessages(CreateTable.java:52)
> at
> org.apache.atlas.hive.hook.HiveMetastoreHookImpl$HiveMetastoreHook.handleEvent(HiveMetastoreHookImpl.java:166)
> at
> org.apache.atlas.hive.hook.HiveMetastoreHookImpl.onCreateTable(HiveMetastoreHookImpl.java:77)
> at
> org.apache.hadoop.hive.metastore.MetaStoreListenerNotifier$20.notify(MetaStoreListenerNotifier.java:92)
> at
> org.apache.hadoop.hive.metastore.MetaStoreListenerNotifier.notifyEvent(MetaStoreListenerNotifier.java:267)
> at
> org.apache.hadoop.hive.metastore.MetaStoreListenerNotifier.notifyEvent(MetaStoreListenerNotifier.java:329)
> at
> org.apache.hadoop.hive.metastore.MetaStoreListenerNotifier.notifyEvent(MetaStoreListenerNotifier.java:367)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_core(HiveMetaStore.java:1999)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_core(HiveMetaStore.java:1786)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_with_environment_context(HiveMetaStore.java:2035)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:147)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:108)
> at com.sun.proxy.$Proxy28.create_table_with_environment_context(Unknown
> Source)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.create_table_with_environment_context(HiveMetaStoreClient.java:2867)
> at
> org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient.create_table_with_environment_context(SessionHiveMetaStoreClient.java:121)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:837)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:822)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.invoke(RetryingMetaStoreClient.java:212)
> at com.sun.proxy.$Proxy29.createTable(Unknown Source)
> at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:921)
> at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:937)
> at org.apache.hadoop.hive.ql.exec.DDLTask.createTable(DDLTask.java:4954)
> at org.apache.hadoop.hive.ql.exec.DDLTask.execute(DDLTask.java:428)
> at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:205)
>
[jira] [Created] (ATLAS-3208) Handle process/process_exec creation for HMS hook
Le Ma created ATLAS-3208: Summary: Handle process/process_exec creation for HMS hook Key: ATLAS-3208 URL: https://issues.apache.org/jira/browse/ATLAS-3208 Project: Atlas Issue Type: Bug Reporter: Le Ma Assignee: Le Ma -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-3207) Run pre-commit job once a patch is submitted on jira
Le Ma created ATLAS-3207: Summary: Run pre-commit job once a patch is submitted on jira Key: ATLAS-3207 URL: https://issues.apache.org/jira/browse/ATLAS-3207 Project: Atlas Issue Type: New Feature Reporter: Le Ma It would be nice to have the automation that could run pre-commit job once a patch is submitted to Jira. By adding this, it could be easier for contributors to validate their patch and once is this part of committing process, we could commit more bug-free code. I've heard that Hive use this approach for commit. Thankd -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-3204) HMS hook fails to process create_table event due to ATLAS-3197
[
https://issues.apache.org/jira/browse/ATLAS-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Le Ma reassigned ATLAS-3204:
Assignee: Le Ma (was: Sarath Subramanian)
> HMS hook fails to process create_table event due to ATLAS-3197
> --
>
> Key: ATLAS-3204
> URL: https://issues.apache.org/jira/browse/ATLAS-3204
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.0.0
>Reporter: Na Li
>Assignee: Le Ma
>Priority: Major
> Attachments: ATLAS-3204.001.patch
>
>
> ATLAS-3197 creates Hive DDL entity even in HMS hook when processing
> create_table event, where the HiveContext is null. That causes
> NullPointerException.
> The fix should generate AtlasEntity based on its in HiveHook or HMS hook.
> {code}
> 2019-05-09 23:15:37,936 ERROR - [main:] ~
> HiveMetastoreHook.handleEvent(org.apache.hadoop.hive.metastore.events.CreateTableEvent@1850f2da):
> failed to process operation {} (HiveMetastoreHookImpl$HiveMetastoreHook:169)
> java.lang.NullPointerException
> at
> org.apache.atlas.hive.hook.events.BaseHiveEvent.createHiveDDLEntity(BaseHiveEvent.java:692)
> at
> org.apache.atlas.hive.hook.events.BaseHiveEvent.createHiveDDLEntity(BaseHiveEvent.java:671)
> at
> org.apache.atlas.hive.hook.events.CreateTable.processTable(CreateTable.java:153)
> at
> org.apache.atlas.hive.hook.events.CreateTable.getHiveMetastoreEntities(CreateTable.java:77)
> at
> org.apache.atlas.hive.hook.events.CreateTable.getNotificationMessages(CreateTable.java:52)
> at
> org.apache.atlas.hive.hook.HiveMetastoreHookImpl$HiveMetastoreHook.handleEvent(HiveMetastoreHookImpl.java:166)
> at
> org.apache.atlas.hive.hook.HiveMetastoreHookImpl.onCreateTable(HiveMetastoreHookImpl.java:77)
> at
> org.apache.hadoop.hive.metastore.MetaStoreListenerNotifier$20.notify(MetaStoreListenerNotifier.java:92)
> at
> org.apache.hadoop.hive.metastore.MetaStoreListenerNotifier.notifyEvent(MetaStoreListenerNotifier.java:267)
> at
> org.apache.hadoop.hive.metastore.MetaStoreListenerNotifier.notifyEvent(MetaStoreListenerNotifier.java:329)
> at
> org.apache.hadoop.hive.metastore.MetaStoreListenerNotifier.notifyEvent(MetaStoreListenerNotifier.java:367)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_core(HiveMetaStore.java:1999)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_core(HiveMetaStore.java:1786)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.create_table_with_environment_context(HiveMetaStore.java:2035)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:147)
> at
> org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:108)
> at com.sun.proxy.$Proxy28.create_table_with_environment_context(Unknown
> Source)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.create_table_with_environment_context(HiveMetaStoreClient.java:2867)
> at
> org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient.create_table_with_environment_context(SessionHiveMetaStoreClient.java:121)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:837)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:822)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.invoke(RetryingMetaStoreClient.java:212)
> at com.sun.proxy.$Proxy29.createTable(Unknown Source)
> at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:921)
> at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:937)
> at org.apache.hadoop.hive.ql.exec.DDLTask.createTable(DDLTask.java:4954)
> at org.apache.hadoop.hive.ql.exec.DDLTask.execute(DDLTask.java:428)
> at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:205)
> at
> org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:97)
> at
[jira] [Updated] (ATLAS-3197) Add QueryText for hive_table and hive_db
[ https://issues.apache.org/jira/browse/ATLAS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3197: - Attachment: ATLAS-3197-2.patch > Add QueryText for hive_table and hive_db > > > Key: ATLAS-3197 > URL: https://issues.apache.org/jira/browse/ATLAS-3197 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3197-2.patch, ATLAS-3197.patch > > > This patch introduced a model called Hive_table_ddl and hive_db_ddl which are > used to track commands that are executed either on a table entity or bd > entity. DDL entities will be added to a table/db entity through > relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when > a new command is executed, a new ddl entity will be created, it will append > to the existing ddlQueries field if a table/db has already been created. Once > a table/db is deleted, all these relationship attributes will be deleted as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3197) Add QueryText for hive_table and hive_db
[ https://issues.apache.org/jira/browse/ATLAS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3197: - Attachment: (was: ATLAS-3197.patch) > Add QueryText for hive_table and hive_db > > > Key: ATLAS-3197 > URL: https://issues.apache.org/jira/browse/ATLAS-3197 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3197.patch > > > This patch introduced a model called Hive_table_ddl and hive_db_ddl which are > used to track commands that are executed either on a table entity or bd > entity. DDL entities will be added to a table/db entity through > relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when > a new command is executed, a new ddl entity will be created, it will append > to the existing ddlQueries field if a table/db has already been created. Once > a table/db is deleted, all these relationship attributes will be deleted as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3197) Add QueryText for hive_table and hive_db
[ https://issues.apache.org/jira/browse/ATLAS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3197: - Attachment: ATLAS-3197.patch > Add QueryText for hive_table and hive_db > > > Key: ATLAS-3197 > URL: https://issues.apache.org/jira/browse/ATLAS-3197 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3197.patch > > > This patch introduced a model called Hive_table_ddl and hive_db_ddl which are > used to track commands that are executed either on a table entity or bd > entity. DDL entities will be added to a table/db entity through > relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when > a new command is executed, a new ddl entity will be created, it will append > to the existing ddlQueries field if a table/db has already been created. Once > a table/db is deleted, all these relationship attributes will be deleted as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3197) Add QueryText for hive_table and hive_db
[ https://issues.apache.org/jira/browse/ATLAS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3197: - Attachment: ATLAS-3197.patch > Add QueryText for hive_table and hive_db > > > Key: ATLAS-3197 > URL: https://issues.apache.org/jira/browse/ATLAS-3197 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3197.patch > > > This patch introduced a model called Hive_table_ddl and hive_db_ddl which are > used to track commands that are executed either on a table entity or bd > entity. DDL entities will be added to a table/db entity through > relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when > a new command is executed, a new ddl entity will be created, it will append > to the existing ddlQueries field if a table/db has already been created. Once > a table/db is deleted, all these relationship attributes will be deleted as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3197) Add QueryText for hive_table and hive_db
[ https://issues.apache.org/jira/browse/ATLAS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3197: - Attachment: (was: ATLAS-3197.patch) > Add QueryText for hive_table and hive_db > > > Key: ATLAS-3197 > URL: https://issues.apache.org/jira/browse/ATLAS-3197 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Fix For: trunk > > > This patch introduced a model called Hive_table_ddl and hive_db_ddl which are > used to track commands that are executed either on a table entity or bd > entity. DDL entities will be added to a table/db entity through > relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when > a new command is executed, a new ddl entity will be created, it will append > to the existing ddlQueries field if a table/db has already been created. Once > a table/db is deleted, all these relationship attributes will be deleted as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3197) Add QueryText for hive_table and hive_db
[ https://issues.apache.org/jira/browse/ATLAS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3197: - Attachment: (was: ATLAS-3197.patch) > Add QueryText for hive_table and hive_db > > > Key: ATLAS-3197 > URL: https://issues.apache.org/jira/browse/ATLAS-3197 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > > This patch introduced a model called Hive_table_ddl and hive_db_ddl which are > used to track commands that are executed either on a table entity or bd > entity. DDL entities will be added to a table/db entity through > relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when > a new command is executed, a new ddl entity will be created, it will append > to the existing ddlQueries field if a table/db has already been created. Once > a table/db is deleted, all these relationship attributes will be deleted as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3114) Issue with concurrent bulk inserts for entities
[ https://issues.apache.org/jira/browse/ATLAS-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3114: - Attachment: (was: 2010-rdbms_model.json) > Issue with concurrent bulk inserts for entities > --- > > Key: ATLAS-3114 > URL: https://issues.apache.org/jira/browse/ATLAS-3114 > Project: Atlas > Issue Type: Bug >Reporter: Ayush Nigam >Assignee: chaitali borole >Priority: Major > Attachments: 2010-rdbms_model.json, ATLAS-3114.patch, > AtlasClientV2Test.java, Error.txt, Screen Shot 2019-05-07 at 4.31.38 PM.png, > Screen Shot 2019-05-07 at 4.32.00 PM.png, Screen Shot 2019-05-07 at 4.32.26 > PM.png, image-2019-05-07-09-28-21-892.png, model.json > > > We have a model with tables having attribute 'columns' in which we are > attaching list of object ids for all columns once these are created. We are > using clientV2 java APIs. > We are doing bulk operation for columns and parallelizing the tables. > Sometimes the issue is that bulk creation for columns is successful,i.e. > atlas don't throw any exception but we get some columns as created,some as > updated,whereas as none of the columns existed before.Even it misses out some > entities while creating.Some are created and some are just silently missed > without throwing an exception. > So to sum up issue is there for concurrent bulk create/update calls.It works > for concurrent single entity create/update calls. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3114) Issue with concurrent bulk inserts for entities
[ https://issues.apache.org/jira/browse/ATLAS-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3114: - Attachment: 2010-rdbms_model.json > Issue with concurrent bulk inserts for entities > --- > > Key: ATLAS-3114 > URL: https://issues.apache.org/jira/browse/ATLAS-3114 > Project: Atlas > Issue Type: Bug >Reporter: Ayush Nigam >Assignee: chaitali borole >Priority: Major > Attachments: 2010-rdbms_model.json, ATLAS-3114.patch, > AtlasClientV2Test.java, Error.txt, Screen Shot 2019-05-07 at 4.31.38 PM.png, > Screen Shot 2019-05-07 at 4.32.00 PM.png, Screen Shot 2019-05-07 at 4.32.26 > PM.png, image-2019-05-07-09-28-21-892.png, model.json > > > We have a model with tables having attribute 'columns' in which we are > attaching list of object ids for all columns once these are created. We are > using clientV2 java APIs. > We are doing bulk operation for columns and parallelizing the tables. > Sometimes the issue is that bulk creation for columns is successful,i.e. > atlas don't throw any exception but we get some columns as created,some as > updated,whereas as none of the columns existed before.Even it misses out some > entities while creating.Some are created and some are just silently missed > without throwing an exception. > So to sum up issue is there for concurrent bulk create/update calls.It works > for concurrent single entity create/update calls. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3114) Issue with concurrent bulk inserts for entities
[ https://issues.apache.org/jira/browse/ATLAS-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3114: - Attachment: Screen Shot 2019-05-07 at 4.32.26 PM.png Screen Shot 2019-05-07 at 4.32.00 PM.png Screen Shot 2019-05-07 at 4.31.38 PM.png > Issue with concurrent bulk inserts for entities > --- > > Key: ATLAS-3114 > URL: https://issues.apache.org/jira/browse/ATLAS-3114 > Project: Atlas > Issue Type: Bug >Reporter: Ayush Nigam >Assignee: chaitali borole >Priority: Major > Attachments: 2010-rdbms_model.json, ATLAS-3114.patch, > AtlasClientV2Test.java, Error.txt, Screen Shot 2019-05-07 at 4.31.38 PM.png, > Screen Shot 2019-05-07 at 4.32.00 PM.png, Screen Shot 2019-05-07 at 4.32.26 > PM.png, image-2019-05-07-09-28-21-892.png, model.json > > > We have a model with tables having attribute 'columns' in which we are > attaching list of object ids for all columns once these are created. We are > using clientV2 java APIs. > We are doing bulk operation for columns and parallelizing the tables. > Sometimes the issue is that bulk creation for columns is successful,i.e. > atlas don't throw any exception but we get some columns as created,some as > updated,whereas as none of the columns existed before.Even it misses out some > entities while creating.Some are created and some are just silently missed > without throwing an exception. > So to sum up issue is there for concurrent bulk create/update calls.It works > for concurrent single entity create/update calls. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3114) Issue with concurrent bulk inserts for entities
[ https://issues.apache.org/jira/browse/ATLAS-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3114: - Attachment: (was: Screen Shot 2019-05-07 at 4.31.38 PM.png) > Issue with concurrent bulk inserts for entities > --- > > Key: ATLAS-3114 > URL: https://issues.apache.org/jira/browse/ATLAS-3114 > Project: Atlas > Issue Type: Bug >Reporter: Ayush Nigam >Assignee: chaitali borole >Priority: Major > Attachments: 2010-rdbms_model.json, ATLAS-3114.patch, > AtlasClientV2Test.java, Error.txt, image-2019-05-07-09-28-21-892.png, > model.json > > > We have a model with tables having attribute 'columns' in which we are > attaching list of object ids for all columns once these are created. We are > using clientV2 java APIs. > We are doing bulk operation for columns and parallelizing the tables. > Sometimes the issue is that bulk creation for columns is successful,i.e. > atlas don't throw any exception but we get some columns as created,some as > updated,whereas as none of the columns existed before.Even it misses out some > entities while creating.Some are created and some are just silently missed > without throwing an exception. > So to sum up issue is there for concurrent bulk create/update calls.It works > for concurrent single entity create/update calls. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3114) Issue with concurrent bulk inserts for entities
[ https://issues.apache.org/jira/browse/ATLAS-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3114: - Attachment: (was: Screen Shot 2019-05-07 at 4.31.26 PM.png) > Issue with concurrent bulk inserts for entities > --- > > Key: ATLAS-3114 > URL: https://issues.apache.org/jira/browse/ATLAS-3114 > Project: Atlas > Issue Type: Bug >Reporter: Ayush Nigam >Assignee: chaitali borole >Priority: Major > Attachments: 2010-rdbms_model.json, ATLAS-3114.patch, > AtlasClientV2Test.java, Error.txt, image-2019-05-07-09-28-21-892.png, > model.json > > > We have a model with tables having attribute 'columns' in which we are > attaching list of object ids for all columns once these are created. We are > using clientV2 java APIs. > We are doing bulk operation for columns and parallelizing the tables. > Sometimes the issue is that bulk creation for columns is successful,i.e. > atlas don't throw any exception but we get some columns as created,some as > updated,whereas as none of the columns existed before.Even it misses out some > entities while creating.Some are created and some are just silently missed > without throwing an exception. > So to sum up issue is there for concurrent bulk create/update calls.It works > for concurrent single entity create/update calls. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3114) Issue with concurrent bulk inserts for entities
[ https://issues.apache.org/jira/browse/ATLAS-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3114: - Attachment: (was: Screen Shot 2019-05-07 at 4.32.26 PM.png) > Issue with concurrent bulk inserts for entities > --- > > Key: ATLAS-3114 > URL: https://issues.apache.org/jira/browse/ATLAS-3114 > Project: Atlas > Issue Type: Bug >Reporter: Ayush Nigam >Assignee: chaitali borole >Priority: Major > Attachments: 2010-rdbms_model.json, ATLAS-3114.patch, > AtlasClientV2Test.java, Error.txt, image-2019-05-07-09-28-21-892.png, > model.json > > > We have a model with tables having attribute 'columns' in which we are > attaching list of object ids for all columns once these are created. We are > using clientV2 java APIs. > We are doing bulk operation for columns and parallelizing the tables. > Sometimes the issue is that bulk creation for columns is successful,i.e. > atlas don't throw any exception but we get some columns as created,some as > updated,whereas as none of the columns existed before.Even it misses out some > entities while creating.Some are created and some are just silently missed > without throwing an exception. > So to sum up issue is there for concurrent bulk create/update calls.It works > for concurrent single entity create/update calls. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3114) Issue with concurrent bulk inserts for entities
[ https://issues.apache.org/jira/browse/ATLAS-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3114: - Attachment: (was: Screen Shot 2019-05-07 at 4.32.00 PM.png) > Issue with concurrent bulk inserts for entities > --- > > Key: ATLAS-3114 > URL: https://issues.apache.org/jira/browse/ATLAS-3114 > Project: Atlas > Issue Type: Bug >Reporter: Ayush Nigam >Assignee: chaitali borole >Priority: Major > Attachments: 2010-rdbms_model.json, ATLAS-3114.patch, > AtlasClientV2Test.java, Error.txt, image-2019-05-07-09-28-21-892.png, > model.json > > > We have a model with tables having attribute 'columns' in which we are > attaching list of object ids for all columns once these are created. We are > using clientV2 java APIs. > We are doing bulk operation for columns and parallelizing the tables. > Sometimes the issue is that bulk creation for columns is successful,i.e. > atlas don't throw any exception but we get some columns as created,some as > updated,whereas as none of the columns existed before.Even it misses out some > entities while creating.Some are created and some are just silently missed > without throwing an exception. > So to sum up issue is there for concurrent bulk create/update calls.It works > for concurrent single entity create/update calls. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3114) Issue with concurrent bulk inserts for entities
[ https://issues.apache.org/jira/browse/ATLAS-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3114: - Attachment: Screen Shot 2019-05-07 at 4.32.26 PM.png Screen Shot 2019-05-07 at 4.32.00 PM.png Screen Shot 2019-05-07 at 4.31.38 PM.png Screen Shot 2019-05-07 at 4.31.26 PM.png > Issue with concurrent bulk inserts for entities > --- > > Key: ATLAS-3114 > URL: https://issues.apache.org/jira/browse/ATLAS-3114 > Project: Atlas > Issue Type: Bug >Reporter: Ayush Nigam >Assignee: chaitali borole >Priority: Major > Attachments: 2010-rdbms_model.json, ATLAS-3114.patch, > AtlasClientV2Test.java, Error.txt, Screen Shot 2019-05-07 at 4.31.26 PM.png, > Screen Shot 2019-05-07 at 4.31.38 PM.png, Screen Shot 2019-05-07 at 4.32.00 > PM.png, Screen Shot 2019-05-07 at 4.32.26 PM.png, > image-2019-05-07-09-28-21-892.png, model.json > > > We have a model with tables having attribute 'columns' in which we are > attaching list of object ids for all columns once these are created. We are > using clientV2 java APIs. > We are doing bulk operation for columns and parallelizing the tables. > Sometimes the issue is that bulk creation for columns is successful,i.e. > atlas don't throw any exception but we get some columns as created,some as > updated,whereas as none of the columns existed before.Even it misses out some > entities while creating.Some are created and some are just silently missed > without throwing an exception. > So to sum up issue is there for concurrent bulk create/update calls.It works > for concurrent single entity create/update calls. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3114) Issue with concurrent bulk inserts for entities
[ https://issues.apache.org/jira/browse/ATLAS-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835195#comment-16835195 ] Le Ma commented on ATLAS-3114: -- Hello [~sreenivasulu_nallap...@intuit.com] , Thanks for the update. I've attached the screenshots I took after I ran the attached patch file. I will re-upload the model I am using again. Thanks, Le > Issue with concurrent bulk inserts for entities > --- > > Key: ATLAS-3114 > URL: https://issues.apache.org/jira/browse/ATLAS-3114 > Project: Atlas > Issue Type: Bug >Reporter: Ayush Nigam >Assignee: chaitali borole >Priority: Major > Attachments: 2010-rdbms_model.json, ATLAS-3114.patch, > AtlasClientV2Test.java, Error.txt, image-2019-05-07-09-28-21-892.png, > model.json > > > We have a model with tables having attribute 'columns' in which we are > attaching list of object ids for all columns once these are created. We are > using clientV2 java APIs. > We are doing bulk operation for columns and parallelizing the tables. > Sometimes the issue is that bulk creation for columns is successful,i.e. > atlas don't throw any exception but we get some columns as created,some as > updated,whereas as none of the columns existed before.Even it misses out some > entities while creating.Some are created and some are just silently missed > without throwing an exception. > So to sum up issue is there for concurrent bulk create/update calls.It works > for concurrent single entity create/update calls. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3197) Add QueryText for hive_table and hive_db
[ https://issues.apache.org/jira/browse/ATLAS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3197: - Attachment: (was: ATLAS-3197.patch) > Add QueryText for hive_table and hive_db > > > Key: ATLAS-3197 > URL: https://issues.apache.org/jira/browse/ATLAS-3197 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Attachments: ATLAS-3197.patch > > > This patch introduced a model called Hive_table_ddl and hive_db_ddl which are > used to track commands that are executed either on a table entity or bd > entity. DDL entities will be added to a table/db entity through > relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when > a new command is executed, a new ddl entity will be created, it will append > to the existing ddlQueries field if a table/db has already been created. Once > a table/db is deleted, all these relationship attributes will be deleted as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3197) Add QueryText for hive_table and hive_db
[ https://issues.apache.org/jira/browse/ATLAS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3197: - Attachment: (was: ATLAS-3197.patch) > Add QueryText for hive_table and hive_db > > > Key: ATLAS-3197 > URL: https://issues.apache.org/jira/browse/ATLAS-3197 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Attachments: ATLAS-3197.patch > > > This patch introduced a model called Hive_table_ddl and hive_db_ddl which are > used to track commands that are executed either on a table entity or bd > entity. DDL entities will be added to a table/db entity through > relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when > a new command is executed, a new ddl entity will be created, it will append > to the existing ddlQueries field if a table/db has already been created. Once > a table/db is deleted, all these relationship attributes will be deleted as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3197) Add QueryText for hive_table and hive_db
[ https://issues.apache.org/jira/browse/ATLAS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3197: - Description: This patch introduced a model called Hive_table_ddl and hive_db_ddl which are used to track commands that are executed either on a table entity or bd entity. DDL entities will be added to a table/db entity through relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when a new command is executed, a new ddl entity will be created, it will append to the existing DDLQueries field if a table/db has already been created. Once a table/db is deleted, all these relationship attribute will be deleted as well. > Add QueryText for hive_table and hive_db > > > Key: ATLAS-3197 > URL: https://issues.apache.org/jira/browse/ATLAS-3197 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Attachments: ATLAS-3197.patch > > > This patch introduced a model called Hive_table_ddl and hive_db_ddl which are > used to track commands that are executed either on a table entity or bd > entity. DDL entities will be added to a table/db entity through > relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when > a new command is executed, a new ddl entity will be created, it will append > to the existing DDLQueries field if a table/db has already been created. Once > a table/db is deleted, all these relationship attribute will be deleted as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3197) Add QueryText for hive_table and hive_db
[ https://issues.apache.org/jira/browse/ATLAS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3197: - External issue URL: https://reviews.apache.org/r/70605/ > Add QueryText for hive_table and hive_db > > > Key: ATLAS-3197 > URL: https://issues.apache.org/jira/browse/ATLAS-3197 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Attachments: ATLAS-3197.patch > > > This patch introduced a model called Hive_table_ddl and hive_db_ddl which are > used to track commands that are executed either on a table entity or bd > entity. DDL entities will be added to a table/db entity through > relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when > a new command is executed, a new ddl entity will be created, it will append > to the existing ddlQueries field if a table/db has already been created. Once > a table/db is deleted, all these relationship attributes will be deleted as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3197) Add QueryText for hive_table and hive_db
[ https://issues.apache.org/jira/browse/ATLAS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3197: - Description: This patch introduced a model called Hive_table_ddl and hive_db_ddl which are used to track commands that are executed either on a table entity or bd entity. DDL entities will be added to a table/db entity through relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when a new command is executed, a new ddl entity will be created, it will append to the existing ddlQueries field if a table/db has already been created. Once a table/db is deleted, all these relationship attributes will be deleted as well. (was: This patch introduced a model called Hive_table_ddl and hive_db_ddl which are used to track commands that are executed either on a table entity or bd entity. DDL entities will be added to a table/db entity through relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when a new command is executed, a new ddl entity will be created, it will append to the existing DDLQueries field if a table/db has already been created. Once a table/db is deleted, all these relationship attribute will be deleted as well.) > Add QueryText for hive_table and hive_db > > > Key: ATLAS-3197 > URL: https://issues.apache.org/jira/browse/ATLAS-3197 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > Attachments: ATLAS-3197.patch > > > This patch introduced a model called Hive_table_ddl and hive_db_ddl which are > used to track commands that are executed either on a table entity or bd > entity. DDL entities will be added to a table/db entity through > relationshipAttribute call HIVE_DB_TO_DDL and hive_tb_to_ddl. Every time when > a new command is executed, a new ddl entity will be created, it will append > to the existing ddlQueries field if a table/db has already been created. Once > a table/db is deleted, all these relationship attributes will be deleted as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-3197) Add QueryText for hive_table and hive_db
[ https://issues.apache.org/jira/browse/ATLAS-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Le Ma updated ATLAS-3197: - Attachment: (was: ATLAS-3197.patch) > Add QueryText for hive_table and hive_db > > > Key: ATLAS-3197 > URL: https://issues.apache.org/jira/browse/ATLAS-3197 > Project: Atlas > Issue Type: New Feature >Reporter: Le Ma >Assignee: Le Ma >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
