date:20170919

Build failed in Jenkins: Atlas-master-UnitTests #88

2017-09-19 Thread Apache Jenkins Server

See 


Changes:

[madhan] ATLAS-2121: basic-search update to use case-sensitive filter for

--
[...truncated 261.61 KB...]
Running org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest
Running org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateV1Test
Running org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStoreTest
Running 
org.apache.atlas.repository.store.graph.v1.AtlasRelationshipStoreSoftDeleteV1Test
Running org.apache.atlas.repository.store.graph.v1.AtlasDeleteHandlerV1Test
Running org.apache.atlas.query.LexerTest
Running org.apache.atlas.RepositoryServiceLoadingTest
Running org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1Test
Running 
org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1BulkImportPercentTest
Running org.apache.atlas.repository.store.graph.v1.HardDeleteHandlerV1Test
Running 
org.apache.atlas.repository.store.graph.v1.AtlasRelationshipStoreHardDeleteV1Test
Running org.apache.atlas.query.BaseGremlinTest
Running 
org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateHardDeleteV1Test
Running 
org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateSoftDeleteV1Test
Running org.apache.atlas.repository.audit.InMemoryAuditRepositoryTest
Running org.apache.atlas.query.QueryProcessorTest
Running org.apache.atlas.BaseRepositoryTest
Running org.apache.atlas.repository.typestore.StoreBackedTypeCacheTest
Running org.apache.atlas.query.GremlinTest
Running org.apache.atlas.query.ExpressionTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.596 sec - in 
org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryHATest
Running org.apache.atlas.repository.store.graph.v1.AtlasEntityDefStoreV1Test
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.823 sec - in 
org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateV1Test
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.569 sec - in 
org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1BulkImportPercentTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 36.309 sec - in 
org.apache.atlas.util.CompiledQueryCacheKeyTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 35.364 sec - in 
org.apache.atlas.BaseRepositoryTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 36.412 sec - in 
org.apache.atlas.TestModules
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 36.16 sec - in 
org.apache.atlas.utils.ObjectUpdateSynchronizerTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 36.693 sec - in 
org.apache.atlas.TestUtils
Running org.apache.atlas.repository.BaseTest
Running org.apache.atlas.repository.store.graph.v1.SoftDeleteHandlerV1Test
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 36.661 sec - in 
org.apache.atlas.query.LexerTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 36.298 sec - in 
org.apache.atlas.repository.audit.InMemoryAuditRepositoryTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 37.336 sec - in 
org.apache.atlas.repository.store.graph.v1.AtlasRelationshipStoreV1Test
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 36.667 sec - in 
org.apache.atlas.query.BaseGremlinTest
Running org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 37.278 sec - in 
org.apache.atlas.repository.store.graph.v1.AtlasDeleteHandlerV1Test
Running org.apache.atlas.repository.userprofile.UserProfileServiceTest
Running org.apache.atlas.repository.graph.GraphBackedRepositorySoftDeleteTest
Running org.apache.atlas.repository.graph.GraphBackedSearchIndexerMockTest
Running org.apache.atlas.repository.graph.Gremlin3QueryOptimizerTest
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 36.876 sec - 
in org.apache.atlas.query.ExpressionTest
Running org.apache.atlas.repository.graph.Gremlin2QueryOptimizerTest
Running org.apache.atlas.repository.graph.TestIntSequence
Running org.apache.atlas.repository.graph.GraphBackedRepositoryHardDeleteTest
Running org.apache.atlas.repository.graph.GraphBackedMetadataRepositoryTest
Running org.apache.atlas.repository.graph.GraphHelperTest
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 39.021 sec - 
in org.apache.atlas.query.ParserTest
Running org.apache.atlas.repository.graph.ReverseReferenceUpdateSoftDeleteTest
Running org.apache.atlas.repository.graph.ReverseReferenceUpdateHardDeleteTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 42.895 sec - in 
org.apache.atlas.RepositoryServiceLoadingTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 42.489 sec - in 
org.apache.atlas.query.QueryProcessorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 43.795 sec - in 
org.apache.atla

[jira] [Updated] (ATLAS-2101) Remove use of Guava Stopwatch from Atlas

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-2101:

Fix Version/s: (was: trunk)
   0.8.2
   0.9-incubating

Committed to following branches:
 - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/7eff37a6
 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/7780b520

> Remove use of Guava Stopwatch from Atlas
> 
>
> Key: ATLAS-2101
> URL: https://issues.apache.org/jira/browse/ATLAS-2101
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Minor
> Fix For: 0.9-incubating, 0.8.2
>
> Attachments: StandardIDPool.java
>
>
> *Background*
> Using _IntelliJ_ attempt to start Atlas server. Chances are the startup will 
> fail due to error in resolving _com.google.common.base.StopWatch_.
> Similar problem is observed on some build environments.
> *Solution*
> * Add _StandardIDPool.java_ to shaded _Titan0_ JAR. 
> * Replace use of _Stopwatch_ with some alternative implementation.
> See also: [HBASE-14963|https://issues.apache.org/jira/browse/HBASE-14963]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Atlas issues about 0.9 release

2017-09-19 Thread Madhan Neethiraj

Junheng, Ismaël,


> 1. The Atlas version 0.9 is in development phase, I can see the version
> 0.9-SNAPSHOT published on your website and then where can I get the 0.9
> package?
0.9 version is still under development in the master branch. Only after it is 
released, 0.9 libraries will be available. The latest release version is 0.8.1, 
from branch-0.8. 

>   And when will the 0.9 formal release be published?
Next release from master branch is likely to be in February/March 2018. Before 
this release from master branch, there might be another release from branch-0.8.


> 2. I see the 0.9 version will support Spark Integration, NiFi Integration
> and so on in “cwiki” page, but in the 0.9-incubating issues page, I don’t
> see these features.
>
>   So will the 0.9 version support them?
NiFi integration – likely to be available in the next release from master. It 
is not clear whether Spark integration will make it though.

>Extra question, what are the goals of the Atlas 0.9 release (what will
>be the main points)?
- we plan to move to Hadoop-3,  HBase-2, JanusGraph; probably higher version of 
Solr & Kafka
- features: relationship as a first-class type, tag-propagation, HBase hook, 
search improvements, Open Metadata and Governance items

>We wrote an integration of Atlas that uses the v1 of the API, so we
 >   would also like to know if the v1 API will still be available for 0.9.
Yes. V1 API will be available; but new functionalities like relationships, 
tag-propagation will only be available via V2 APIs.


Apologies for the delayed response to your questions.

Regards,
Madhan

On 8/16/17, 3:17 AM, "Ismaël Mejía"  wrote:

Extra question, what are the goals of the Atlas 0.9 release (what will
be the main points)?

We wrote an integration of Atlas that uses the v1 of the API, so we
would also like to know if the v1 API will still be available for 0.9.

Regards,
Ismaël

On Thu, Aug 10, 2017 at 8:56 AM, Junheng Cui(崔俊珩)  
wrote:
> Dear Atlas development team，
>
>
>
> I am a SW engineer working at Inspur China. Now I am using Atlas for data
> government. But I hava some questions, may I ask you about that?
>
>
>
> 1. The Atlas version 0.9 is in development phase, I can see the version
> 0.9-SNAPSHOT published on your website and then where can I get the 0.9
> package?
>
>   And when will the 0.9 formal release be published?
>
>
>
> 2. I see the 0.9 version will support Spark Integration, NiFi Integration
> and so on in “cwiki” page, but in the 0.9-incubating issues page, I don’t
> see these features.
>
>   So will the 0.9 version support them?
>
>
>
> The Atlas is a very useful program for data government, it helps my 
company
> so much.
>
> Thanks a lot!
>
>
>
>
>
> Best regards,
>
> Junheng Cui
>
>
>
> 
>
> Software Development Engineer of R&D Center of INSPUR SOFTWARE Co., Ltd
>
> Address:1036 Langchao Road, Jinan, Shandong Province, China
>
>

Build failed in Jenkins: Atlas-0.8-UnitTests #68

2017-09-19 Thread Apache Jenkins Server

See 


Changes:

[madhan] ATLAS-2121: basic-search update to use case-sensitive filter for

--
[...truncated 451.70 KB...]
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 50 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

[INFO] Webapp assembled in [1303 msecs]
[INFO] Building war: 

[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ 
atlas-webapp ---
[INFO] 
[INFO] --- enunciate-maven-plugin:2.8.0:docs (default) @ atlas-webapp ---
[INFO] [ENUNCIATE] Skipping enunciate per configuration.
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-webapp ---
[WARNING] The parameter forkMode is deprecated since version 2.14. Use 
forkCount and reuseForks instead.
[INFO] Surefire report directory: 

[INFO] Using configured provider org.apache.maven.surefire.testng.TestNGProvider
[WARNING] file.encoding cannot be set as system property, use 
-Dfile.encoding=... instead

---
 T E S T S
---
Running org.apache.atlas.util.RestUtilsTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.312 sec - in 
org.apache.atlas.util.RestUtilsTest
Running org.apache.atlas.web.setup.SetupStepsTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.273 sec - in 
org.apache.atlas.web.setup.SetupStepsTest
Running org.apache.atlas.web.security.NegativeSSLAndKerberosTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 51.173 sec - in 
org.apache.atlas.web.security.NegativeSSLAndKerberosTest
Running org.apache.atlas.web.security.FileAuthenticationTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.68 sec - in 
org.apache.atlas.web.security.FileAuthenticationTest
Running org.apache.atlas.web.security.SSLAndKerberosTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 63.417 sec - in 
org.apache.atlas.web.security.SSLAndKerberosTest
Running org.apache.atlas.web.security.UserDaoTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.647 sec - in 
org.apache.atlas.web.security.UserDaoTest
Running org.apache.atlas.web.security.SSLTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 26.264 sec - in 
org.apache.atlas.web.security.SSLTest
Running org.apache.atlas.web.util.ServletsTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.678 sec - in 
org.apache.atlas.web.util.ServletsTest
Running org.apache.atlas.web.resources.AdminResourceTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.147 sec - in 
org.apache.atlas.web.resources.AdminResourceTest
Running org.apache.atlas.web.resources.TaxonomyServiceTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.039 sec - in 
org.apache.atlas.web.resources.TaxonomyServiceTest
Running org.apache.atlas.web.resources.EntityResourceTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.543 sec - in 
org.apache.atlas.web.resources.EntityResourceTest
Running org.apache.atlas.web.resources.AdminExportTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.246 sec - in 
org.apache.atlas.web.resources.AdminExportTe

Build failed in Jenkins: Atlas-0.8-IntegrationTests #70

2017-09-19 Thread Apache Jenkins Server

See 


Changes:

[madhan] ATLAS-2121: basic-search update to use case-sensitive filter for

--
[...truncated 537.26 KB...]
127.0.0.1 - - [20/Sep/2017:04:53:53 +] "GET 
/api/atlas/v2/types/classificationdef/name/blah HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:53 +] "GET 
/api/atlas/v2/types/classificationdef/guid/blah HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:53 +] "GET 
/api/atlas/v2/types/entitydef/name/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:53 +] "GET 
/api/atlas/v2/types/entitydef/guid/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:53 +] "POST /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:53 +] "GET 
/api/atlas/v2/types/typedefs/?supertype=AeAL2IC9Syn&type=CLASS HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:53 +] "GET 
/api/atlas/v2/types/typedefs/?notsupertype=BpJIlBeTm3Z&supertype=AeAL2IC9Syn&type=CLASS
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:53 +] "POST /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:53 +] "GET 
/api/atlas/discovery/search?query=from+hive_db_v1+name%3D%22dbw78NUU5KnO%22 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:54 +] "PUT /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:54 +] "GET 
/api/atlas/v2/types/typedefs/?type=ENTITY HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:54 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:54 +] "POST /api/atlas/types HTTP/1.1" 409 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:54 +] "GET /api/atlas/types/blah HTTP/1.1" 
404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:54 +] "GET 
/api/atlas/v2/types/typedef/name/class_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:54 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:55 +] "GET 
/api/atlas/v2/types/typedef/name/secure_trait HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:54 +] "GET 
/api/atlas/discovery/search/gremlin?query=g.V.has('type',+'hive_table_v1').toList()
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:55 +] "GET 
/api/atlas/v2/types/typedef/name/pii_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:55 +] "GET 
/api/atlas/v2/types/typedef/name/ssn_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:55 +] "POST /api/atlas/types HTTP/1.1" 409 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:55 +] "GET 
/api/atlas/v2/types/typedef/name/salary_trait HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:55 +] "GET 
/api/atlas/v2/types/typedef/name/ARwc4E1JyXy HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:55 +] "GET 
/api/atlas/v2/types/typedef/name/sox_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:56 +] "GET 
/api/atlas/v2/types/typedef/name/A1MGiVmkSYXz HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:56 +] "GET /api/atlas/types?type=TRAIT 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:56 +] "GET 
/api/atlas/v2/types/typedef/name/AaULjKCqP0j HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:56 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:56 +] "GET 
/api/atlas/v2/types/typedef/name/BKUk0rsBUNQ HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:56 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:56 +] "GET 
/api/atlas/v2/types/typedef/name/A1u3upCYo6Dj HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:53:56 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.

