[jira] [Updated] (ATLAS-3867) Relationship search API should have a provision to fetch custom attributes in search results

2020-07-02 Thread Pinal (Jira)


 [ 
https://issues.apache.org/jira/browse/ATLAS-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pinal updated ATLAS-3867:
-
Fix Version/s: 2.1.0

> Relationship search API should have a provision to fetch custom attributes in 
> search results
> 
>
> Key: ATLAS-3867
> URL: https://issues.apache.org/jira/browse/ATLAS-3867
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: Relationships
> Fix For: 2.1.0, 3.0.0
>
>
> {code:java}
> /v2/search/relationship?guid=ac9e04cc-f927-4334-af08-c83bc3733f5b=__hive_table.columns=name=ASCENDING
> {code}
> The response of the  above API contains below attributes only:
> {code:java}
> "attributes": {
> "owner": "hive",
> "qualifiedName": "ho.us_customers.age@cm",
> "name": "age"
>   },{code}
>  Is it possible to fetch a custom attribute "*dcProfiledData*" present in 
> Technical properties of the entity detailed page.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (ATLAS-3869) Upgrade httpclient from 4.5.3 to 4.5.4

2020-07-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ATLAS-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150309#comment-17150309
 ] 

ASF subversion and git services commented on ATLAS-3869:


Commit 1518c04f07e46a829bed4d2dce948b4df87a93c9 in atlas's branch 
refs/heads/branch-2.0 from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1518c04 ]

ATLAS-3869 Upgrade httpclient from 4.5.3 to 4.5.4

Signed-off-by: nixonrodrigues 
(cherry picked from commit 337575c81b993e2cdcd6dc462dcf614940c783c2)


> Upgrade httpclient from 4.5.3 to 4.5.4
> --
>
> Key: ATLAS-3869
> URL: https://issues.apache.org/jira/browse/ATLAS-3869
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-3869-Upgrade-httpclient-from-4.5.3-to-4.5.4.patch
>
>
> Found below exception where data was not getting added in SOLR from 
> janusgraph.
>  
> {noformat}
> Caused by: java.lang.ClassCastException: [B cannot be cast to java.lang.String
>   at 
> org.apache.http.conn.ssl.DefaultHostnameVerifier.getSubjectAltNames(DefaultHostnameVerifier.java:309)
>   at 
> org.apache.http.conn.ssl.DefaultHostnameVerifier.verify(DefaultHostnameVerifier.java:112)
>   at 
> org.apache.http.conn.ssl.DefaultHostnameVerifier.verify(DefaultHostnameVerifier.java:99)
>   at 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:463)
>   at 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:397)
>   at 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:355)
>   at 
> org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
>   at 
> org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:359)
>   at 
> org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381)
>   at 
> org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)
>   at 
> org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
>   at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
>   at 
> org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)
>   at 
> org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
>   at 
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
>   at 
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
>   at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:526)
>   at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:253)
>   at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:242)
>   at 
> org.apache.solr.client.solrj.impl.LBHttpSolrClient.doRequest(LBHttpSolrClient.java:483)
>   ... 7 more
> 2020-06-29 07:31:25,893 WARN  - [SIGTERM handler:] ~ Unable to close 
> transaction standardjanusgraphtx[0x18d7a16a] (StandardJanusGraph:230)
> java.lang.IllegalArgumentException: The transaction has already been closed
>   at 
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:142)
>   at 
> org.janusgraph.graphdb.transaction.StandardJanusGraphTx.rollback(StandardJanusGraphTx.java:1401)
>   at 
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsTransaction$1.doRollback(JanusGraphBlueprintsTransaction.java:190)
>   at 
> org.apache.tinkerpop.gremlin.structure.util.AbstractTransaction.rollback(AbstractTransaction.java:114)
>   at 
> org.apache.tinkerpop.gremlin.structure.Transaction$CLOSE_BEHAVIOR$2.accept(Transaction.java:182)
>   at 
> org.apache.tinkerpop.gremlin.structure.Transaction$CLOSE_BEHAVIOR$2.accept(Transaction.java:179)
>   at 
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsGraph$GraphTransaction.close(JanusGraphBlueprintsGraph.java:327)
>   at 
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsTransaction$1.doClose(JanusGraphBlueprintsTransaction.java:205)
>   at 
> org.apache.tinkerpop.gremlin.structure.util.AbstractTransaction.close(AbstractTransaction.java:139)
>   at 
> org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsTransaction.close(JanusGraphBlueprintsTransaction.java:215)
>   at 
> org.janusgraph.graphdb.database.StandardJanusGraph.closeInternal(StandardJanusGraph.java:226)
>   at 
> org.janusgraph.graphdb.database.StandardJanusGraph.access$500(StandardJanusGraph.java:91)

[jira] [Commented] (ATLAS-3871) Add unit tests to path extractor utility for s3, s3 v2, adls path entities

2020-07-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ATLAS-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150308#comment-17150308
 ] 

ASF subversion and git services commented on ATLAS-3871:


Commit 845017b1a07af0a2682d0baff660b65cc637f963 in atlas's branch 
refs/heads/branch-2.0 from Nikhil Bonte
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=845017b ]

ATLAS-3871 Add unit tests to path extractor utility for s3, s3 v2, adls path 
entities

Signed-off-by: nixonrodrigues 
(cherry picked from commit e72aa1076a5a1272935fed4dedaf9e29e41fa30b)


> Add unit tests to path extractor utility for s3, s3 v2, adls path entities
> --
>
> Key: ATLAS-3871
> URL: https://issues.apache.org/jira/browse/ATLAS-3871
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 2.0.0
>Reporter: Nikhil Bonte
>Assignee: Nikhil Bonte
>Priority: Major
>
> AtlasPathExtractorUtilTest added in ATLAS-3836 which covers unit tests for 
> ozone & hdfs path entites.
>  
> This Jira will improve AtlasPathExtractorUtilTest.java to cover s3, s3v2 & 
> adls path entities.
> Would add more tests for ozone as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (ATLAS-3867) Relationship search API should have a provision to fetch custom attributes in search results

2020-07-02 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/ATLAS-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150307#comment-17150307
 ] 

ASF subversion and git services commented on ATLAS-3867:


Commit 1ec50fb6fe8f966b7ca5fe2c793aca6995508a36 in atlas's branch 
refs/heads/branch-2.0 from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1ec50fb ]

ATLAS-3867 : Relationship search API should have a provision to fetch custom 
attributes in search results

Signed-off-by: nixonrodrigues 
(cherry picked from commit f932e52c687479c77b9967165353b0fffa6f2fa0)


> Relationship search API should have a provision to fetch custom attributes in 
> search results
> 
>
> Key: ATLAS-3867
> URL: https://issues.apache.org/jira/browse/ATLAS-3867
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-intg
>Affects Versions: 2.0.0
>Reporter: Pinal
>Assignee: Pinal
>Priority: Major
>  Labels: Relationships
> Fix For: 3.0.0
>
>
> {code:java}
> /v2/search/relationship?guid=ac9e04cc-f927-4334-af08-c83bc3733f5b=__hive_table.columns=name=ASCENDING
> {code}
> The response of the  above API contains below attributes only:
> {code:java}
> "attributes": {
> "owner": "hive",
> "qualifiedName": "ho.us_customers.age@cm",
> "name": "age"
>   },{code}
>  Is it possible to fetch a custom attribute "*dcProfiledData*" present in 
> Technical properties of the entity detailed page.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)