Review Request 62236: ATLAS-2128 : UI Regression : DSL Results pagination doesn't spawn more than 2 pages

2017-09-11 Thread keval bhatt 

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

Review request for atlas, Apoorv Naik, Ayub Pathan, Madhan Neethiraj, Nixon 
Rodrigues, Sarath Subramanian, and Sharmadha Sainath.


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


Repository: atlas


Description
---

1. Created 300 hive_tables.
2. On Basic Search in UI , fired search typename= hive_table
3. hive_table results were fetched across 12 pages - 25 entities in each page - 
which is the correct behavior.
4. On Advanced Search in UI , fired search typename = hive_table
  a. In the 1st page , 1- 25 results were shown.
  b. On clicking next , in the 2nd page , 26 - 50 results were shown
  c. On clicking next , Expected to land in 3rd page with 51 - 75 results , but 
, 26-50 results were loaded again and the Next Button was disabled.

Calls made to the Atlas backend seem to be correct. On clicking "Next" each 
time , correct set of results were fetched. For example , call was made to 
fetch entities from offset 50 , limit = 25 , but the UI still showed 26-50 
results and disabled "Next" button.


Diffs
-

  dashboardv2/public/js/views/search/SearchResultLayoutView.js 970d6a3 


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


Testing
---

Tested with 200 data next and previous buttons is working as expected.


Thanks,

keval bhatt

[jira] [Updated] (ATLAS-2128) UI Regression : DSL Results pagination doesn't spawn more than 2 pages

2017-09-11 Thread Keval Bhatt (JIRA) 

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

Keval Bhatt updated ATLAS-2128:
---
Attachment: ATLAS-2128.patch

> UI Regression : DSL Results pagination doesn't spawn more than 2 pages
> --
>
> Key: ATLAS-2128
> URL: https://issues.apache.org/jira/browse/ATLAS-2128
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Blocker
> Attachments: ATLAS-2128.patch
>
>
> 1. Created 300 hive_tables.
> 2. On Basic Search in UI , fired search typename= hive_table
> 3. hive_table results were fetched across 12 pages - 25 entities in each page 
> - which is the correct behavior.
> 4.On Advanced Search in UI , fired search typename = hive_table
> *  In the 1st page , 1- 25 results were shown.
> *  On clicking next , in the 2nd page , 26 - 50 results were shown
> *  On  clicking next , Expected to land in 3rd page with 51 - 75 
> results , but , 26-50 results were loaded again and the Next Button was 
> disabled.
> Calls made to the Atlas backend seem to be correct. On clicking "Next" each 
> time , correct set of results were fetched. For example , call was made to 
> fetch entities from offset 50 , limit = 25 , but the UI still showed 26-50 
> results and disabled "Next" button.



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

[jira] [Updated] (ATLAS-2127) Import of an entity associated with a tag into backup cluster with updateTypeDefinition options set to false

2017-09-11 Thread Sharmadha Sainath (JIRA) 

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

Sharmadha Sainath updated ATLAS-2127:
-
Attachment: hdfs_path1.zip

[~ashutoshm] , Attached a zip file containing an hdfs_path attached to a tag 
tag1. 
Import_options.json :
{code}
{
"options":{
"updateTypeDefinition":false
}
}
{code}
Steps to reproduce :
Import the zip file into the cluster which doesn't have a tag named tag1 with 
import option updateTypeDefinition set to false.

> Import of an entity associated with a tag into backup cluster with 
> updateTypeDefinition options set to false
> 
>
> Key: ATLAS-2127
> URL: https://issues.apache.org/jira/browse/ATLAS-2127
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
> Attachments: hdfs_path1.zip, ImportExceptionWithTag.txt
>
>
> 1. On cluster1 , created an entity and associated it to a tag.
> 2. Exported the entity into a zipfile.
> 3. cluster2 is in clean state.(i.e no entity / tag is created)
> 4. Tried to import the entity zip into cluster2 with import option 
> "updateTypeDefinition" set to false.
> 5. Import failed with NPE. 
> Since updateTypeDefinition is set to false , NPE is thrown when the entity is 
> attempted to be associated to the tag in the backup cluster.
> This is the expected behavior , but the cause of the issue is not very 
> explicit to the end user when Atlas throws NPE.
> Attached the exception stack trace.



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

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

2017-09-11 Thread Apache Jenkins Server 
See 