Build failed in Jenkins: Atlas-master-IntegrationTests #111

2017-09-19 Thread Apache Jenkins Server

See 


Changes:

[madhan] ATLAS-2121: basic-search update to use case-sensitive filter for

--
[...truncated 449.87 KB...]
127.0.0.1 - - [20/Sep/2017:04:43:23 +] "GET 
/api/atlas/v2/types/entitydef/name/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:23 +] "GET 
/api/atlas/v2/types/entitydef/guid/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:23 +] "POST /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:24 +] "GET 
/api/atlas/v2/types/typedefs/?supertype=AGxNaOLvHi3&type=CLASS HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:24 +] "GET 
/api/atlas/v2/types/typedefs/?notsupertype=Bwp4VKENcVO&supertype=AGxNaOLvHi3&type=CLASS
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:24 +] "POST /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:24 +] "PUT /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:25 +] "GET 
/api/atlas/v2/types/typedefs/?type=ENTITY HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:25 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:25 +] "POST /api/atlas/types HTTP/1.1" 409 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:25 +] "GET /api/atlas/types/blah HTTP/1.1" 
404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:25 +] "GET 
/api/atlas/v2/types/typedef/name/class_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:25 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:25 +] "GET 
/api/atlas/v2/types/typedef/name/secure_trait HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:25 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:25 +] "GET 
/api/atlas/v2/types/typedef/name/pii_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:25 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:25 +] "GET 
/api/atlas/v2/types/typedef/name/ssn_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:25 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:26 +] "GET 
/api/atlas/v2/types/typedef/name/salary_trait HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:26 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:26 +] "GET 
/api/atlas/v2/types/typedef/name/sox_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:26 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:26 +] "GET /api/atlas/types?type=TRAIT 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:26 +] "GET 
/api/atlas/v2/types/typedef/name/AiqUQ9nQqi6 HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:26 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:26 +] "GET 
/api/atlas/v2/types/typedef/name/A1QF5ohcvXXh HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:26 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:26 +] "GET 
/api/atlas/v2/types/typedef/name/BzUbXVvwRZP HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:26 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:27 +] "GET 
/api/atlas/v2/types/typedef/name/CWOfCO9KKpw HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:27 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:27 +] "GET 
/api/atlas/types?type=CLASS&supertype=AiqUQ9nQqi6¬supertype=BzUbXVvwRZP 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:27 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:27 +] "PUT /api/atlas/types HTTP/1.1" 200 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:04:43:28 +] "GET /api/atlas/types/khDUJ1iuG7 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
Tests run: 143, Failures: 16, Errors: 0, Skipped: 100, Time elapsed: 35.944 sec 
<<< FAILURE! - in TestSuite
setUp(org.apache.atlas.web.integration.EntityDiscoveryJerseyResourceIT)  Time 
elapsed: 5.072 sec  <<< FAILURE!
org.apache.atlas.AtlasServiceException: Metadata service API 
org.apache.atlas.AtlasBaseClient$APIInfo@5f9da73c failed with status 400 (Bad 
Request) Response Body ({"error":"Unknown datatype: hive_db"})
at 
org.apache.atlas.web.inte

[jira] [Updated] (ATLAS-2121) Inconsistency in basic search results due to case sensitivity of type names

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-2121:

Issue Type: Sub-task  (was: Bug)
Parent: ATLAS-1822

> Inconsistency in basic search results due to case sensitivity of type names
> ---
>
> Key: ATLAS-2121
> URL: https://issues.apache.org/jira/browse/ATLAS-2121
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.2
>
>
> Type names are case sensitive hence 2 types can be created with different 
> cases. 
> Example :
> 1. type1 with attributes a , b
> 2. TYPE1 with attributes c , d
> The types creation succeeds and 
> {code}
> /api/atlas/v2/types/entitydef/name/type1
> /api/atlas/v2/types/entitydef/name/TYPE1
> {code}
> return the corresponding type definitions correctly.
> When an entity e1 of type1 is created, 
> and when a BASIC search is fired with
>  typeName= type1 , e1 is returned and
>  typeName=TYPE1 also , e1 is returned.
> But in the case of DSL search , 
> typeName = type1 returns e1
> typeName = TYPE1 doesn't return any result - which is the correct behavior.
> This issue is major from tag side too because , UI Tag search is Basic and 
> returns entity tagged with tag1 when searched for tag1 or TAG1.
> Whereas DSL search with
> classification=tag1 returns entity
> classification=TAG1 does not return any entity. - which is the correct 
> behavior.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2028) Basic query with entity and tag filters : Invalid filter keys for type and tags attributes are ignored and fetches all entities of the type / associated to the tag

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-2028:

Issue Type: Sub-task  (was: Bug)
Parent: ATLAS-1822

> Basic query with entity and tag filters : Invalid filter keys for type and 
> tags attributes are ignored and fetches all entities of the type / associated 
> to the tag
> ---
>
> Key: ATLAS-2028
> URL: https://issues.apache.org/jira/browse/ATLAS-2028
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
> Attachments: 
> 0001-ATLAS-2028-Invalid-attributes-in-Basic-search-reques.patch
>
>
> Basic search request with POST body fired using curl:
> {code}
> {
>   
> "entityFilters":{"condition":"AND","criterion":[{"attributeName":"invalid_attr","operator":"=","attributeValue":"userdir"}]},
>   "tagFilters":null,
>   "attributes":null,
>   "query":null,
>   "excludeDeletedEntities":true,
>   "limit":25,
>   "typeName":"hdfs_path",
>   "classification":null
> }
> {code}
> All the hdfs_path entities are fetched because invalid filter keys are 
> ignored :
> {code}
> Converted query string with 2 replacements: [v."__typeName":(hdfs_path) AND 
> v."__state":ACTIVE] => [iyt_t:(hdfs_path) AND b2d_t:ACTIVE] 
> (IndexSerializer:648)
> {code}
> Same happens with invalid tag attribute filters also.
> This gives a delusion that all returned hdfs_path entities are satisfied by 
> the filter condition.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2091) Search using entity and trait attributes - "#" in string attribute filter doesn't fetch results

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-2091:

Issue Type: Sub-task  (was: Bug)
Parent: ATLAS-1822

> Search using entity and trait attributes - "#" in string attribute filter 
> doesn't fetch results
> ---
>
> Key: ATLAS-2091
> URL: https://issues.apache.org/jira/browse/ATLAS-2091
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
> Attachments: 
> 0001-ATLAS-2091-Attribute-values-containing-Tokenizer-cha.patch
>
>
> 1. Created an hdfs_path entity with owner name = "user#3"
> 2. Fired basic search with type name = hdfs_path and filter - owner = user#3. 
> hdfs_path entity was returned.
> 3. Fired basic search with type name = hdfs_path and filter - owner contains 
> user#3. No entity is returned.
> Other than "=" , operators like != , contains , ends_with , begins_with are 
> not fetching expected results due to # in search filter key.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2118) Basic search - Contains clause issues

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-2118:

Issue Type: Sub-task  (was: Bug)
Parent: ATLAS-1822

> Basic search - Contains clause issues
> -
>
> Key: ATLAS-2118
> URL: https://issues.apache.org/jira/browse/ATLAS-2118
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.8-incubating, 0.9-incubating, 0.8.1-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
> Fix For: 0.8-incubating, 0.9-incubating, 0.8.1-incubating
>
> Attachments: 
> 0001-ATLAS-2118-Issues-with-contains-in-Basic-search.patch
>
>
> If the contains clause attribute value contains any of the special regex 
> chars like 
> "+", "|", "(", "{", "[", "*", "?", "$", "/", "^"
> then the graph query fails with Invalid pattern exception
> Solution: Escape all occurrences of the special characters 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2117) Basic search issues due to Titan Solr schema

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-2117:

Issue Type: Sub-task  (was: Bug)
Parent: ATLAS-1822