--
[...truncated 454.36 KB...]
[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 [890 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.notification.NotificationEntityChangeListenerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.469 sec - in 
org.apache.atlas.notification.NotificationEntityChangeListenerTest
Running org.apache.atlas.notification.AdaptiveWaiterTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.144 sec - in 
org.apache.atlas.notification.AdaptiveWaiterTest
Running org.apache.atlas.notification.NotificationHookConsumerKafkaTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.58 sec - in 
org.apache.atlas.notification.NotificationHookConsumerKafkaTest
Running org.apache.atlas.notification.NotificationHookConsumerTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.642 sec - in 
org.apache.atlas.notification.NotificationHookConsumerTest
Running org.apache.atlas.util.RestUtilsTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.406 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.844 sec - in 
org.apache.atlas.web.setup.SetupStepsTest
Running org.apache.atlas.web.security.NegativeSSLAndKerberosTest
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 37.867 sec <<< 
FAILURE! - in org.apache.atlas.web.security.NegativeSSLAndKerberosTest
testUnsecuredClient(org.apache.atlas.web.security.NegativeSSLAndKerberosTest)  
Time elapsed: 0.385 sec  <<< FAILURE!
java.lang.AssertionError: expected: but was:
at org.testng.Assert.fail(Assert.java:89)
at org.testng.Assert.failNotEquals(Assert.java:489)
at org.testng.Assert.assertTrue(Assert.java:37)
at org.testng.Assert.assertTrue(Assert.java:47)
at 
org.apache.atlas.web.security.NegativeSSLAndKerberosTest.testUnsecuredClient(NegativeSSLAndKerberosTest.java:139)

Running org.apache.atlas.web.security.SSLAndKerberosTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 35.634 sec - in 
org.apache.atlas.web.security.SSLAndKerberosTest
Running org.apache.atlas.web.security.SSLTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.202 sec - in 
org.apache.atlas.web.security.SSLTest
Running org.apache.atlas.web.security.FileAuthenticationTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.392 sec - in 
org.apache.atlas.web.security.FileAuthenticationTest
Running org.apache.atlas.web.security.UserDaoTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.883 sec - in 
org.apache.atlas.web.security.UserDaoTest
Running org.apache.atlas.web.resources.AdminExportTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.334 sec - in 
org.apache.atlas.web.resources.AdminExportTest
Runn

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

2017-09-11 Thread Apache Jenkins Server 
See 


--
[...truncated 34.20 MB...]
2017-09-12 03:50:24,904 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo description (GraphToTypedInstanceMapper:144)
2017-09-12 03:50:24,905 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=description, dataType={name=string, description=null}, 
multiplicity={lower=0, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=false, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2662144] (GraphToTypedInstanceMapper:387)
2017-09-12 03:50:24,906 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.description from vertex[id=2662144 type=hive_table 
guid=5a9ffad1-2847-40f6-a9cb-d9b19534d540] (GraphHelper:433)
2017-09-12 03:50:24,907 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo owner (GraphToTypedInstanceMapper:144)
2017-09-12 03:50:24,907 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=owner, dataType={name=string, description=null}, 
multiplicity={lower=0, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=true, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2662144] (GraphToTypedInstanceMapper:387)
2017-09-12 03:50:24,908 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.owner from vertex[id=2662144 type=hive_table 
guid=5a9ffad1-2847-40f6-a9cb-d9b19534d540] (GraphHelper:433)
2017-09-12 03:50:24,910 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.owner from vertex[id=2662144 type=hive_table 
guid=5a9ffad1-2847-40f6-a9cb-d9b19534d540] (GraphHelper:433)
2017-09-12 03:50:24,911 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[47ac4048-c3c1-41c0-8551-4be08db9f42d] 
(GraphBackedMetadataRepository:179)
2017-09-12 03:50:24,911 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[0f34007b-aea8-4d9d-9f97-9abcd617e72f] 
(GraphBackedMetadataRepository:179)
2017-09-12 03:50:24,911 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[0f695fe5-c4c0-4d56-bacb-19ee5be1b9e8] 
(GraphBackedMetadataRepository:179)
2017-09-12 03:50:24,911 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[509fb7c3-7238-42bc-b505-33ff3b8e2c49] 
(GraphBackedMetadataRepository:179)
2017-09-12 03:50:24,946 DEBUG - [NotificationHookConsumer thread-0:] ~ Sending 
message for topic ATLAS_ENTITIES: 
{"version":{"version":"1.0.0"},"message":{"entity":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"5a9ffad1-2847-40f6-a9cb-d9b19534d540","version":0,"typeName":"hive_table","state":"ACTIVE"},"typeName":"hive_table","values":{"tableType":"MANAGED_TABLE","name":"table6yrtaynnqz","createTime":"2017-09-12T03:48:55.000Z","temporary":false,"db":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"1a593e90-ae2e-4ec5-a72e-c7b85afb3639","version":0,"typeName":"hive_db","state":"ACTIVE"},"retention":0,"qualifiedName":"default.table6yrtaynnqz@primary","columns":[{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"47ac4048-c3c1-41c0-8551-4be08db9f42d","version":0,"typeName":"hive_column","state":"ACTIVE"},"typeName":"hive_column","values":{"name":"id","qualifiedName":"default.table6yrtaynnqz.id@primary","position":0,"owner":"jenkins","type":"int","table":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"5a9ffad1-2847-40f6-a9cb-d9b19534d540","version":0,"typeName":"hive_table","state":"ACTIVE"}},"traitNames":[],"traits":{},"systemAttributes":{"createdBy":"jenkins","modifiedBy":"jenkins","createdTime":"2017-09-12T03:50:23.559Z","modifiedTime":"2017-09-12T03:50:23.559Z"}},{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"0f34007b-aea8-4d9d-9f97-9abcd617e72f","version":0,"typeName":"hive_column","state":"ACTIVE"},"typeName":"hive_column","values":{"name":"name","qualifiedName":"default.table6yrtaynnqz.name@primary","position":1,"owner":"jenkins","type":"string","table":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"5a9ffad1-2847-40f6-a9cb-d9b19534d540","version":0,"typeName":"hive_table","state":"ACTIVE"}},"traitNames":[],"traits":{},"systemAttributes":{"createdBy":"jenkins","modifiedBy":"jenkins","createdTime":"2017-09-12T03:50:23.559Z","modifiedTime":"2017-09-12T03:50:23.559Z"}}],"comment":"table
 
comment","lastAccessTime":"2017-09-12T03:48:55.000Z","owner":"jenkins","sd":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass"

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

2017-09-11 Thread Apache Jenkins Server 
See 


--
[...truncated 442.61 KB...]
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/pci HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/sox HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/sec HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/finance HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/FactOomKrmtELZ HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/ETLafttFjZc15 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/DimensionHDPsqqEZi3 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/MetricXsNxqD5JFD HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/hive_db_v1 HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/hive_column_v1 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/hive_table_v1 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/hive_process_v1 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "POST /api/atlas/types HTTP/1.1" 400 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/tableType HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/serdeType HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/classification HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/pii HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/phi HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/pci HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/sox HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:39:59 +] "GET 
/api/atlas/v2/types/typedef/name/sec HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "GET 
/api/atlas/v2/types/typedef/name/finance HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "GET 
/api/atlas/v2/types/typedef/name/FactJI9ejMDwSp HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "GET 
/api/atlas/v2/types/typedef/name/ETLa7FPFqqZCC HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "GET 
/api/atlas/v2/types/typedef/name/DimensionmL6uGzek1B HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "GET 
/api/atlas/v2/types/typedef/name/MetricUvcNxNaFg9 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "GET 
/api/atlas/v2/types/typedef/name/hive_db_v1 HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "GET 
/api/atlas/v2/types/typedef/name/hive_column_v1 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "GET 
/api/atlas/v2/types/typedef/name/hive_table_v1 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "GET 
/api/atlas/v2/types/typedef/name/hive_process_v1 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "POST /api/atlas/types HTTP/1.1" 400 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "POST /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "POST /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 409 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "GET 
/api/atlas/v2/types/enumdef/name/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "GET 
/api/atlas/v2/types/enumdef/guid/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "GET 
/api/atlas/v2/types/structdef/name/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "GET 
/api/atlas/v2/types/structdef/guid/blah HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [12/Sep/2017:03:40:00 +] "GET 
/api/atlas/v2/types/classificationdef/name/blah HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.

[jira] [Assigned] (ATLAS-2129) Atlas shutdown during progress of bulk import throws ConcurrentModificationException

2017-09-11 Thread Ashutosh Mestry (JIRA) 

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

Ashutosh Mestry reassigned ATLAS-2129:
--

Assignee: Ashutosh Mestry

> Atlas shutdown during progress of bulk import throws 
> ConcurrentModificationException
> 
>
> Key: ATLAS-2129
> URL: https://issues.apache.org/jira/browse/ATLAS-2129
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
>Priority: Blocker
>
> 1. Exported an hive_db containing 300 hive_table entities from cluster1 into 
> a zip file .
> 2. Tried to import into cluster2.
> 3. When the import was in progress ( at 34%) , stopped Atlas.
> 4. Following exception was seen in application logs of cluster2 :
> {code}
> 2017-09-11 10:17:09,192 INFO  - [pool-2-thread-9 - 
> 83fe24a2-ff2b-4add-a94e-a54b09090912:] ~ bulkImport(): progress: 34% (of 301) 
> - 
> entity:last-imported:hive_table:[102]:(2d629a8e-5c94-40e8-b83f-8a9c91c6de8d) 
> (AtlasEntityStoreV1:238)
> 2017-09-11 10:17:09,340 ERROR - [SIGTERM handler:] ~ Could not commit 
> transaction [1] due to exception (StandardTitanGraph:731)
> java.util.ConcurrentModificationException
>   at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901)
>   at java.util.ArrayList$Itr.next(ArrayList.java:851)
>   at 
> atlas.shaded.titan.guava.common.collect.Iterators$7.computeNext(Iterators.java:701)
>   at 
> atlas.shaded.titan.guava.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
>   at 
> atlas.shaded.titan.guava.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
>   at 
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.prepareCommit(StandardTitanGraph.java:473)
>   at 
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.commit(StandardTitanGraph.java:654)
>   at 
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1337)
>   at 
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.shutdown(TitanBlueprintsGraph.java:120)
>   at 
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.shutdownInternal(StandardTitanGraph.java:171)
>   at 
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.access$700(StandardTitanGraph.java:75)
>   at 
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph$ShutdownThread.start(StandardTitanGraph.java:756)
>   at 
> java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:102)
>   at 
> java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:46)
>   at java.lang.Shutdown.runHooks(Shutdown.java:123)
>   at java.lang.Shutdown.sequence(Shutdown.java:167)
>   at java.lang.Shutdown.exit(Shutdown.java:212)
>   at java.lang.Terminator$1.handle(Terminator.java:52)
>   at sun.misc.Signal$1.run(Signal.java:212)
>   at java.lang.Thread.run(Thread.java:748)
> {code}
> Other operations that are called during Atlas shut down such as Shutdown hook 
> , Stopping KafkaNotification service , NotificationHookConsumer , 
> HBaseBasedAuditRepository are not called.
> 5.After that , restarted Atlas.  Atlas functioned properly.
> 6.Resumed import with import option , startGuid=  %. Atlas was stopped when Import was going on at 34% >
> 7. Import completed successfully.
> 8.Post import, only entities from 33% to 100% were imported . Initial 32% of 
> the entities were not imported.
> 9.Fired an import command again without any interruption and without 
> specifying the startGUID. All 300 hive_table entities and 1 hive_db were 
> imported successfully.



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

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

2017-09-11 Thread Apache Jenkins Server 
See

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

2017-09-11 Thread Apache Jenkins Server 
See 


Changes:

[madhan] ATLAS-1218: Atlas says it is started but does not accept REST requests

[madhan] ATLAS-2071 : UI : Minification of atlas code (js,css)

[madhan] ATLAS-2060: Fix logger class name typos

[madhan] ATLAS-2085: HA initialization fix

[madhan] ATLAS-2083: Refactor AtlasDefStore classes to reduce code