> Basic search issues due to Titan Solr schema
> 
>
> Key: ATLAS-2117
> URL: https://issues.apache.org/jira/browse/ATLAS-2117
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.8-incubating, 0.9-incubating, 0.8.1-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
> Fix For: 0.8-incubating, 0.9-incubating, 0.8.1-incubating
>
> Attachments: 
> 0001-ATLAS-2117-Work-around-for-basic-search-due-to-Titan.patch
>
>
> When using Solr as indexing backend, the tokenization of the string is 
> performed using the StandardTokenizerFactory which treats punctuations and 
> special characters as delimiters which results in the more indexed terms 
> being associated with the associated vertex (document)
> Also there's a LowercaseFilterFactory which makes lookup case insensitive.
> This schema design doesn't work well for the current basic search enhancement 
> (ATLAS-1880) causing a lot of false positives/negatives when querying the 
> index.
> The workaround/hack for this is to do an in-memory filtering when such schema 
> violations are found or push the entire attribute query down to the graph 
> which might be in-efficient and memory intensive. (Current JIRA will track 
> this)
> Correct solution would be to re-index the existing data with a schema change 
> and not use the mentioned code workarounds for better performance of the 
> search. (Should be taken up in separate JIRA)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2115) Regression: Basic search performance

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-2115:

Issue Type: Sub-task  (was: Bug)
Parent: ATLAS-1822

> Regression: Basic search performance
> 
>
> Key: ATLAS-2115
> URL: https://issues.apache.org/jira/browse/ATLAS-2115
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.8-incubating, 0.8.1-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
> Fix For: 0.9-incubating, 0.8.2
>
>
> When searching using a tag without any attributes the call timings were 
> doubled (worst case tripled) regardless of the offset and limit. This patch 
> introduces a new code path which allows faster retrieval of vertices for the 
> mentioned scenario. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2082) Regression: Search fails when filter contains a boolean attribute and a string attribute with special characters

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-2082:

Issue Type: Sub-task  (was: Bug)
Parent: ATLAS-1822

> Regression: Search fails when filter contains a boolean attribute and a 
> string attribute with special characters
> 
>
> Key: ATLAS-2082
> URL: https://issues.apache.org/jira/browse/ATLAS-2082
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Affects Versions: 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2082.patch, BooleanAndCapsStringSearch.txt
>
>
> When a search is applied with 2 filters : boolean and string and if string 
> filter has capitalized characters, Atlas throws 500 Internal server error.
> Example POST body request :
> {code}
> {  
>"entityFilters":{  
>   "condition":"AND",
>   "criterion":[  
>  {  
> "attributeName":"isFile",
> "operator":"=",
> "attributeValue":"true"
>  },
>  {  
> "attributeName":"owner",
> "operator":"=",
> "attributeValue":"Hrt_qa"
>  }
>   ]
>},
>"tagFilters":null,
>"attributes":[  
>   "isFile"
>],
>"query":null,
>"excludeDeletedEntities":true,
>"limit":25,
>"typeName":"hdfs_path",
>"classification":null
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2061) Regression : Entity,Tag filter fetches empty results when applied on an enum attribute.

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-2061:

Issue Type: Sub-task  (was: Bug)
Parent: ATLAS-1822

> Regression : Entity,Tag filter fetches empty results when applied on an enum 
> attribute.
> ---
>
> Key: ATLAS-2061
> URL: https://issues.apache.org/jira/browse/ATLAS-2061
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Blocker
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: 
> 0001-ATLAS-2061-Entity-Tag-filter-fetches-empty-results-w.patch
>
>
> 1.Created a tag with an attribute fileAction of type file_action.
> 2.Associated the tag to an entity with fileAction value "EXECUTE"
> 3.Fired a basic query with classification =  and tag filter : 
> fileAction = EXECUTE.  The entity was not fetched.
> No results are fetched with "!=" operator too on values other than EXECUTE 
> like WRITE , READ etc.,
> Hence , enum filtering is not fetching results. 
> This is a regression , as few commits back,  enum filtering was working as 
> expected.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2022) Regression : Empty results fetched from GET Basic search query

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-2022:

Issue Type: Sub-task  (was: Bug)
Parent: ATLAS-1822

> Regression : Empty results fetched from GET Basic search query
> --
>
> Key: ATLAS-2022
> URL: https://issues.apache.org/jira/browse/ATLAS-2022
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Sharmadha Sainath
>Priority: Blocker
> Fix For: trunk, 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2022.patch
>
>
> Basic search query fired as a POST request with attribute , tag filters 
> fetches correct results.
> But Basic query fired as a GET request with query params encoded in the URL , 
> returns empty results.
> For example : Basic query : typeName = "hive_table" query =  hive_table in Atlas"
> http://localhost:21000/api/atlas/v2/search/basic?typeName=hive_table&query=employee
> returns 
> {code}
> {
> queryType: "BASIC",
> searchParameters: {
> query: "employee",
> typeName: "hive_table",
> excludeDeletedEntities: false,
> limit: 0,
> offset: 0
> },
> queryText: "employee"
> }
> {code}
> Few commits back , following was the response :
> {code}
> {
> queryType: "BASIC",
> type: "hive_table",
> entities: [
> {
> typeName: "hive_table",
> attributes: {
> owner: "admin",
> qualifiedName: "default.employee@cl1",
> name: "employee",
> description: null
> },
> guid: "253aa208-0415-4e86-8611-3858fad78ede",
> status: "ACTIVE",
> displayText: "employee",
> classificationNames: [ ]
> }
> ]
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2025) Basic query with entity and tag filters : Providing invalid tag name for classification returns all entities matching typename/query

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-2025:

Issue Type: Sub-task  (was: Bug)
Parent: ATLAS-1822

> Basic query with entity and tag filters : Providing invalid tag name for 
> classification returns all entities matching typename/query
> 
>
> Key: ATLAS-2025
> URL: https://issues.apache.org/jira/browse/ATLAS-2025
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: 
> 0002-ATLAS-2025-Validation-of-classification-type-in-basi.patch
>
>
> Fired a basic query with following POST request body with Non Existing tag 
> using curl (because UI only lets user select from existing tags):
> {code}
> {
> "entityFilters":null,
> "tagFilters":null,
> "attributes":null,
> "query":null,
> "excludeDeletedEntities":true,
> "limit":25,
> "typeName":"kafka_topic",
> "classification":"non_existing_tag"
> }
> {code}
> GET Basic search request with classification parameter also lists all the 
> kakfa_topic entities:
> {code}
> http://localhost:21000/api/atlas/v2/search/basic?typeName=kafka_topic&classification=non_existing_tag&limit=50
> {code}
> Expected 40X Response code saying that tag doesn't exist. But the response 
> listed all the kafka_topic entities. This gives an delusion that all returned 
> kafka_topic entities are tagged with 'non_existing_tag'



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2008) basic-search: numeric tag-attribute filtering fails with java.lang.ClassCastException

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-2008:

Issue Type: Sub-task  (was: Bug)
Parent: ATLAS-1822

> basic-search: numeric tag-attribute filtering fails with 
> java.lang.ClassCastException
> -
>
> Key: ATLAS-2008
> URL: https://issues.apache.org/jira/browse/ATLAS-2008
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2008.patch
>
>
> When tag-attribute filter includes attributes of numeric types (int, double, 
> float), Gremlin queries fail due to ClassCastException:
> {noformat}
> 2017-07-29 07:58:15,868 DEBUG - [pool-1-thread-9 - 
> e81686ab-44b5-403a-94e2-cf2a342806c6:] ~ 
> gremlinTagFilterQuery=g.V().has('__guid', T.in, guids).has('__traitNames', 
> T.in, traitNames).as('e').out().has('__typeName', T.in, 
> typeNames).has('tag4.attr4-double', T.gte, 6).back('e').toList() 
> (ClassificationSearchProcessor:119)
> ...
> 2017-07-29 07:58:16,189 WARN  - [pool-1-thread-9 - 
> e81686ab-44b5-403a-94e2-cf2a342806c6:] ~ javax.script.ScriptException: 
> java.lang.ClassCastException: java.lang.Integer cannot be cast to 
> java.lang.Double (ClassificationSearchProcessor:260)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (ATLAS-2121) Inconsistency in basic search results due to case sensitivity of type names

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj resolved ATLAS-2121.
-
   Resolution: Fixed
Fix Version/s: 0.8.2
   0.9-incubating

Committed to the following branches:
 - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/c0f0abc1
 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/5645c9e7

> Inconsistency in basic search results due to case sensitivity of type names
> ---
>
> Key: ATLAS-2121
> URL: https://issues.apache.org/jira/browse/ATLAS-2121
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: 0.9-incubating, 0.8.2
>
>
> Type names are case sensitive hence 2 types can be created with different 
> cases. 
> Example :
> 1. type1 with attributes a , b
> 2. TYPE1 with attributes c , d
> The types creation succeeds and 
> {code}
> /api/atlas/v2/types/entitydef/name/type1
> /api/atlas/v2/types/entitydef/name/TYPE1
> {code}
> return the corresponding type definitions correctly.
> When an entity e1 of type1 is created, 
> and when a BASIC search is fired with
>  typeName= type1 , e1 is returned and
>  typeName=TYPE1 also , e1 is returned.
> But in the case of DSL search , 
> typeName = type1 returns e1
> typeName = TYPE1 doesn't return any result - which is the correct behavior.
> This issue is major from tag side too because , UI Tag search is Basic and 
> returns entity tagged with tag1 when searched for tag1 or TAG1.
> Whereas DSL search with
> classification=tag1 returns entity
> classification=TAG1 does not return any entity. - which is the correct 
> behavior.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1994) Search API: Work with Tag attributes when query and entity filters are specified

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-1994:

Issue Type: Sub-task  (was: Improvement)
Parent: ATLAS-1822

> Search API: Work with Tag attributes when query and entity filters are 
> specified
> 
>
> Key: ATLAS-1994
> URL: https://issues.apache.org/jira/browse/ATLAS-1994
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>
> Currently when the entity text query is specified with the entity and it's 
> filters none of the tag attributes are considered during filtering (search). 
> This change honors the tag attributes during search even under the above 
> scenario



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1961) Basic search improvement in use of Solr index for attribute filtering

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-1961:

Issue Type: Sub-task  (was: Improvement)
Parent: ATLAS-1822

> Basic search improvement in use of Solr index for attribute filtering
> -
>
> Key: ATLAS-1961
> URL: https://issues.apache.org/jira/browse/ATLAS-1961
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1961.patch
>
>
> Current basic search implementation uses Solr only when both type and 
> attribute filters can be done via Solr. When the type specified has too many 
> subtypes, Solr is not used - even though Solr could be used for attribute 
> filtering. Use of Solr for attribute filtering can be help quicker response.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 62416: ATLAS-2121: Case sensitivity for tag/type name search with index

2017-09-19 Thread Madhan Neethiraj


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62416/#review185770
---


Ship it!




Ship It!

- Madhan Neethiraj


On Sept. 19, 2017, 7:15 p.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62416/
> ---
> 
> (Updated Sept. 19, 2017, 7:15 p.m.)
> 
> 
> Review request for atlas and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2121
> https://issues.apache.org/jira/browse/ATLAS-2121
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Currently the index query returns case insensitive results, this patch add 
> the typename / tag name check to the in memory predicate to honor case 
> sensitivity.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/discovery/ClassificationSearchProcessor.java
>  1d4815df 
>   
> repository/src/main/java/org/apache/atlas/discovery/EntitySearchProcessor.java
>  970cd28e 
> 
> 
> Diff: https://reviews.apache.org/r/62416/diff/2/
> 
> 
> Testing
> ---
> 
> UI and REST calls work as expected.
> 
> 
> Thanks,
> 
> Apoorv Naik
> 
>

[jira] [Assigned] (ATLAS-1822) Search Query Builder and Faceted Search in Atlas

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj reassigned ATLAS-1822:
---

Assignee: Madhan Neethiraj

> Search Query Builder and Faceted Search in Atlas
> 
>
> Key: ATLAS-1822
> URL: https://issues.apache.org/jira/browse/ATLAS-1822
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-webui
>Reporter: Srikanth Venkat
>Assignee: Madhan Neethiraj
>
> Current search experience in Atlas UI is pretty basic and any advanced 
> searches require knowledge of DSL that might be difficult for business users.
> As a data steward or data consumer, I need an easy and intuitive way to 
> perform faceted searches on entities, classifications, relationships, and 
> business glossaries and filter the results based on a combination of 
> parameters so I can navigate and locate assets for curation and in order to 
> take any governance actions. I also need to be able to save my searches and 
> filters and rerun them dynamically against the latest state of the enterprise 
> metadata catalog in Atlas.
> Implementation considerations:
> # For business users, there should be default filters provided based on 
> commonly used criteria in the search experience
> # Any search results should only show metadata of data assets that user has 
> permission to view, based upon authorization policies (via Ranger)
> # Search facets need to be based on search conditions and should allow for 
> sequence of AND, OR and NOT operations with multiple search conditions
> # Search facets details (should allow for combinations of any or all of the 
> following):
> * Asset type (entity types)
> * Attribute value checker (should allow for combinations of range checks, 
> ordinality, exact match, numeric, string and date comparisons, single or 
> muliple values, category checks, nulls)
> * Created time
> * Updated time
> * Size (where relevant for e.g. HDFS files)
> * Deleted/Active status
> * Owner
> * Custom property values
> * File format
> * Asset name
> * Physical storage context: Datalake/cluster or datacenter holding the asset
> * Classification
> * Glossary/taxonomy association
> Note:
> # Searches should be able to be saved and scoped to a particular business 
> catalog or asset type or namespace (when multi-tenancy is supported by Atlas 
> in the future) 
> # Once search results are available, user should be able to filter by any of 
> the facets.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2100) Support for Saving Searches

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-2100:

Issue Type: Sub-task  (was: Improvement)
Parent: ATLAS-1822

> Support for Saving Searches
> ---
>
> Key: ATLAS-2100
> URL: https://issues.apache.org/jira/browse/ATLAS-2100
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
> Fix For: trunk
>
> Attachments: ATLAS-2100-SavedSearch-EntityBased.patch
>
>
> *Background*
> The current set of features around search allows user to construct complex 
> queries. These queries once constructed, cannot be persisted and re-used 
> later. The user will have to reconstruct these if they were to run them again.
> *Solution*
> The ability to save constructed queries and retrieve them later will benefit 
> the user.
> *Implementation*
> A logged in user should be able to:
> *  Save the constructed query.
> *  View all the queries constructed.  
> *  Edit already constructed query.
> *  Execute already constructed query.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2148) Saved Search: Introduce BASIC and ADVANCE Search Types During Save

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj updated ATLAS-2148:

Issue Type: Sub-task  (was: Improvement)
Parent: ATLAS-1822

> Saved Search: Introduce BASIC and ADVANCE Search Types During Save
> --
>
> Key: ATLAS-2148
> URL: https://issues.apache.org/jira/browse/ATLAS-2148
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core, atlas-webui
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Minor
> Fix For: 0.9-incubating, 0.8.2
>
> Attachments: ATLAS-2148-QueryType.patch
>
>
> *Background*
> Existing implementation of _SavedSearch_ does not have a way to differentiate 
> saving of basic and advanced searches.
> Basic searches are the ones where user constructs the query using the new 
> search UI.
> Advanced queries are where the user types a DSL query into the search box.
> Having this notion should allow for better differentiation of the 2 types of 
> queries. If the type is used in specifying unique attribute, user could 
> create query with same name.
> *Implementation*
> Additional attribute added to ___AtlasSavedSearch_. REST API updated to 
> include the query type parameter.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (ATLAS-1991) Unique attributes are not shown in AtlasObjectId.

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj resolved ATLAS-1991.
-
Resolution: Invalid

Unique-attributes can be set on an AtlasObjectId instance with the following 
method:
{code}
public void setUniqueAttributes(Map uniqueAttributes)
{code}


> Unique attributes are not shown in AtlasObjectId.
> -
>
> Key: ATLAS-1991
> URL: https://issues.apache.org/jira/browse/ATLAS-1991
> Project: Atlas
>  Issue Type: Bug
>Reporter: David Radley
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Jenkins build is back to normal : Atlas-0.8-UnitTests #67

2017-09-19 Thread Apache Jenkins Server

See

Build failed in Jenkins: Atlas-0.8-IntegrationTests #69

2017-09-19 Thread Apache Jenkins Server

See 


Changes:

[madhan] ATLAS-2148: saved-search API enhancement to support searchType

--
[...truncated 497.25 KB...]
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "GET 
/api/atlas/v2/types/typedef/name/sec HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "GET 
/api/atlas/v2/types/typedef/name/finance HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "GET 
/api/atlas/v2/types/typedef/name/FactX5PppOnPRw HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "GET 
/api/atlas/v2/types/typedef/name/ETLyDvJji6wb2 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "GET 
/api/atlas/v2/types/typedef/name/DimensioncX5LVhuxq2 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "GET 
/api/atlas/v2/types/typedef/name/MetricitjTGXoaCr HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "GET 
/api/atlas/v2/types/typedef/name/hive_db_v1 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "GET 
/api/atlas/v2/types/typedef/name/hive_column_v1 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "GET 
/api/atlas/v2/types/typedef/name/hive_table_v1 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "GET 
/api/atlas/v2/types/typedef/name/hive_process_v1 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:31 +] "GET 
/api/atlas/lineage/hive/table/sales_fact_monthly_mvkJ93HlLDIs/inputs/graph 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:33 +] "GET 
/api/atlas/entities?type=hive_table_v1&property=qualifiedName&value=sales_facts6W3c14CMa
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:33 +] "GET 
/api/atlas/lineage/e65e3919-ad5b-45fa-b034-6d21f68c07e8/outputs/graph HTTP/1.1" 
200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:35 +] "GET 
/api/atlas/entities?type=hive_table_v1&property=qualifiedName&value=sales_facteAA1uTPSbn
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:35 +] "GET 
/api/atlas/v2/lineage/6d752bec-2670-4afd-b7f4-c47a0acca849?direction=OUTPUT&depth=5
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:36 +] "GET 
/api/atlas/lineage/hive/table/blah/schema HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:36 +] "GET 
/api/atlas/entities?type=hive_table_v1&property=qualifiedName&value=sales_fact_monthly_mvkJ93HlLDIs
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:36 +] "GET 
/api/atlas/lineage/148d41d7-6306-404c-ba2b-eb9f2f8bcfdc/inputs/graph HTTP/1.1" 
200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:37 +] "GET 
/api/atlas/lineage/hive/table/sales_facts6W3c14CMa/outputs/graph HTTP/1.1" 200 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:39 +] "GET 
/api/atlas/lineage/hive/table/SalescoOnWkSYxs/schema HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:39 +] "GET 
/api/atlas/entities?type=hive_table_v1&property=qualifiedName&value=sales_facts6W3c14CMa
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:39 +] "GET 
/api/atlas/lineage/e65e3919-ad5b-45fa-b034-6d21f68c07e8/schema HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:40 +] "GET 
/api/atlas/entities?type=hive_table_v1&property=qualifiedName&value=sales_fact_monthly_mvIKNP3NSMxi
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:40 +] "GET 
/api/atlas/v2/lineage/7810b2fd-9685-45d9-a5dc-e9e5369fee76?direction=BOTH&depth=5
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:42 +] "GET 
/api/atlas/lineage/hive/table/sales_facts6W3c14CMa/schema HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:50:42 +] "GET 
/api/atla

Build failed in Jenkins: Atlas-master-IntegrationTests #110

2017-09-19 Thread Apache Jenkins Server

See 


Changes:

[madhan] ATLAS-2148: saved-search API enhancement to support searchType

--
[...truncated 449.36 KB...]
127.0.0.1 - - [20/Sep/2017:01:43:17 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:17 +] "GET 
/api/atlas/v2/types/typedef/name/salary_trait HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:17 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:17 +] "GET 
/api/atlas/v2/types/typedef/name/sox_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:17 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:17 +] "GET /api/atlas/types?type=TRAIT 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:17 +] "GET 
/api/atlas/v2/types/typedef/name/AB4uY4AkA5L HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:17 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:18 +] "GET 
/api/atlas/v2/types/typedef/name/A1DvCIPIBOMl HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:18 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:18 +] "GET 
/api/atlas/v2/types/typedef/name/Brr81SURTV3 HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:18 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:18 +] "GET 
/api/atlas/v2/types/typedef/name/CgWKkh2uczt HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:18 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:18 +] "GET 
/api/atlas/types?type=CLASS&supertype=AB4uY4AkA5L¬supertype=Brr81SURTV3 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:18 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:19 +] "PUT /api/atlas/types HTTP/1.1" 200 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:19 +] "GET /api/atlas/types/FVMwxYCR4A 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:38 +] "POST /api/atlas/types HTTP/1.1" 400 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/tableType HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/serdeType HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/classification HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/pii HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/phi HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/pci HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/sox HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/sec HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/finance HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/FactoHlvrClnEe HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/ETLdH5r1LfPrY HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/DimensionwlyTAAArMC HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/MetricpeIR032Oqu HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/hive_db_v1 HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/hive_column_v1 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/hive_table_v1 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "GET 
/api/atlas/v2/types/typedef/name/hive_process_v1 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [20/Sep/2017:01:43:39 +] "POST /api/atlas/types HTTP/1.1" 400 
- "-" "Java/1.7.0_80"
Tests run: 143, Failures: 16, Errors: 0, Skipped: 100, Time elapsed: 35.005 sec 
<<< FAILURE! - in TestSuite
setUp(org.apache.atlas.web.integration.EntityDiscoveryJerseyResourceIT)  Time 
elapsed: 3.913 sec  <<< FAILURE!
org.apache.atlas.AtlasSer