--
[...truncated 29.90 MB...]
2017-09-11 21:59:41,562 DEBUG - [NotificationHookConsumer thread-0:] ~ Found 
null (GraphHelper:366)
2017-09-11 21:59:41,563 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo qualifiedName (GraphToTypedInstanceMapper:144)
2017-09-11 21:59:41,563 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=qualifiedName, dataType={name=string, description=null}, 
multiplicity={lower=1, upper=1, isUnique=false}, isComposite=false, 
isUnique=true, isIndexable=true, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2661376] (GraphToTypedInstanceMapper:387)
2017-09-11 21:59:41,564 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Referenceable.qualifiedName from vertex[id=2661376 type=hdfs_path 
guid=8f39759b-b6e9-40de-91ca-c6bf6c4cdc1d] (GraphHelper:433)
2017-09-11 21:59:41,566 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Referenceable.qualifiedName from vertex[id=2661376 type=hdfs_path 
guid=8f39759b-b6e9-40de-91ca-c6bf6c4cdc1d] (GraphHelper:433)
2017-09-11 21:59:41,567 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo name (GraphToTypedInstanceMapper:144)
2017-09-11 21:59:41,567 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=name, dataType={name=string, description=null}, 
multiplicity={lower=1, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=true, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2661376] (GraphToTypedInstanceMapper:387)
2017-09-11 21:59:41,568 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.name from vertex[id=2661376 type=hdfs_path 
guid=8f39759b-b6e9-40de-91ca-c6bf6c4cdc1d] (GraphHelper:433)
2017-09-11 21:59:41,570 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.name from vertex[id=2661376 type=hdfs_path 
guid=8f39759b-b6e9-40de-91ca-c6bf6c4cdc1d] (GraphHelper:433)
2017-09-11 21:59:41,571 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo description (GraphToTypedInstanceMapper:144)
2017-09-11 21:59:41,571 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=description, dataType={name=string, description=null}, 
multiplicity={lower=0, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=false, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2661376] (GraphToTypedInstanceMapper:387)
2017-09-11 21:59:41,572 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.description from vertex[id=2661376 type=hdfs_path 
guid=8f39759b-b6e9-40de-91ca-c6bf6c4cdc1d] (GraphHelper:433)
2017-09-11 21:59:41,573 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo owner (GraphToTypedInstanceMapper:144)
2017-09-11 21:59:41,573 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=owner, dataType={name=string, description=null}, 
multiplicity={lower=0, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=true, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2661376] (GraphToTypedInstanceMapper:387)
2017-09-11 21:59:41,574 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.owner from vertex[id=2661376 type=hdfs_path 
guid=8f39759b-b6e9-40de-91ca-c6bf6c4cdc1d] (GraphHelper:433)
2017-09-11 21:59:41,597 DEBUG - [NotificationHookConsumer thread-0:] ~ Sending 
message for topic ATLAS_ENTITIES: 
{"version":{"version":"1.0.0"},"message":{"entity":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"a3b8cd2c-7309-4f5a-8ee9-5c124d92e9c8","version":0,"typeName":"hive_process","state":"ACTIVE"},"typeName":"hive_process","values":{"queryId":"jenkins_20170911215745_46ed04ad-4ae1-49e0-92bc-38081457e0fa","name":"create
  external table tablegi1tx4b1fj(id int, name string) comment \u0027table 
comment\u0027  partitioned by(dt string) location 
\u0027pfile:///home/jenkins/jenkins-slave/workspace/atlas-0.8-integrationtests/addons/hive-bridge/./target/sometestpath-data-sszrbdrluj\u0027","startTime":"2017-09-11T21:57:45.456Z","queryPlan":"Not
 
Supported","operationType":"CREATETABLE","outputs":[{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"5c9d8f09-97c4-4026-abcd-fc6ad119dbdd","version":0,"typeName":"DataSet","state":"ACTIVE"}],"endTime":"2017-09-11T21:57:45.612Z","recentQueries":["create
  external table tablegi1tx4b1fj(id int, name string) comment \u0

Re: Review Request 62129: ATLAS-2117: Basic search issues due to Titan Solr schema

2017-09-11 Thread Apoorv Naik 

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

(Updated Sept. 11, 2017, 9:48 p.m.)


Review request for atlas and Madhan Neethiraj.


Changes
---

Added dependency on other another review, for the IN predicate changes.


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


Repository: atlas


Description
---

See JIRA


Diffs
-

  
repository/src/main/java/org/apache/atlas/discovery/ClassificationSearchProcessor.java
 0daab030 
  repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
d5e39236 
  repository/src/main/java/org/apache/atlas/util/SearchPredicateUtil.java 
fc973e6f 


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


Testing
---

UI and REST calls working as expected now.


Thanks,

Apoorv Naik

[jira] [Updated] (ATLAS-1805) Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to Atlas

2017-09-11 Thread Ramesh Mani (JIRA) 

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

Ramesh Mani updated ATLAS-1805:
---
Attachment: 
0001-ATLAS-1805-Provide-an-Atlas-hook-to-send-Hbase-Names_003.patch

> Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to 
> Atlas
> ---
>
> Key: ATLAS-1805
> URL: https://issues.apache.org/jira/browse/ATLAS-1805
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
> Attachments: 
> 0001-ATLAS-1805-Provide-an-Atlas-hook-to-send-Hbase-Names_002.patch, 
> 0001-ATLAS-1805-Provide-an-Atlas-hook-to-send-Hbase-Names_003.patch, 
> 0001-ATLAS-1805-Provide-an-Atlas-hook-to-send-Hbase-Names.patch
>
>
> Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to 
> Atlas



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

Re: Review Request 59821: ATLAS-1805:Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to Atlas

2017-09-11 Thread Ramesh Mani 

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

(Updated Sept. 11, 2017, 9:43 p.m.)


Review request for atlas and Madhan Neethiraj.


Changes
---

Fixed review comments


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


Repository: atlas


Description
---

ATLAS-1805: Provide an Atlas hook to send Hbase Namespace/Table/column family 
metadata to Atlas


Diffs (updated)
-

  addons/hbase-bridge-shim/pom.xml PRE-CREATION 
  
addons/hbase-bridge-shim/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessor.java
 PRE-CREATION 
  addons/hbase-bridge/pom.xml PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessor.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessorBase.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/model/HBaseDataTypes.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/model/HBaseOperationContext.java
 PRE-CREATION 
  addons/hbase-bridge/src/main/resources/atlas-hbase-import-log4j.xml 
PRE-CREATION 
  
addons/hbase-bridge/src/test/java/org/apache/atlas/hbase/HBaseAtlasHookTest.java
 PRE-CREATION 
  addons/models/1060-hbase_model.json 3e46e06 
  addons/models/patches/001-hbase_table_column_family_add_attribute.json 
PRE-CREATION 
  distro/src/main/assemblies/standalone-package.xml 215cb23 
  pom.xml 157122a 


Diff: https://reviews.apache.org/r/59821/diff/5/

Changes: https://reviews.apache.org/r/59821/diff/4-5/


Testing
---

* Review comments fixed with 2 exceptions whcih I have commented on 
* Added an IT test
* Testing done in LOCAL VM


Thanks,

Ramesh Mani

[jira] [Updated] (ATLAS-2083) Refactor AtlasDefStore classes to reduce code duplication

2017-09-11 Thread Madhan Neethiraj (JIRA) 

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

Madhan Neethiraj updated ATLAS-2083:

Fix Version/s: 0.8.2

Committed to branch-0.8: 
http://git-wip-us.apache.org/repos/asf/atlas/commit/5ca7955a

> Refactor AtlasDefStore classes to reduce code duplication
> ---
>
> Key: ATLAS-2083
> URL: https://issues.apache.org/jira/browse/ATLAS-2083
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Richard Ding
>Assignee: Richard Ding
> Fix For: 0.9-incubating, 0.8.2
>
> Attachments: ATLAS-2083_1.patch, ATLAS-2083.patch
>
>
> Currently each top-level TypeDef defines its own DefStore interface. These 
> interfaces have the same methods.  I suggest that we use generic interface to 
> reduce the code duplication.
> We can also tighten the type restriction on these interfaces. Replacing 
> Object reference with AtlasVertex reference.



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

Re: Review Request 62110: ATLAS-2115: Fix Regression on Basic search

2017-09-11 Thread Apoorv Naik 

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

(Updated Sept. 11, 2017, 9:40 p.m.)


Review request for atlas and Madhan Neethiraj.


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


Repository: atlas


Description
---

ATLAS-1880 introduced regression in call timings for the basic search GET 
implementation


Diffs (updated)
-

  
repository/src/main/java/org/apache/atlas/discovery/ClassificationSearchProcessor.java
 0daab030 
  
repository/src/main/java/org/apache/atlas/discovery/EntitySearchProcessor.java 
a4a638af 
  repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
d5e39236 
  repository/src/main/java/org/apache/atlas/util/SearchPredicateUtil.java 
fc973e6f 


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

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


Testing
---

Tested via scripts and network call timing in Chrome/Firefox.


Thanks,

Apoorv Naik

[jira] [Updated] (ATLAS-2060) Fix logger class name typos

2017-09-11 Thread Madhan Neethiraj (JIRA) 

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

Madhan Neethiraj updated ATLAS-2060:

Fix Version/s: 0.8.2

Committed to branch-0.8: 
http://git-wip-us.apache.org/repos/asf/atlas/commit/16a02fc7

> Fix logger class name typos
> ---
>
> Key: ATLAS-2060
> URL: https://issues.apache.org/jira/browse/ATLAS-2060
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 0.8-incubating
>Reporter: Richard Ding
>Assignee: Richard Ding
>Priority: Trivial
> Fix For: 0.9-incubating, 0.8.2
>
> Attachments: ATLAS-2060.patch
>
>
> There are two classes in intg module that have incorrect logger class names.



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

[jira] [Updated] (ATLAS-2071) UI : Minification of atlas code (js,css)

2017-09-11 Thread Madhan Neethiraj (JIRA) 

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

Madhan Neethiraj updated ATLAS-2071:

Fix Version/s: 0.8.2

Committed to branch-0.8: 
http://git-wip-us.apache.org/repos/asf/atlas/commit/565213d4

> UI : Minification of atlas code (js,css)
> 
>
> Key: ATLAS-2071
> URL: https://issues.apache.org/jira/browse/ATLAS-2071
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.9-incubating, 0.8.2
>
> Attachments: ATLAS-2071.patch
>
>




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

[jira] [Updated] (ATLAS-1218) Atlas says it is started but does not accept REST requests

2017-09-11 Thread Madhan Neethiraj (JIRA) 

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

Madhan Neethiraj updated ATLAS-1218:

Fix Version/s: 0.8.2

Committed to branch-0.8: 
http://git-wip-us.apache.org/repos/asf/atlas/commit/97ce63ec

> Atlas says it is started but does not accept REST requests
> --
>
> Key: ATLAS-1218
> URL: https://issues.apache.org/jira/browse/ATLAS-1218
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: David Radley
>Assignee: Richard Ding
> Fix For: 0.9-incubating, 0.8.2
>
> Attachments: ATLAS-1218_1.patch, ATLAS-1218_2.patch, ATLAS-1218.patch
>
>
> I start Atlas on the command line and it tells me is started - but REST 
> requests are not accepted immediately. There appears to be asynchronous 
> background processes that have not yet initialized. I feel that when Atlas 
> says it is started it should be open for business and accept REST requests.  
> a few seconds later REST requests are accepted. 



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

Review Request 62227: ATLAS-2120: Import API: Type Attribute Type Definition Matched

2017-09-11 Thread Ashutosh Mestry 

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

Review request for atlas, Madhan Neethiraj and Sharmadha Sainath.


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


Repository: atlas


Description
---

This is a minor change, that performs additional check during import process. 

Import process now matches type definition for the types being imported. It 
fails and logs exception if types do not match.


Diffs
-

  docs/src/site/twiki/Import-API-Options.twiki cc09fc7 
  
repository/src/main/java/org/apache/atlas/repository/impexp/TypeAttributeDifference.java
 68bc583 
  
repository/src/test/java/org/apache/atlas/repository/impexp/ImportServiceTest.java
 42f7011 
  
repository/src/test/java/org/apache/atlas/repository/impexp/ZipFileResourceTestUtils.java
 d80fab0 
  repository/src/test/resources/hdfs_path1.zip PRE-CREATION 
  repository/src/test/resources/tag1.json PRE-CREATION 


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


Testing
---

**Unit tests**
- Additional failure unit tests added.

**Functional tests**
- Executed success and failure scenarios.


Thanks,

Ashutosh Mestry

[jira] [Updated] (ATLAS-2120) Inconsistency in Importing already existing types on backup cluster with new definition.

2017-09-11 Thread Ashutosh Mestry (JIRA) 

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

Ashutosh Mestry updated ATLAS-2120:
---
Attachment: ATLAS-2120-Import-Failure-Test.patch

> Inconsistency in Importing already existing types on backup cluster with new 
> definition.
> 
>
> Key: ATLAS-2120
> URL: https://issues.apache.org/jira/browse/ATLAS-2120
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
>Priority: Critical
> Attachments: ATLAS-2120-Import-Failure-Test.patch, 
> ATLAS-2120-Import-Failure-Test.patch, hdfs_path1.zip
>
>
> 1.Created a tag tag1 on cluster1 with attributes : 
> * attrib1 : string
> * attrib2 : integer
> 2.Created a tag with same name on cluster2 with attributes:
> *attrib1: date
> *attrib3: integer
> (Note the tag names are same , and attrib1 is same but datatypes of attrib1 
> are different in both the clusters)
> 3. On cluster1 , created an entity and associated the tag1 to the entity with 
> attribute values
> *attrib1: "randstr"
> *attrib2: 5
>   and exported the entity into zip file .
> 4.Tried to import the entity into cluster2. 
> Import failed with 500 Internal server error and with following exception :
> {code}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
>  org.apache.atlas.repository.graphdb.AtlasSchemaViolationException: 
> com.thinkaurelius.titan.core.SchemaViolationException: Value [rand_str] is 
> not an instance of the expected data type for property key [tag1.attrib1] and 
> cannot be converted. Expected: class java.lang.Long, found: class 
> java.lang.String"}
> {code}
> Following is the inconsistency observed :
> Entity is not imported into the cluster2 , but the type definition of tag1 in 
> cluster2 had 3 attributes now (attrib1 : date , attrib2:Integer , 
> attrib3:Integer) and 500 Internal server error is thrown.
> Normally, when a datatype of an attribute is attempted to be updated , Atlas 
> throws the following exception and the type is not updated.
> {code}
> {"errorCode":"ATLAS-400-00-029","errorMessage":"Data type update for 
> attribute is not supported"}
> {code}
> Expected the same to happen while importing (i.e) Import failing with Bad 
> request with the proper error message.



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

[jira] [Commented] (ATLAS-2120) Inconsistency in Importing already existing types on backup cluster with new definition.

2017-09-11 Thread Ashutosh Mestry (JIRA) 

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

Ashutosh Mestry commented on ATLAS-2120:


[~ssainath] We have decided to address this by checking attribute type of 
attributes that exist. If attribute exists and its type differ, we throw an 
exception. I will update documentation with this.

> Inconsistency in Importing already existing types on backup cluster with new 
> definition.
> 
>
> Key: ATLAS-2120
> URL: https://issues.apache.org/jira/browse/ATLAS-2120
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
>Priority: Critical
> Attachments: ATLAS-2120-Import-Failure-Test.patch, hdfs_path1.zip
>
>
> 1.Created a tag tag1 on cluster1 with attributes : 
> * attrib1 : string
> * attrib2 : integer
> 2.Created a tag with same name on cluster2 with attributes:
> *attrib1: date
> *attrib3: integer
> (Note the tag names are same , and attrib1 is same but datatypes of attrib1 
> are different in both the clusters)
> 3. On cluster1 , created an entity and associated the tag1 to the entity with 
> attribute values
> *attrib1: "randstr"
> *attrib2: 5
>   and exported the entity into zip file .
> 4.Tried to import the entity into cluster2. 
> Import failed with 500 Internal server error and with following exception :
> {code}
> {"errorCode":"ATLAS-500-00-001","errorMessage":"org.apache.atlas.exception.AtlasBaseException:
>  org.apache.atlas.repository.graphdb.AtlasSchemaViolationException: 
> com.thinkaurelius.titan.core.SchemaViolationException: Value [rand_str] is 
> not an instance of the expected data type for property key [tag1.attrib1] and 
> cannot be converted. Expected: class java.lang.Long, found: class 
> java.lang.String"}
> {code}
> Following is the inconsistency observed :
> Entity is not imported into the cluster2 , but the type definition of tag1 in 
> cluster2 had 3 attributes now (attrib1 : date , attrib2:Integer , 
> attrib3:Integer) and 500 Internal server error is thrown.
> Normally, when a datatype of an attribute is attempted to be updated , Atlas 
> throws the following exception and the type is not updated.
> {code}
> {"errorCode":"ATLAS-400-00-029","errorMessage":"Data type update for 
> attribute is not supported"}
> {code}
> Expected the same to happen while importing (i.e) Import failing with Bad 
> request with the proper error message.



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

[jira] [Commented] (ATLAS-2063) Compressed HiveHook Messages

2017-09-11 Thread Ashutosh Mestry (JIRA) 

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

Ashutosh Mestry commented on ATLAS-2063:


Duplicate of: [ATLAS-204|https://issues.apache.org/jira/browse/ATLAS-2064]

> Compressed HiveHook Messages
> 
>
> Key: ATLAS-2063
> URL: https://issues.apache.org/jira/browse/ATLAS-2063
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
> Fix For: trunk
>
>
> *Background*
> Messages posted by hooks to Atlas Kafka topics are JSON format. 
> Kafka imposes a 1MB limit on the message size.
> Occasionally, depending on operations performed, this threshold is reached. 
> This results in messages being dropped.
> The entities are thus not reflected in Atlas.
> *Solution*
> Applying compression to these message will alleviate the problem.



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

[jira] [Commented] (ATLAS-2127) Import of an entity associated with a tag into backup cluster with updateTypeDefinition options set to false

2017-09-11 Thread Ashutosh Mestry (JIRA) 

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

Ashutosh Mestry commented on ATLAS-2127:


[~ssainath] Can you please attach the ZIP file. It will help me.

> Import of an entity associated with a tag into backup cluster with 
> updateTypeDefinition options set to false
> 
>
> Key: ATLAS-2127
> URL: https://issues.apache.org/jira/browse/ATLAS-2127
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
> Attachments: ImportExceptionWithTag.txt
>
>
> 1. On cluster1 , created an entity and associated it to a tag.
> 2. Exported the entity into a zipfile.
> 3. cluster2 is in clean state.(i.e no entity / tag is created)
> 4. Tried to import the entity zip into cluster2 with import option 
> "updateTypeDefinition" set to false.
> 5. Import failed with NPE. 
> Since updateTypeDefinition is set to false , NPE is thrown when the entity is 
> attempted to be associated to the tag in the backup cluster.
> This is the expected behavior , but the cause of the issue is not very 
> explicit to the end user when Atlas throws NPE.
> Attached the exception stack trace.



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

[jira] [Assigned] (ATLAS-2127) Import of an entity associated with a tag into backup cluster with updateTypeDefinition options set to false

2017-09-11 Thread Ashutosh Mestry (JIRA) 

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

Ashutosh Mestry reassigned ATLAS-2127:
--

Assignee: Ashutosh Mestry

> Import of an entity associated with a tag into backup cluster with 
> updateTypeDefinition options set to false
> 
>
> Key: ATLAS-2127
> URL: https://issues.apache.org/jira/browse/ATLAS-2127
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Ashutosh Mestry
> Attachments: ImportExceptionWithTag.txt
>
>
> 1. On cluster1 , created an entity and associated it to a tag.
> 2. Exported the entity into a zipfile.
> 3. cluster2 is in clean state.(i.e no entity / tag is created)
> 4. Tried to import the entity zip into cluster2 with import option 
> "updateTypeDefinition" set to false.
> 5. Import failed with NPE. 
> Since updateTypeDefinition is set to false , NPE is thrown when the entity is 
> attempted to be associated to the tag in the backup cluster.
> This is the expected behavior , but the cause of the issue is not very 
> explicit to the end user when Atlas throws NPE.
> Attached the exception stack trace.



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

[jira] [Commented] (ATLAS-2109) Create basic IGC OMRS Connector for existing releases

2017-09-11 Thread CASSIO DOS SANTOS (JIRA) 

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

CASSIO DOS SANTOS commented on ATLAS-2109:
--

[~mandy_chessell] Does the scope of the basic connector include support for 
synchronization in both directions, between Atlas and IGC, for all the asset 
types supported by the current IGC server (release 11.5)? Or should this be 
split into 2 sub-tasks, one for the Atlas-to-IGC and another for IGC-to-Atlas 
direction? 

> Create basic IGC OMRS Connector for existing releases
> -
>
> Key: ATLAS-2109
> URL: https://issues.apache.org/jira/browse/ATLAS-2109
> Project: Atlas
>  Issue Type: Sub-task
>  Components:  atlas-core
>Reporter: Mandy Chessell
>
> This is the first version of the IGC OMRS Connector that works with existing 
> IGC servers.



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

Re: Review Request 59821: ATLAS-1805:Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to Atlas

2017-09-11 Thread Madhan Neethiraj 

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




addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
Lines 76 (patched)


Looks like constants in line #76 - #87 are for attribute names. It will be 
helpful to prefix these names with "ATTR_". Perhaps line #74 as well.



addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
Lines 132 (patched)


It will be useful to print exception as well:
  LOG.info("Interrupt received in shutdown.", ie);



addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
Lines 148 (patched)


"try {" at line #148 can move inside 'if' block at line #149.



addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
Lines 183 (patched)


'operation' is already part of 'hbaseOperationContext'. It will be good to 
not pass this as a separate argument. Same for line #190 and #197 as well.



addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
Lines 205 (patched)


nameSpaceRef is sent as null from the caller at line #183. It this argument 
is not necessary, please remove.



addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
Lines 272 (patched)


- namespaceReference and tableReference are sent as null from the caller at 
line #190. It these arguments are not necessary, please remove.
- this method doesn't seem to be used outside this class. In that case, 
consider marking this a private method.



addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
Lines 332 (patched)


- this method doesn't seem to be used outside this class. In that case, 
consider marking this a private method.



addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
Lines 350 (patched)


- namespaceReference and tableReference are sent as null from the caller at 
line #197. It these arguments are not necessary, please remove.
- this method doesn't seem to be used outside this class. In that case, 
consider marking this a private method.



addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
Lines 435 (patched)


to be consistent, avoid space after "(".

Also, I see other places that miss a space after a ",". Please review and 
add a space after a ",".



addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
Lines 854 (patched)


'user' could be null - from line #838. Please update here to handle this 
case.


- Madhan Neethiraj


On Sept. 10, 2017, 7:04 a.m., Ramesh Mani wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/59821/
> ---
> 
> (Updated Sept. 10, 2017, 7:04 a.m.)
> 
> 
> Review request for atlas and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-1805
> https://issues.apache.org/jira/browse/ATLAS-1805
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-1805: Provide an Atlas hook to send Hbase Namespace/Table/column family 
> metadata to Atlas
> 
> 
> Diffs
> -
> 
>   addons/hbase-bridge-shim/pom.xml PRE-CREATION 
>   
> addons/hbase-bridge-shim/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessor.java
>  PRE-CREATION 
>   addons/hbase-bridge/pom.xml PRE-CREATION 
>   
> addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
>  PRE-CREATION 
>   
> addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessor.java
>  PRE-CREATION 
>   
> addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessorBase.java
>  PRE-CREATION 
>   
> addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/model/HBaseDataTypes.java
>  PRE-CREATION 
>   
> addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/model/HBaseOperationContext.java
>  PRE-CREATION 
>   addons/hbase-bridge/src/main/resources/atlas-hbase-import-log4j.xml 
> PRE-CREATION 
>   
> addons/hbase-bridge/src/test/java/org/apache/atlas/hbase/HBaseAtlasHookTest.java
>  PRE-CREATION 
>   addons/models/1060-hbase_model.json 3e46e06 
>   addons/models/patch

[jira] [Resolved] (ATLAS-2113) [Regression] Basic search

2017-09-11 Thread Apoorv Naik (JIRA) 

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

Apoorv Naik resolved ATLAS-2113.

Resolution: Duplicate

> [Regression] Basic search
> -
>
> Key: ATLAS-2113
> URL: https://issues.apache.org/jira/browse/ATLAS-2113
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
> Fix For: 0.9-incubating
>
>
> The REST call timings for the use-case when only classification is specified 
> have regressed after introduction of ATLAS-1880. This JIRA will track all 
> such use-cases and provide a code fix (if possible)



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

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

2017-09-11 Thread Apoorv Naik (JIRA) 

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

Apoorv Naik resolved ATLAS-1994.

Resolution: Fixed

> 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: Improvement
>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] [Resolved] (ATLAS-2001) Invalid attribute during entity update should throw 400

2017-09-11 Thread Apoorv Naik (JIRA) 

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

Apoorv Naik resolved ATLAS-2001.

Resolution: Not A Bug

> Invalid attribute during entity update should throw 400
> ---
>
> Key: ATLAS-2001
> URL: https://issues.apache.org/jira/browse/ATLAS-2001
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk, 0.8-incubating
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
> Fix For: trunk, 0.8-incubating
>
> Attachments: 
> 0001-ATLAS-2001-Invalid-attribute-during-entity-update-sh.patch
>
>
> Current implementation just ignores the invalid attributes and proceeds. Fix 
> is to throw a bad request exception from the store.



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

[jira] [Assigned] (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-11 Thread Apoorv Naik (JIRA) 

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

Apoorv Naik reassigned ATLAS-2028:
--

Assignee: Apoorv Naik

> 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: Bug
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>
> 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] [Created] (ATLAS-2129) Atlas shutdown during progress of bulk import throws ConcurrentModificationException

2017-09-11 Thread Sharmadha Sainath (JIRA) 
Sharmadha Sainath created ATLAS-2129:


 Summary: Atlas shutdown during progress of bulk import throws 
ConcurrentModificationException
 Key: ATLAS-2129
 URL: https://issues.apache.org/jira/browse/ATLAS-2129
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Priority: Blocker


1. Exported an hive_db containing 300 hive_table entities from cluster1 into a 
zip file .
2. Tried to import into cluster2.
3. When the import was in progress ( at 34%) , stopped Atlas.
4. Following exception was seen in application logs of cluster2 :
{code}
2017-09-11 10:17:09,192 INFO  - [pool-2-thread-9 - 
83fe24a2-ff2b-4add-a94e-a54b09090912:] ~ bulkImport(): progress: 34% (of 301) - 
entity:last-imported:hive_table:[102]:(2d629a8e-5c94-40e8-b83f-8a9c91c6de8d) 
(AtlasEntityStoreV1:238)
2017-09-11 10:17:09,340 ERROR - [SIGTERM handler:] ~ Could not commit 
transaction [1] due to exception (StandardTitanGraph:731)
java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901)
at java.util.ArrayList$Itr.next(ArrayList.java:851)
at 
atlas.shaded.titan.guava.common.collect.Iterators$7.computeNext(Iterators.java:701)
at 
atlas.shaded.titan.guava.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
at 
atlas.shaded.titan.guava.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
at 
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.prepareCommit(StandardTitanGraph.java:473)
at 
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.commit(StandardTitanGraph.java:654)
at 
com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1337)
at 
com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.shutdown(TitanBlueprintsGraph.java:120)
at 
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.shutdownInternal(StandardTitanGraph.java:171)
at 
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.access$700(StandardTitanGraph.java:75)
at 
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph$ShutdownThread.start(StandardTitanGraph.java:756)
at 
java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:102)
at 
java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:46)
at java.lang.Shutdown.runHooks(Shutdown.java:123)
at java.lang.Shutdown.sequence(Shutdown.java:167)
at java.lang.Shutdown.exit(Shutdown.java:212)
at java.lang.Terminator$1.handle(Terminator.java:52)
at sun.misc.Signal$1.run(Signal.java:212)
at java.lang.Thread.run(Thread.java:748)
{code}

Other operations that are called during Atlas shut down such as Shutdown hook , 
Stopping KafkaNotification service , NotificationHookConsumer , 
HBaseBasedAuditRepository are not called.

5.After that , restarted Atlas.  Atlas functioned properly.
6.Resumed import with import option , startGuid= 
7. Import completed successfully.
8.Post import, only entities from 33% to 100% were imported . Initial 32% of 
the entities were not imported.
9.Fired an import command again without any interruption and without specifying 
the startGUID. All 300 hive_table entities and 1 hive_db were imported 
successfully.




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

[jira] [Assigned] (ATLAS-2128) UI Regression : DSL Results pagination doesn't spawn more than 2 pages

2017-09-11 Thread Keval Bhatt (JIRA) 

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

Keval Bhatt reassigned ATLAS-2128:
--

Assignee: Keval Bhatt

> UI Regression : DSL Results pagination doesn't spawn more than 2 pages
> --
>
> Key: ATLAS-2128
> URL: https://issues.apache.org/jira/browse/ATLAS-2128
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Blocker
>
> 1. Created 300 hive_tables.
> 2. On Basic Search in UI , fired search typename= hive_table
> 3. hive_table results were fetched across 12 pages - 25 entities in each page 
> - which is the correct behavior.
> 4.On Advanced Search in UI , fired search typename = hive_table
> *  In the 1st page , 1- 25 results were shown.
> *  On clicking next , in the 2nd page , 26 - 50 results were shown
> *  On  clicking next , Expected to land in 3rd page with 51 - 75 
> results , but , 26-50 results were loaded again and the Next Button was 
> disabled.
> Calls made to the Atlas backend seem to be correct. On clicking "Next" each 
> time , correct set of results were fetched. For example , call was made to 
> fetch entities from offset 50 , limit = 25 , but the UI still showed 26-50 
> results and disabled "Next" button.



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

[jira] [Comment Edited] (ATLAS-2128) UI Regression : DSL Results pagination doesn't spawn more than 2 pages

2017-09-11 Thread Ayub Pathan (JIRA) 

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

Ayub Pathan edited comment on ATLAS-2128 at 9/11/17 10:02 AM:
--

Looks like, this issue is introduced as part of 
https://github.com/apache/atlas/commit/d0beadf2e4a83bce17b8c42e7a584a035cf416c2 
this commit.

To be more precise, this line might be causing the issue.: 
https://github.com/apache/atlas/blob/master/dashboardv2/public/js/views/search/SearchResultLayoutView.js#L366
{code}
if (!model.entities && that.offset > that.limit) {
that.ui.nextData.attr('disabled', true);
that.offset = that.offset - that.limit;
that.hideLoader();
return;
}
{code}

CC [~kevalbhatt]


was (Author: ayubkhan):
This issue is introduced as part of 
https://github.com/apache/atlas/commit/d0beadf2e4a83bce17b8c42e7a584a035cf416c2 
this commit.

To be more precise, this line might be causing the issue.: 
https://github.com/apache/atlas/blob/master/dashboardv2/public/js/views/search/SearchResultLayoutView.js#L366
{code}
if (!model.entities && that.offset > that.limit) {
that.ui.nextData.attr('disabled', true);
that.offset = that.offset - that.limit;
that.hideLoader();
return;
}
{code}

CC [~kevalbhatt]

> UI Regression : DSL Results pagination doesn't spawn more than 2 pages
> --
>
> Key: ATLAS-2128
> URL: https://issues.apache.org/jira/browse/ATLAS-2128
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Priority: Blocker
>
> 1. Created 300 hive_tables.
> 2. On Basic Search in UI , fired search typename= hive_table
> 3. hive_table results were fetched across 12 pages - 25 entities in each page 
> - which is the correct behavior.
> 4.On Advanced Search in UI , fired search typename = hive_table
> *  In the 1st page , 1- 25 results were shown.
> *  On clicking next , in the 2nd page , 26 - 50 results were shown
> *  On  clicking next , Expected to land in 3rd page with 51 - 75 
> results , but , 26-50 results were loaded again and the Next Button was 
> disabled.
> Calls made to the Atlas backend seem to be correct. On clicking "Next" each 
> time , correct set of results were fetched. For example , call was made to 
> fetch entities from offset 50 , limit = 25 , but the UI still showed 26-50 
> results and disabled "Next" button.



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

[jira] [Commented] (ATLAS-2128) UI Regression : DSL Results pagination doesn't spawn more than 2 pages

2017-09-11 Thread Ayub Pathan (JIRA) 

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

Ayub Pathan commented on ATLAS-2128:


This issue is introduced as part of 
https://github.com/apache/atlas/commit/d0beadf2e4a83bce17b8c42e7a584a035cf416c2 
this commit.

To be more precise, this line might be causing the issue.: 
https://github.com/apache/atlas/blob/master/dashboardv2/public/js/views/search/SearchResultLayoutView.js#L366
{code}
if (!model.entities && that.offset > that.limit) {
that.ui.nextData.attr('disabled', true);
that.offset = that.offset - that.limit;
that.hideLoader();
return;
}
{code}

CC [~kevalbhatt]

> UI Regression : DSL Results pagination doesn't spawn more than 2 pages
> --
>
> Key: ATLAS-2128
> URL: https://issues.apache.org/jira/browse/ATLAS-2128
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating, 0.8.1-incubating
>Reporter: Sharmadha Sainath
>Priority: Blocker
>
> 1. Created 300 hive_tables.
> 2. On Basic Search in UI , fired search typename= hive_table
> 3. hive_table results were fetched across 12 pages - 25 entities in each page 
> - which is the correct behavior.
> 4.On Advanced Search in UI , fired search typename = hive_table
> *  In the 1st page , 1- 25 results were shown.
> *  On clicking next , in the 2nd page , 26 - 50 results were shown
> *  On  clicking next , Expected to land in 3rd page with 51 - 75 
> results , but , 26-50 results were loaded again and the Next Button was 
> disabled.
> Calls made to the Atlas backend seem to be correct. On clicking "Next" each 
> time , correct set of results were fetched. For example , call was made to 
> fetch entities from offset 50 , limit = 25 , but the UI still showed 26-50 
> results and disabled "Next" button.



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

[jira] [Created] (ATLAS-2128) UI Regression : DSL Results pagination doesn't spawn more than 2 pages

2017-09-11 Thread Sharmadha Sainath (JIRA) 
Sharmadha Sainath created ATLAS-2128:


 Summary: UI Regression : DSL Results pagination doesn't spawn more 
than 2 pages
 Key: ATLAS-2128
 URL: https://issues.apache.org/jira/browse/ATLAS-2128
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 0.9-incubating, 0.8.1-incubating
Reporter: Sharmadha Sainath
Priority: Blocker


1. Created 300 hive_tables.
2. On Basic Search in UI , fired search typename= hive_table
3. hive_table results were fetched across 12 pages - 25 entities in each page - 
which is the correct behavior.
4.On Advanced Search in UI , fired search typename = hive_table
*  In the 1st page , 1- 25 results were shown.
*  On clicking next , in the 2nd page , 26 - 50 results were shown
*  On  clicking next , Expected to land in 3rd page with 51 - 75 
results , but , 26-50 results were loaded again and the Next Button was 
disabled.

Calls made to the Atlas backend seem to be correct. On clicking "Next" each 
time , correct set of results were fetched. For example , call was made to 
fetch entities from offset 50 , limit = 25 , but the UI still showed 26-50 
results and disabled "Next" button.




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

[jira] [Created] (ATLAS-2127) Import of an entity associated with a tag into backup cluster with updateTypeDefinition options set to false

2017-09-11 Thread Sharmadha Sainath (JIRA) 
Sharmadha Sainath created ATLAS-2127:


 Summary: Import of an entity associated with a tag into backup 
cluster with updateTypeDefinition options set to false
 Key: ATLAS-2127
 URL: https://issues.apache.org/jira/browse/ATLAS-2127
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
 Attachments: ImportExceptionWithTag.txt

1. On cluster1 , created an entity and associated it to a tag.
2. Exported the entity into a zipfile.
3. cluster2 is in clean state.(i.e no entity / tag is created)
4. Tried to import the entity zip into cluster2 with import option 
"updateTypeDefinition" set to false.
5. Import failed with NPE. 

Since updateTypeDefinition is set to false , NPE is thrown when the entity is 
attempted to be associated to the tag in the backup cluster.

This is the expected behavior , but the cause of the issue is not very explicit 
to the end user when Atlas throws NPE.

Attached the exception stack trace.




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