Build failed in Jenkins: Atlas-master-UnitTests #87

2017-09-19 Thread Apache Jenkins Server

See 


Changes:

[madhan] ATLAS-2148: saved-search API enhancement to support searchType

--
[...truncated 261.74 KB...]
Running org.apache.atlas.query.LexerTest
Running 
org.apache.atlas.repository.store.graph.v1.AtlasRelationshipDefStoreV1Test
Running org.apache.atlas.BaseRepositoryTest
Running org.apache.atlas.util.CompiledQueryCacheKeyTest
Running org.apache.atlas.RepositoryServiceLoadingTest
Running org.apache.atlas.query.LineageQueryTest
Running 
org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateHardDeleteV1Test
Running org.apache.atlas.utils.ObjectUpdateSynchronizerTest
Running org.apache.atlas.repository.store.graph.v1.AtlasEntityDefStoreV1Test
Running org.apache.atlas.repository.store.graph.v1.HardDeleteHandlerV1Test
Running 
org.apache.atlas.repository.store.graph.v1.AtlasRelationshipStoreSoftDeleteV1Test
Running org.apache.atlas.query.GremlinTest
Running org.apache.atlas.query.QueryProcessorTest
Running org.apache.atlas.repository.store.graph.v1.AtlasRelationshipStoreV1Test
Running org.apache.atlas.services.MetricsServiceTest
Running org.apache.atlas.repository.store.graph.v1.AtlasDeleteHandlerV1Test
Running org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1Test
Running org.apache.atlas.query.BaseGremlinTest
Running org.apache.atlas.discovery.GraphBackedDiscoveryServiceTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.177 sec - in 
org.apache.atlas.repository.store.graph.v1.InverseReferenceUpdateV1Test
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.653 sec - in 
org.apache.atlas.TestModules
Running org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStoreTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 29.946 sec - in 
org.apache.atlas.util.CompiledQueryCacheKeyTest
Running org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest
Running org.apache.atlas.repository.typestore.StoreBackedTypeCacheTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 29.721 sec - in 
org.apache.atlas.repository.store.graph.v1.AtlasRelationshipStoreV1Test
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 29.611 sec - in 
org.apache.atlas.repository.store.graph.v1.AtlasDeleteHandlerV1Test
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 29.633 sec - in 
org.apache.atlas.query.BaseGremlinTest
Running org.apache.atlas.repository.graph.AbstractGremlinQueryOptimizerTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 31.349 sec - in 
org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1BulkImportPercentTest
Running org.apache.atlas.repository.graph.Gremlin2QueryOptimizerTest
Running org.apache.atlas.repository.graph.TestIntSequence
Running org.apache.atlas.repository.graph.GraphBackedSearchIndexerTest
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 33.324 sec - 
in org.apache.atlas.query.ExpressionTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.515 sec - in 
org.apache.atlas.query.QueryProcessorTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 33.393 sec - in 
org.apache.atlas.BaseRepositoryTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.891 sec - in 
org.apache.atlas.utils.ObjectUpdateSynchronizerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 33.673 sec - in 
org.apache.atlas.query.LexerTest
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.161 sec - 
in org.apache.atlas.query.ParserTest
Running org.apache.atlas.repository.graph.GraphRepoMapperScaleTest
Running org.apache.atlas.repository.graph.ReverseReferenceUpdateHardDeleteTest
Running org.apache.atlas.repository.graph.ReverseReferenceUpdateSoftDeleteTest
Running org.apache.atlas.repository.graph.Gremlin3QueryOptimizerTest
Running org.apache.atlas.repository.graph.GraphHelperTest
Running org.apache.atlas.repository.graph.GraphBackedRepositoryHardDeleteTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 36.515 sec - in 
org.apache.atlas.services.MetricsServiceTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 39.35 sec - in 
org.apache.atlas.discovery.EntityDiscoveryServiceTest
Running org.apache.atlas.repository.graph.GraphBackedRepositorySoftDeleteTest
Running org.apache.atlas.repository.graph.GraphBackedSearchIndexerMockTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 42.174 sec - in 
org.apache.atlas.discovery.DataSetLineageServiceTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 41.725 sec - in 
org.apache.atlas.RepositoryServiceLoadingTest
Running org.apache.atlas.repository.graph.GraphHelperMockTest
Running org.apache.atlas.repository.graph.GraphBackedMetadataRepositoryTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 42.99 sec - in 
org.apache.atlas.repositor

[jira] [Resolved] (ATLAS-2148) Saved Search: Introduce BASIC and ADVANCE Search Types During Save

2017-09-19 Thread Madhan Neethiraj (JIRA)


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

Madhan Neethiraj resolved ATLAS-2148.
-
   Resolution: Fixed
Fix Version/s: 0.8.2
   0.9-incubating

Committed to following branches:
 - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/400477c4
 - branch-0.8: http://git-wip-us.apache.org/repos/asf/atlas/commit/2dc137c1

> Saved Search: Introduce BASIC and ADVANCE Search Types During Save
> --
>
> Key: ATLAS-2148
> URL: https://issues.apache.org/jira/browse/ATLAS-2148
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-webui
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Minor
> Fix For: 0.9-incubating, 0.8.2
>
> Attachments: ATLAS-2148-QueryType.patch
>
>
> *Background*
> Existing implementation of _SavedSearch_ does not have a way to differentiate 
> saving of basic and advanced searches.
> Basic searches are the ones where user constructs the query using the new 
> search UI.
> Advanced queries are where the user types a DSL query into the search box.
> Having this notion should allow for better differentiation of the 2 types of 
> queries. If the type is used in specifying unique attribute, user could 
> create query with same name.
> *Implementation*
> Additional attribute added to ___AtlasSavedSearch_. REST API updated to 
> include the query type parameter.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 62420: ATLAS-2148: Enhancement to Saved Search

2017-09-19 Thread Madhan Neethiraj


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62420/#review185761
---


Ship it!




Ship It!

- Madhan Neethiraj


On Sept. 19, 2017, 11:33 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62420/
> ---
> 
> (Updated Sept. 19, 2017, 11:33 p.m.)
> 
> 
> Review request for atlas, keval bhatt and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2148
> https://issues.apache.org/jira/browse/ATLAS-2148
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Implementation**
> 
> - _DataAccess.save_ now returns entity with GUID set. Logic uses 
> _EntityMutationResponse_ for inferring the GUID.
> - REST APIs have undergone minor changes. CURL calls updated (see below).
> 
> 
> _Please used attached JSON for the examples below._
> 
> **Retrieve List of Saved Searches**
> ```javascript
> curl -g -X GET -u admin:admin -H "Content-Type: application/json" -H 
> "Cache-Control: no-cache"  "http://localhost:21000/api/atlas/v2/search/saved";
> ```
> 
> **Retrieve Specific Saved Searches**
> 
> ```javascript
> curl -g -X GET -u admin:admin -H "Content-Type: application/json" -H 
> "Cache-Control: no-cache"  
> "http://localhost:21000/api/atlas/v2/search/saved/BASIC/my_search1";
> ```
> 
> ```javascript
> curl -g -X GET -u admin:admin -H "Content-Type: application/json" -H 
> "Cache-Control: no-cache"  
> "http://localhost:21000/api/atlas/v2/search/saved/ADVANCED/my_search3";
> ```
> 
> **Save**
> ```javascript
> curl -g -X POST -u admin:admin -H "Content-Type: application/json" -H 
> "Cache-Control: no-cache"  "http://localhost:21000/api/atlas/v2/search/saved"; 
> -d @../docs/savedSearch.json
> ```
> 
> **Update**
> ```javascript
> curl -g -X PUT -u admin:admin -H "Content-Type: application/json" -H 
> "Cache-Control: no-cache"  "http://localhost:21000/api/atlas/v2/search/saved"; 
> -d @../docs/savedSearch.json
> ```
> 
> **Delete**
> ```javascript
> curl -g -X DELETE -u admin:admin -H "Content-Type: application/json" -H 
> "Cache-Control: no-cache"  
> "http://localhost:21000/api/atlas/v2/search/saved/0d0f75ef-b101-466f-843e-60196b81c98e";
> ```
> 
> 
> Diffs
> -
> 
>   addons/models/0010-base_model.json 8f38f596 
>   intg/src/main/java/org/apache/atlas/model/profile/AtlasUserSavedSearch.java 
> b0698fcf 
>   
> repository/src/main/java/org/apache/atlas/discovery/AtlasDiscoveryService.java
>  baaee85d 
>   
> repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java
>  ad21ee48 
>   
> repository/src/main/java/org/apache/atlas/repository/ogm/AtlasSavedSearchDTO.java
>  26eee200 
>   repository/src/main/java/org/apache/atlas/repository/ogm/DataAccess.java 
> bc93cc6e 
>   
> repository/src/main/java/org/apache/atlas/repository/userprofile/UserProfileService.java
>  766d1c7d 
>   
> repository/src/test/java/org/apache/atlas/repository/userprofile/UserProfileServiceTest.java
>  4e832968 
>   webapp/src/main/java/org/apache/atlas/web/rest/DiscoveryREST.java ad595c81 
> 
> 
> Diff: https://reviews.apache.org/r/62420/diff/3/
> 
> 
> Testing
> ---
> 
> **Unit tests**
> Updated to reflect new logic.
> 
> **Functional tests**
> From the new UI.
> CURL calls.
> 
> 
> File Attachments
> 
> 
> saved Search
>   
> https://reviews.apache.org/media/uploaded/files/2017/09/19/f9f6ec2d-28f6-487a-8126-aaf6fc8a1028__savedSearch.json
> saved search for update
>   
> https://reviews.apache.org/media/uploaded/files/2017/09/19/2b1d4619-65d8-4435-87cb-9b11878a7420__savedSearch-for-update.json
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

Re: Review Request 62420: ATLAS-2148: Enhancement to Saved Search

2017-09-19 Thread Ashutosh Mestry


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62420/
---

(Updated Sept. 19, 2017, 11:33 p.m.)


Review request for atlas, keval bhatt and Madhan Neethiraj.


Changes
---

Updates include:
- Additional refactoring.


Bugs: ATLAS-2148
https://issues.apache.org/jira/browse/ATLAS-2148


Repository: atlas


Description
---

**Implementation**

- _DataAccess.save_ now returns entity with GUID set. Logic uses 
_EntityMutationResponse_ for inferring the GUID.
- REST APIs have undergone minor changes. CURL calls updated (see below).


_Please used attached JSON for the examples below._

**Retrieve List of Saved Searches**
```javascript
curl -g -X GET -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  "http://localhost:21000/api/atlas/v2/search/saved";
```

**Retrieve Specific Saved Searches**

```javascript
curl -g -X GET -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  
"http://localhost:21000/api/atlas/v2/search/saved/BASIC/my_search1";
```

```javascript
curl -g -X GET -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  
"http://localhost:21000/api/atlas/v2/search/saved/ADVANCED/my_search3";
```

**Save**
```javascript
curl -g -X POST -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  "http://localhost:21000/api/atlas/v2/search/saved"; 
-d @../docs/savedSearch.json
```

**Update**
```javascript
curl -g -X PUT -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  "http://localhost:21000/api/atlas/v2/search/saved"; 
-d @../docs/savedSearch.json
```

**Delete**
```javascript
curl -g -X DELETE -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  
"http://localhost:21000/api/atlas/v2/search/saved/0d0f75ef-b101-466f-843e-60196b81c98e";
```


Diffs (updated)
-

  addons/models/0010-base_model.json 8f38f596 
  intg/src/main/java/org/apache/atlas/model/profile/AtlasUserSavedSearch.java 
b0698fcf 
  
repository/src/main/java/org/apache/atlas/discovery/AtlasDiscoveryService.java 
baaee85d 
  
repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java 
ad21ee48 
  
repository/src/main/java/org/apache/atlas/repository/ogm/AtlasSavedSearchDTO.java
 26eee200 
  repository/src/main/java/org/apache/atlas/repository/ogm/DataAccess.java 
bc93cc6e 
  
repository/src/main/java/org/apache/atlas/repository/userprofile/UserProfileService.java
 766d1c7d 
  
repository/src/test/java/org/apache/atlas/repository/userprofile/UserProfileServiceTest.java
 4e832968 
  webapp/src/main/java/org/apache/atlas/web/rest/DiscoveryREST.java ad595c81 


Diff: https://reviews.apache.org/r/62420/diff/3/

Changes: https://reviews.apache.org/r/62420/diff/2-3/


Testing
---

**Unit tests**
Updated to reflect new logic.

**Functional tests**
>From the new UI.
CURL calls.


File Attachments


saved Search
  
https://reviews.apache.org/media/uploaded/files/2017/09/19/f9f6ec2d-28f6-487a-8126-aaf6fc8a1028__savedSearch.json
saved search for update
  
https://reviews.apache.org/media/uploaded/files/2017/09/19/2b1d4619-65d8-4435-87cb-9b11878a7420__savedSearch-for-update.json


Thanks,

Ashutosh Mestry

Re: Review Request 62420: ATLAS-2148: Enhancement to Saved Search

2017-09-19 Thread Ashutosh Mestry


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62420/
---

(Updated Sept. 19, 2017, 10:40 p.m.)


Review request for atlas, keval bhatt and Madhan Neethiraj.


Changes
---

Updates includes:
- JSONs for new query & updated query.


Bugs: ATLAS-2148
https://issues.apache.org/jira/browse/ATLAS-2148


Repository: atlas


Description
---

**Implementation**

- _DataAccess.save_ now returns entity with GUID set. Logic uses 
_EntityMutationResponse_ for inferring the GUID.
- REST APIs have undergone minor changes. CURL calls updated (see below).


_Please used attached JSON for the examples below._

**Retrieve List of Saved Searches**
```javascript
curl -g -X GET -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  "http://localhost:21000/api/atlas/v2/search/saved";
```

**Retrieve Specific Saved Searches**

```javascript
curl -g -X GET -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  
"http://localhost:21000/api/atlas/v2/search/saved/BASIC/my_search1";
```

```javascript
curl -g -X GET -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  
"http://localhost:21000/api/atlas/v2/search/saved/ADVANCED/my_search3";
```

**Save**
```javascript
curl -g -X POST -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  "http://localhost:21000/api/atlas/v2/search/saved"; 
-d @../docs/savedSearch.json
```

**Update**
```javascript
curl -g -X PUT -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  "http://localhost:21000/api/atlas/v2/search/saved"; 
-d @../docs/savedSearch.json
```

**Delete**
```javascript
curl -g -X DELETE -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  
"http://localhost:21000/api/atlas/v2/search/saved/0d0f75ef-b101-466f-843e-60196b81c98e";
```


Diffs
-

  addons/models/0010-base_model.json 8f38f596 
  intg/src/main/java/org/apache/atlas/model/profile/AtlasUserSavedSearch.java 
b0698fcf 
  
repository/src/main/java/org/apache/atlas/discovery/AtlasDiscoveryService.java 
baaee85d 
  
repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java 
ad21ee48 
  
repository/src/main/java/org/apache/atlas/repository/ogm/AtlasSavedSearchDTO.java
 26eee200 
  repository/src/main/java/org/apache/atlas/repository/ogm/DataAccess.java 
bc93cc6e 
  
repository/src/main/java/org/apache/atlas/repository/userprofile/UserProfileService.java
 766d1c7d 
  
repository/src/test/java/org/apache/atlas/repository/userprofile/UserProfileServiceTest.java
 4e832968 
  webapp/src/main/java/org/apache/atlas/web/rest/DiscoveryREST.java ad595c81 


Diff: https://reviews.apache.org/r/62420/diff/2/


Testing
---

**Unit tests**
Updated to reflect new logic.

**Functional tests**
>From the new UI.
CURL calls.


File Attachments (updated)


saved Search
  
https://reviews.apache.org/media/uploaded/files/2017/09/19/f9f6ec2d-28f6-487a-8126-aaf6fc8a1028__savedSearch.json
saved search for update
  
https://reviews.apache.org/media/uploaded/files/2017/09/19/2b1d4619-65d8-4435-87cb-9b11878a7420__savedSearch-for-update.json


Thanks,

Ashutosh Mestry

Re: Review Request 62420: ATLAS-2148: Enhancement to Saved Search

2017-09-19 Thread Ashutosh Mestry


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62420/
---

(Updated Sept. 19, 2017, 10:37 p.m.)


Review request for atlas, keval bhatt and Madhan Neethiraj.


Changes
---

Updates include:
- Minor refactoring.


Bugs: ATLAS-2148
https://issues.apache.org/jira/browse/ATLAS-2148


Repository: atlas


Description
---

**Implementation**

- _DataAccess.save_ now returns entity with GUID set. Logic uses 
_EntityMutationResponse_ for inferring the GUID.
- REST APIs have undergone minor changes. CURL calls updated (see below).


_Please used attached JSON for the examples below._

**Retrieve List of Saved Searches**
```javascript
curl -g -X GET -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  "http://localhost:21000/api/atlas/v2/search/saved";
```

**Retrieve Specific Saved Searches**

```javascript
curl -g -X GET -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  
"http://localhost:21000/api/atlas/v2/search/saved/BASIC/my_search1";
```

```javascript
curl -g -X GET -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  
"http://localhost:21000/api/atlas/v2/search/saved/ADVANCED/my_search3";
```

**Save**
```javascript
curl -g -X POST -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  "http://localhost:21000/api/atlas/v2/search/saved"; 
-d @../docs/savedSearch.json
```

**Update**
```javascript
curl -g -X PUT -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  "http://localhost:21000/api/atlas/v2/search/saved"; 
-d @../docs/savedSearch.json
```

**Delete**
```javascript
curl -g -X DELETE -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  
"http://localhost:21000/api/atlas/v2/search/saved/0d0f75ef-b101-466f-843e-60196b81c98e";
```


Diffs (updated)
-

  addons/models/0010-base_model.json 8f38f596 
  intg/src/main/java/org/apache/atlas/model/profile/AtlasUserSavedSearch.java 
b0698fcf 
  
repository/src/main/java/org/apache/atlas/discovery/AtlasDiscoveryService.java 
baaee85d 
  
repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java 
ad21ee48 
  
repository/src/main/java/org/apache/atlas/repository/ogm/AtlasSavedSearchDTO.java
 26eee200 
  repository/src/main/java/org/apache/atlas/repository/ogm/DataAccess.java 
bc93cc6e 
  
repository/src/main/java/org/apache/atlas/repository/userprofile/UserProfileService.java
 766d1c7d 
  
repository/src/test/java/org/apache/atlas/repository/userprofile/UserProfileServiceTest.java
 4e832968 
  webapp/src/main/java/org/apache/atlas/web/rest/DiscoveryREST.java ad595c81 


Diff: https://reviews.apache.org/r/62420/diff/2/

Changes: https://reviews.apache.org/r/62420/diff/1-2/


Testing
---

**Unit tests**
Updated to reflect new logic.

**Functional tests**
>From the new UI.
CURL calls.


File Attachments


Saved Search JSON
  
https://reviews.apache.org/media/uploaded/files/2017/09/19/f845e2cf-3354-48e4-bfed-76b09a581af2__savedSearch.json


Thanks,

Ashutosh Mestry

[jira] [Updated] (ATLAS-2148) Saved Search: Introduce BASIC and ADVANCE Search Types During Save

2017-09-19 Thread Ashutosh Mestry (JIRA)


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

Ashutosh Mestry updated ATLAS-2148:
---
Attachment: ATLAS-2148-QueryType.patch

> Saved Search: Introduce BASIC and ADVANCE Search Types During Save
> --
>
> Key: ATLAS-2148
> URL: https://issues.apache.org/jira/browse/ATLAS-2148
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-webui
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Minor
> Attachments: ATLAS-2148-QueryType.patch
>
>
> *Background*
> Existing implementation of _SavedSearch_ does not have a way to differentiate 
> saving of basic and advanced searches.
> Basic searches are the ones where user constructs the query using the new 
> search UI.
> Advanced queries are where the user types a DSL query into the search box.
> Having this notion should allow for better differentiation of the 2 types of 
> queries. If the type is used in specifying unique attribute, user could 
> create query with same name.
> *Implementation*
> Additional attribute added to ___AtlasSavedSearch_. REST API updated to 
> include the query type parameter.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Review Request 62420: ATLAS-2148: Enhancement to Saved Search

2017-09-19 Thread Ashutosh Mestry


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62420/
---

Review request for atlas, keval bhatt and Madhan Neethiraj.


Bugs: ATLAS-2148
https://issues.apache.org/jira/browse/ATLAS-2148


Repository: atlas


Description
---

**Implementation**

- _DataAccess.save_ now returns entity with GUID set. Logic uses 
_EntityMutationResponse_ for inferring the GUID.
- REST APIs have undergone minor changes. CURL calls updated (see below).


_Please used attached JSON for the examples below._

**Retrieve List of Saved Searches**
```javascript
curl -g -X GET -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  "http://localhost:21000/api/atlas/v2/search/saved";
```

**Retrieve Specific Saved Searches**

```javascript
curl -g -X GET -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  
"http://localhost:21000/api/atlas/v2/search/saved/BASIC/my_search1";
```

```javascript
curl -g -X GET -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  
"http://localhost:21000/api/atlas/v2/search/saved/ADVANCED/my_search3";
```

**Save**
```javascript
curl -g -X POST -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  "http://localhost:21000/api/atlas/v2/search/saved"; 
-d @../docs/savedSearch.json
```

**Update**
```javascript
curl -g -X PUT -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  "http://localhost:21000/api/atlas/v2/search/saved"; 
-d @../docs/savedSearch.json
```

**Delete**
```javascript
curl -g -X DELETE -u admin:admin -H "Content-Type: application/json" -H 
"Cache-Control: no-cache"  
"http://localhost:21000/api/atlas/v2/search/saved/0d0f75ef-b101-466f-843e-60196b81c98e";
```


Diffs
-

  addons/models/0010-base_model.json 8f38f59 
  intg/src/main/java/org/apache/atlas/model/profile/AtlasUserSavedSearch.java 
b0698fc 
  
repository/src/main/java/org/apache/atlas/discovery/AtlasDiscoveryService.java 
baaee85 
  
repository/src/main/java/org/apache/atlas/discovery/EntityDiscoveryService.java 
ad21ee4 
  
repository/src/main/java/org/apache/atlas/repository/ogm/AtlasSavedSearchDTO.java
 26eee20 
  repository/src/main/java/org/apache/atlas/repository/ogm/DataAccess.java 
bc93cc6 
  
repository/src/main/java/org/apache/atlas/repository/userprofile/UserProfileService.java
 766d1c7 
  
repository/src/test/java/org/apache/atlas/repository/userprofile/UserProfileServiceTest.java
 4e83296 
  webapp/src/main/java/org/apache/atlas/web/rest/DiscoveryREST.java ad595c8 


Diff: https://reviews.apache.org/r/62420/diff/1/


Testing
---

**Unit tests**
Updated to reflect new logic.

**Functional tests**
>From the new UI.
CURL calls.


File Attachments


Saved Search JSON
  
https://reviews.apache.org/media/uploaded/files/2017/09/19/f845e2cf-3354-48e4-bfed-76b09a581af2__savedSearch.json


Thanks,

Ashutosh Mestry

[jira] [Updated] (ATLAS-2148) Saved Search: Introduce BASIC and ADVANCE Search Types During Save

2017-09-19 Thread Ashutosh Mestry (JIRA)


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

Ashutosh Mestry updated ATLAS-2148:
---
Description: 
*Background*
Existing implementation of _SavedSearch_ does not have a way to differentiate 
saving of basic and advanced searches.

Basic searches are the ones where user constructs the query using the new 
search UI.

Advanced queries are where the user types a DSL query into the search box.

Having this notion should allow for better differentiation of the 2 types of 
queries. If the type is used in specifying unique attribute, user could create 
query with same name.

*Implementation*
Additional attribute added to ___AtlasSavedSearch_. REST API updated to include 
the query type parameter.


  was:
*Background*
Existing implementation of _SavedSearch_ does not have a way to differentiate 
saving of basic and advanced searches.

Basic searches are the ones where user constructs the query using the new 
search UI.

Advanced queries are where the user types a DSL query into the search box.

Having this notion should allow for better differentiation of the 2 types of 
queries. If the type is used in specifying unique attribute, user could create 
query with same name.

*Implementation*
Additional attribute added to __AtlasSavedSearch. REST API updated to include 
the query type parameter.



> Saved Search: Introduce BASIC and ADVANCE Search Types During Save
> --
>
> Key: ATLAS-2148
> URL: https://issues.apache.org/jira/browse/ATLAS-2148
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core, atlas-webui
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Minor
>
> *Background*
> Existing implementation of _SavedSearch_ does not have a way to differentiate 
> saving of basic and advanced searches.
> Basic searches are the ones where user constructs the query using the new 
> search UI.
> Advanced queries are where the user types a DSL query into the search box.
> Having this notion should allow for better differentiation of the 2 types of 
> queries. If the type is used in specifying unique attribute, user could 
> create query with same name.
> *Implementation*
> Additional attribute added to ___AtlasSavedSearch_. REST API updated to 
> include the query type parameter.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2148) Saved Search: Introduce BASIC and ADVANCE Search Types During Save

2017-09-19 Thread Ashutosh Mestry (JIRA)

Ashutosh Mestry created ATLAS-2148:
--

 Summary: Saved Search: Introduce BASIC and ADVANCE Search Types 
During Save
 Key: ATLAS-2148
 URL: https://issues.apache.org/jira/browse/ATLAS-2148
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core, atlas-webui
Affects Versions: trunk
Reporter: Ashutosh Mestry
Assignee: Ashutosh Mestry
Priority: Minor


*Background*
Existing implementation of _SavedSearch_ does not have a way to differentiate 
saving of basic and advanced searches.

Basic searches are the ones where user constructs the query using the new 
search UI.

Advanced queries are where the user types a DSL query into the search box.

Having this notion should allow for better differentiation of the 2 types of 
queries. If the type is used in specifying unique attribute, user could create 
query with same name.

*Implementation*
Additional attribute added to __AtlasSavedSearch. REST API updated to include 
the query type parameter.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 62416: ATLAS-2121: Case sensitivity for tag/type name search with index

2017-09-19 Thread Apoorv Naik


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62416/
---

(Updated Sept. 19, 2017, 7:15 p.m.)


Review request for atlas and Madhan Neethiraj.


Bugs: ATLAS-2121
https://issues.apache.org/jira/browse/ATLAS-2121


Repository: atlas


Description
---

Currently the index query returns case insensitive results, this patch add the 
typename / tag name check to the in memory predicate to honor case sensitivity.


Diffs (updated)
-

  
repository/src/main/java/org/apache/atlas/discovery/ClassificationSearchProcessor.java
 1d4815df 
  
repository/src/main/java/org/apache/atlas/discovery/EntitySearchProcessor.java 
970cd28e 


Diff: https://reviews.apache.org/r/62416/diff/2/

Changes: https://reviews.apache.org/r/62416/diff/1-2/


Testing
---

UI and REST calls work as expected.


Thanks,

Apoorv Naik

Review Request 62416: ATLAS-2121: Case sensitivity for tag/type name search with index

2017-09-19 Thread Apoorv Naik


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62416/
---

Review request for atlas and Madhan Neethiraj.


Bugs: ATLAS-2121
https://issues.apache.org/jira/browse/ATLAS-2121


Repository: atlas


Description
---

Currently the index query returns case insensitive results, this patch add the 
typename / tag name check to the in memory predicate to honor case sensitivity.


Diffs
-

  
repository/src/main/java/org/apache/atlas/discovery/ClassificationSearchProcessor.java
 1d4815df 
  
repository/src/main/java/org/apache/atlas/discovery/EntitySearchProcessor.java 
970cd28e 


Diff: https://reviews.apache.org/r/62416/diff/1/


Testing
---

UI and REST calls work as expected.


Thanks,

Apoorv Naik

[jira] [Reopened] (ATLAS-2121) Inconsistency in basic search results due to case sensitivity of type names

2017-09-19 Thread Apoorv Naik (JIRA)


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

Apoorv Naik reopened ATLAS-2121:


Actually the typename and tag name case sensitivity check was missed in 
ATLAS-2117. Reopening with a new review and patch.

> Inconsistency in basic search results due to case sensitivity of type names
> ---
>
> Key: ATLAS-2121
> URL: https://issues.apache.org/jira/browse/ATLAS-2121
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Critical
>
> Type names are case sensitive hence 2 types can be created with different 
> cases. 
> Example :
> 1. type1 with attributes a , b
> 2. TYPE1 with attributes c , d
> The types creation succeeds and 
> {code}
> /api/atlas/v2/types/entitydef/name/type1
> /api/atlas/v2/types/entitydef/name/TYPE1
> {code}
> return the corresponding type definitions correctly.
> When an entity e1 of type1 is created, 
> and when a BASIC search is fired with
>  typeName= type1 , e1 is returned and
>  typeName=TYPE1 also , e1 is returned.
> But in the case of DSL search , 
> typeName = type1 returns e1
> typeName = TYPE1 doesn't return any result - which is the correct behavior.
> This issue is major from tag side too because , UI Tag search is Basic and 
> returns entity tagged with tag1 when searched for tag1 or TAG1.
> Whereas DSL search with
> classification=tag1 returns entity
> classification=TAG1 does not return any entity. - which is the correct 
> behavior.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2031) Allow EntityDef deletion

2017-09-19 Thread David Radley (JIRA)


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

David Radley updated ATLAS-2031:

Attachment: ATLAS2031.patch

> Allow EntityDef deletion
> 
>
> Key: ATLAS-2031
> URL: https://issues.apache.org/jira/browse/ATLAS-2031
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: David Radley
>Assignee: David Radley
> Attachments: ATLAS2031.patch
>
>
> Allow entityTypes to be removed from classificationDef so that is is possible 
> to delete the entityDef. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Review Request 62405: ATLAS2031 Allow AtlasClassificationDef entitytypes removal

2017-09-19 Thread David Radley


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62405/
---

Review request for atlas and Madhan Neethiraj.


Repository: atlas


Description
---

ATLAS2031 Allow AtlasClassificationDef entitytypes removal


Diffs
-

  intg/src/main/java/org/apache/atlas/AtlasErrorCode.java d205faf5 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasClassificationDefStoreV1.java
 8214cea6 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasTypeDefGraphStoreV1.java
 603516d4 


Diff: https://reviews.apache.org/r/62405/diff/1/


Testing
---

1) create a classificationDef with 2 valid entityTypes EntityA and EntityB
2) update classification def to remove EntityTypeB
3) create an instance of EntityC , try to apply the classificaiton to it . It 
should fail
4) update the classification to have an empty list of classifications.
5) Repeat step 3 and it should now work.


Thanks,

David Radley

[jira] [Updated] (ATLAS-2031) EntityDef deletion

2017-09-19 Thread David Radley (JIRA)


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

David Radley updated ATLAS-2031:

Description: Allow entityTypes to be removed from classificationDef so that 
is is possible to delete the entityDef.   (was: 
- if there is a classificationdef that refers to this entitydef - then do not 
allow the deletion to proceed. 
- allow entityTypes to be removed from classificationDef so that is is possible 
to delete the entityDef. )

> EntityDef deletion
> --
>
> Key: ATLAS-2031
> URL: https://issues.apache.org/jira/browse/ATLAS-2031
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: David Radley
>Assignee: David Radley
>
> Allow entityTypes to be removed from classificationDef so that is is possible 
> to delete the entityDef. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2031) Allow EntityDef deletion

2017-09-19 Thread David Radley (JIRA)


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

David Radley updated ATLAS-2031:

Summary: Allow EntityDef deletion  (was: EntityDef deletion)

> Allow EntityDef deletion
> 
>
> Key: ATLAS-2031
> URL: https://issues.apache.org/jira/browse/ATLAS-2031
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: David Radley
>Assignee: David Radley
>
> Allow entityTypes to be removed from classificationDef so that is is possible 
> to delete the entityDef. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2147) querying supertype "Asset" with multiple filters fails with "unresolved datatype. Can not resolve due to unresolved children"

2017-09-19 Thread Ayub Pathan (JIRA)

Ayub Pathan created ATLAS-2147:
--

 Summary: querying supertype "Asset" with multiple filters fails 
with "unresolved datatype. Can not resolve due to unresolved children"
 Key: ATLAS-2147
 URL: https://issues.apache.org/jira/browse/ATLAS-2147
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.9.1
Reporter: Ayub Pathan
 Fix For: 0.9.1


Example query with multiple filters: Asset where (name="") or 
(qualifiesName="")
Stacktrace:
{noformat}
2017-09-19 14:37:15,166 ERROR - [pool-1-thread-9 - 
1ca16b19-634e-48bb-b872-20025c210b75:] ~ graph rollback due to exception  
(GraphTransactionInterceptor:71)
org.apache.atlas.query.Expressions$UnresolvedException: Unresolved datatype. 
Can not resolve due to unresolved children, expression: Asset where (name = 
"h7") or (qualifiedName = "default.h7@primary")
at 
org.apache.atlas.query.Expressions$FilterExpression.dataType$lzycompute(Expressions.scala:708)
at 
org.apache.atlas.query.Expressions$FilterExpression.dataType(Expressions.scala:706)
at org.apache.atlas.query.Resolver.apply(Resolver.scala:48)
at org.apache.atlas.query.Resolver.apply(Resolver.scala:25)
at scala.PartialFunction$class.applyOrElse(PartialFunction.scala:123)
at org.apache.atlas.query.Resolver.applyOrElse(Resolver.scala:25)
at 
org.apache.atlas.query.Expressions$Expression$class.transformUp(Expressions.scala:201)
at 
org.apache.atlas.query.Expressions$IdExpression.transformUp(Expressions.scala:404)
at 
org.apache.atlas.query.Expressions$Expression$$anonfun$4.apply(Expressions.scala:211)
at scala.collection.Iterator$$anon$11.next(Iterator.scala:409)
at scala.collection.Iterator$class.foreach(Iterator.scala:893)
at scala.collection.AbstractIterator.foreach(Iterator.scala:1336)
at 
scala.collection.generic.Growable$class.$plus$plus$eq(Growable.scala:59)
at 
scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:104)
at 
scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:48)
at scala.collection.TraversableOnce$class.to(TraversableOnce.scala:310)
at scala.collection.AbstractIterator.to(Iterator.scala:1336)
at 
scala.collection.TraversableOnce$class.toBuffer(TraversableOnce.scala:302)
at scala.collection.AbstractIterator.toBuffer(Iterator.scala:1336)
at 
scala.collection.TraversableOnce$class.toArray(TraversableOnce.scala:289)
at scala.collection.AbstractIterator.toArray(Iterator.scala:1336)
at 
org.apache.atlas.query.Expressions$Expression$class.transformChildrenUp(Expressions.scala:240)
at 
org.apache.atlas.query.Expressions$BinaryExpression.transformChildrenUp(Expressions.scala:367)
at 
org.apache.atlas.query.Expressions$Expression$class.transformUp(Expressions.scala:199)
at 
org.apache.atlas.query.Expressions$BinaryExpression.transformUp(Expressions.scala:367)
at 
org.apache.atlas.query.Expressions$Expression$$anonfun$4$$anonfun$apply$3.apply(Expressions.scala:229)
at 
scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
at 
scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
at scala.collection.immutable.List.foreach(List.scala:381)
at scala.collection.TraversableLike$class.map(TraversableLike.scala:234)
at scala.collection.immutable.List.map(List.scala:285)
at 
org.apache.atlas.query.Expressions$Expression$$anonfun$4.apply(Expressions.scala:227)
at scala.collection.Iterator$$anon$11.next(Iterator.scala:409)
at scala.collection.Iterator$class.foreach(Iterator.scala:893)
at scala.collection.AbstractIterator.foreach(Iterator.scala:1336)
at 
scala.collection.generic.Growable$class.$plus$plus$eq(Growable.scala:59)
at 
scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:104)
at 
scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:48)
at scala.collection.TraversableOnce$class.to(TraversableOnce.scala:310)
at scala.collection.AbstractIterator.to(Iterator.scala:1336)
at 
scala.collection.TraversableOnce$class.toBuffer(TraversableOnce.scala:302)
at scala.collection.AbstractIterator.toBuffer(Iterator.scala:1336)
at 
scala.collection.TraversableOnce$class.toArray(TraversableOnce.scala:289)
at scala.collection.AbstractIterator.toArray(Iterator.scala:1336)
at 
org.apache.atlas.query.Expressions$Expression$class.transformChildrenUp(Expressions.scala:240)
at 
org.apache.atlas.query.Expressions$LogicalExpression.transformChildrenUp(Expressions.scala:684)
at 
org.apache.atlas.query.Expressions$Expression$class.transformUp(Expressions.scala:199)
at 
org.apache.at

Build failed in Jenkins: Atlas-0.8-UnitTests #66

2017-09-19 Thread Apache Jenkins Server

See 


Changes:

[madhan] ATLAS-2132: incorrect error for invalid file path/unreadable file

--
[...truncated 451.80 KB...]
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 50 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

[INFO] Webapp assembled in [1947 msecs]
[INFO] Building war: 

[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ 
atlas-webapp ---
[INFO] 
[INFO] --- enunciate-maven-plugin:2.8.0:docs (default) @ atlas-webapp ---
[INFO] [ENUNCIATE] Skipping enunciate per configuration.
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-webapp ---
[WARNING] The parameter forkMode is deprecated since version 2.14. Use 
forkCount and reuseForks instead.
[INFO] Surefire report directory: 

[INFO] Using configured provider org.apache.maven.surefire.testng.TestNGProvider
[WARNING] file.encoding cannot be set as system property, use 
-Dfile.encoding=... instead

---
 T E S T S
---
Running org.apache.atlas.util.RestUtilsTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.308 sec - in 
org.apache.atlas.util.RestUtilsTest
Running org.apache.atlas.web.setup.SetupStepsTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.24 sec - in 
org.apache.atlas.web.setup.SetupStepsTest
Running org.apache.atlas.web.security.NegativeSSLAndKerberosTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 47.962 sec - in 
org.apache.atlas.web.security.NegativeSSLAndKerberosTest
Running org.apache.atlas.web.security.FileAuthenticationTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.727 sec - in 
org.apache.atlas.web.security.FileAuthenticationTest
Running org.apache.atlas.web.security.SSLAndKerberosTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 60.881 sec - in 
org.apache.atlas.web.security.SSLAndKerberosTest
Running org.apache.atlas.web.security.UserDaoTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.63 sec - in 
org.apache.atlas.web.security.UserDaoTest
Running org.apache.atlas.web.security.SSLTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 26.746 sec - in 
org.apache.atlas.web.security.SSLTest
Running org.apache.atlas.web.util.ServletsTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.737 sec - in 
org.apache.atlas.web.util.ServletsTest
Running org.apache.atlas.web.resources.AdminResourceTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.157 sec - in 
org.apache.atlas.web.resources.AdminResourceTest
Running org.apache.atlas.web.resources.TaxonomyServiceTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.145 sec - in 
org.apache.atlas.web.resources.TaxonomyServiceTest
Running org.apache.atlas.web.resources.EntityResourceTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.55 sec - in 
org.apache.atlas.web.resources.EntityResourceTest
Running org.apache.atlas.web.resources.AdminExportTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.252 sec - in 
org.apache.atlas.web.resources.AdminExportTes

Build failed in Jenkins: Atlas-0.8-IntegrationTests #68

2017-09-19 Thread Apache Jenkins Server

See 


Changes:

[madhan] ATLAS-2132: incorrect error for invalid file path/unreadable file

--
[...truncated 535.27 KB...]
127.0.0.1 - - [19/Sep/2017:07:53:47 +] "GET 
/api/atlas/v2/types/classificationdef/name/blah HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:47 +] "GET 
/api/atlas/v2/types/classificationdef/guid/blah HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:47 +] "GET 
/api/atlas/v2/types/entitydef/name/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:47 +] "GET 
/api/atlas/v2/types/entitydef/guid/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:47 +] "POST /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:47 +] "GET 
/api/atlas/v2/types/typedefs/?supertype=AmCWthYYQhJ&type=CLASS HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:47 +] "GET 
/api/atlas/v2/types/typedefs/?notsupertype=Bo8z7Ew8H07&supertype=AmCWthYYQhJ&type=CLASS
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:47 +] "POST /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:47 +] "PUT /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:48 +] "GET 
/api/atlas/v2/types/typedefs/?type=ENTITY HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:48 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:48 +] "POST /api/atlas/types HTTP/1.1" 409 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:48 +] "GET /api/atlas/types/blah HTTP/1.1" 
404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:48 +] "GET 
/api/atlas/v2/types/typedef/name/class_trait HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:48 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:48 +] "GET 
/api/atlas/v2/types/typedef/name/secure_trait HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:48 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:48 +] "GET 
/api/atlas/v2/types/typedef/name/pii_trait HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:48 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:49 +] "GET 
/api/atlas/v2/types/typedef/name/ssn_trait HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:49 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:49 +] "GET 
/api/atlas/v2/types/typedef/name/salary_trait HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:49 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:49 +] "GET 
/api/atlas/v2/types/typedef/name/sox_trait HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:49 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:49 +] "GET /api/atlas/types?type=TRAIT 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:49 +] "GET 
/api/atlas/v2/types/typedef/name/AvB69Z2RgF1 HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:49 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:49 +] "GET 
/api/atlas/v2/types/typedef/name/A1VWivS235qW HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:49 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:50 +] "GET 
/api/atlas/v2/types/typedef/name/Bub6qPrixhl HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:50 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:50 +] "GET 
/api/atlas/v2/types/typedef/name/CsTgFBJWQXM HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:50 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:50 +] "GET 
/api/atlas/types?type=CLASS&supertype=AvB69Z2RgF1¬supertype=Bub6qPrixhl 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:50 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:50 +] "PUT /api/atlas/types HTTP/1.1" 200 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:53:51 +] "GET /api/atlas/types/EWhhzMJVGP 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:54:08 +] "GET 
/api/atlas/v2/types/typedef/name/tableType HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Sep/2017:07:54:08 +] "GET 
/api/atlas/v2/types/

48 matches

Mail list logo