Re: Review Request 51514: [ATLAS-1144] Create/update entity API call should return more definitions

2016-08-30 Thread Apoorv Naik 


> On Aug. 31, 2016, 5:22 a.m., Madhan Neethiraj wrote:
> > webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java, 
> > line 197
> > 
> >
> > Does every request have its own 'uriInfo' object? If not, how does this 
> > method differentiate requests that include "responseType" query parameter 
> > from the ones that don't?

Yes, every request has it's own UriInfo object.


- Apoorv


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


On Aug. 30, 2016, 3:44 p.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/51514/
> ---
> 
> (Updated Aug. 30, 2016, 3:44 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Suma Shivaprasad.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> The bug states that the API response only shows one entity definition in the 
> response of an update/create call wherease the expectation seems to be of 
> getting the entire list of the entities that were created/updated.
> 
> The fix adds the required capability by the means of a query parameter 
> responseType with the value as "full", if the API call is made with this 
> extra parameter, the response would contain an additional field called 
> "definitionList" which is of type JsonArray. If the parameter is unspecified, 
> the API response remains unaffected.
> 
> 
> Diffs
> -
> 
>   webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
> 82016d0 
> 
> Diff: https://reviews.apache.org/r/51514/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Apoorv Naik
> 
>

Re: Review Request 51514: [ATLAS-1144] Create/update entity API call should return more definitions

2016-08-30 Thread Vimal Sharma 

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


Ship it!




- Vimal Sharma


On Aug. 30, 2016, 3:44 p.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/51514/
> ---
> 
> (Updated Aug. 30, 2016, 3:44 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Suma Shivaprasad.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> The bug states that the API response only shows one entity definition in the 
> response of an update/create call wherease the expectation seems to be of 
> getting the entire list of the entities that were created/updated.
> 
> The fix adds the required capability by the means of a query parameter 
> responseType with the value as "full", if the API call is made with this 
> extra parameter, the response would contain an additional field called 
> "definitionList" which is of type JsonArray. If the parameter is unspecified, 
> the API response remains unaffected.
> 
> 
> Diffs
> -
> 
>   webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
> 82016d0 
> 
> Diff: https://reviews.apache.org/r/51514/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Apoorv Naik
> 
>

[jira] [Created] (ATLAS-1149) Changes to UI to sort the hive table schema based on "position" attribute of hive_column

2016-08-30 Thread Sarath Subramanian (JIRA) 
Sarath Subramanian created ATLAS-1149:
-

 Summary: Changes to UI to sort the hive table schema based on 
"position" attribute of hive_column
 Key: ATLAS-1149
 URL: https://issues.apache.org/jira/browse/ATLAS-1149
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
Reporter: Sarath Subramanian
Assignee: Keval Bhatt


This is related to ATLAS-772, hive column needs to be sorted based on its 
original column order. New attribute "position" has been added to hive_column 
type which maintains the column order number. UI needs to use this information 
to sort the column based on this attribute



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1148) Business taxonomy: search for assets under taxonomy shows the root taxonomy as well

2016-08-30 Thread Shwetha G S (JIRA) 

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

Shwetha G S updated ATLAS-1148:
---
Attachment: Screen Shot 2016-08-30 at 9.50.47 PM.png

> Business taxonomy: search for assets under taxonomy shows the root taxonomy 
> as well
> ---
>
> Key: ATLAS-1148
> URL: https://issues.apache.org/jira/browse/ATLAS-1148
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
> Attachments: Screen Shot 2016-08-30 at 9.50.47 PM.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-1148) Business taxonomy: search for assets under taxonomy shows the root taxonomy as well

2016-08-30 Thread Shwetha G S (JIRA) 
Shwetha G S created ATLAS-1148:
--

 Summary: Business taxonomy: search for assets under taxonomy shows 
the root taxonomy as well
 Key: ATLAS-1148
 URL: https://issues.apache.org/jira/browse/ATLAS-1148
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1147) UI: column name doesn't show up in schema tab for hive table

2016-08-30 Thread Shwetha G S (JIRA) 

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

Shwetha G S updated ATLAS-1147:
---
Attachment: Screen Shot 2016-08-30 at 9.21.07 PM.png

> UI: column name doesn't show up in schema tab for hive table
> 
>
> Key: ATLAS-1147
> URL: https://issues.apache.org/jira/browse/ATLAS-1147
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
> Attachments: Screen Shot 2016-08-30 at 9.21.07 PM.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 51514: [ATLAS-1144] Create/update entity API call should return more definitions

2016-08-30 Thread Apoorv Naik 

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

(Updated Aug. 30, 2016, 3:44 p.m.)


Review request for atlas, Madhan Neethiraj and Suma Shivaprasad.


Repository: atlas


Description
---

The bug states that the API response only shows one entity definition in the 
response of an update/create call wherease the expectation seems to be of 
getting the entire list of the entities that were created/updated.

The fix adds the required capability by the means of a query parameter 
responseType with the value as "full", if the API call is made with this extra 
parameter, the response would contain an additional field called 
"definitionList" which is of type JsonArray. If the parameter is unspecified, 
the API response remains unaffected.


Diffs (updated)
-

  webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
82016d0 

Diff: https://reviews.apache.org/r/51514/diff/


Testing
---


Thanks,

Apoorv Naik

[jira] [Commented] (ATLAS-1143) Fail to create hive_table entity with void comment

2016-08-30 Thread Benjamin BONNET (JIRA) 

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

Benjamin BONNET commented on ATLAS-1143:


Here is the create statement : 
{code}hive> show create table toto;
OK
CREATE TABLE `toto`(
  `valeur` string)
COMMENT ''
ROW FORMAT SERDE
  'org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe'
STORED AS INPUTFORMAT
  'org.apache.hadoop.mapred.TextInputFormat'
OUTPUTFORMAT
  'org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat'
LOCATION
  'hdfs://sandbox.hortonworks.com:8020/apps/hive/warehouse/toto'
TBLPROPERTIES (
  'transient_lastDdlTime'='1471620189'){code}

> Fail to create hive_table entity with void comment
> --
>
> Key: ATLAS-1143
> URL: https://issues.apache.org/jira/browse/ATLAS-1143
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Benjamin BONNET
>
> Atlas server fails to create a hive_table entity representing a Hive table 
> taht was created with an empty comment. No comment at all is ok, but a '' 
> comment will lead to that error log :
> {code}
> 2016-08-19 15:23:11,143 INFO  - [NotificationHookConsumer thread-0:] ~ 
> updating entities {
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-870799112922",
> "version":0,
> "typeName":"hive_db",
> "state":"ACTIVE"
>   },
>   "typeName":"hive_db",
>   "values":{
> "name":"default",
> "location":"hdfs://sandbox.hortonworks.com:8020/apps/hive/warehouse",
> "description":"Default Hive database",
> "ownerType":2,
> "qualifiedName":"default@Sandbox",
> "owner":"public",
> "clusterName":"Sandbox",
> "parameters":{
> }
>   },
>   "traitNames":[
>   ],
>   "traits":{
>   }
> },{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-870922191414",
> "version":0,
> "typeName":"hive_table",
> "state":"ACTIVE"
>   },
>   "typeName":"hive_table",
>   "values":{
> "tableType":"MANAGED_TABLE",
> "name":"toto",
> "createTime":"2016-08-19T15:23:09.000Z",
> "temporary":false,
> "db":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-870799112922",
> "version":0,
> "typeName":"hive_db",
> "state":"ACTIVE"
>   },
>   "typeName":"hive_db",
>   "values":{
> "name":"default",
> "location":"hdfs://sandbox.hortonworks.com:8020/apps/hive/warehouse",
> "description":"Default Hive database",
> "ownerType":2,
> "qualifiedName":"default@Sandbox",
> "owner":"public",
> "clusterName":"Sandbox",
> "parameters":{
> }
>   },
>   "traitNames":[
>   ],
>   "traits":{
>   }
> },
> "retention":0,
> "qualifiedName":"default.toto@Sandbox",
> "columns":[
>   {
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>   "id":"-870922398553",
>   "version":0,
>   "typeName":"hive_column",
>   "state":"ACTIVE"
> },
> "typeName":"hive_column",
> "values":{
>   "qualifiedName":"default.toto.valeur@Sandbox",
>   "type":"string",
>   "name":"valeur",
>   "table":{
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-870922191414",
> "version":0,
> "typeName":"hive_table",
> "state":"ACTIVE"
>   }
> },
> "traitNames":[
> ],
> "traits":{
> }
>   }
> ],
> "comment":"",
> "lastAccessTime":"2016-08-19T15:23:09.000Z",
> "sd":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-870922339393",
> "version":0,
> "typeName":"hive_storagedesc",
> "state":"ACTIVE"
>   },
>   "typeName":"hive_storagedesc",
>   "values":{
> 
> "location":"hdfs://sandbox.hortonworks.com:8020/apps/hive/warehouse/toto",
> "serdeInfo":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
>   "typeName":"hive_serde",
>   "values":{
>

ApacheCon Seville CFP closes September 9th

2016-08-30 Thread Rich Bowen 
It's traditional. We wait for the last minute to get our talk proposals
in for conferences.

Well, the last minute has arrived. The CFP for ApacheCon Seville closes
on September 9th, which is less than 2 weeks away. It's time to get your
talks in, so that we can make this the best ApacheCon yet.

It's also time to discuss with your developer and user community whether
there's a track of talks that you might want to propose, so that you
have more complete coverage of your project than a talk or two.

For Apache Big Data, the relevant URLs are:
Event details:
http://events.linuxfoundation.org/events/apache-big-data-europe
CFP:
http://events.linuxfoundation.org/events/apache-big-data-europe/program/cfp

For ApacheCon Europe, the relevant URLs are:
Event details: http://events.linuxfoundation.org/events/apachecon-europe
CFP: http://events.linuxfoundation.org/events/apachecon-europe/program/cfp

This year, we'll be reviewing papers "blind" - that is, looking at the
abstracts without knowing who the speaker is. This has been shown to
eliminate the "me and my buddies" nature of many tech conferences,
producing more diversity, and more new speakers. So make sure your
abstracts clearly explain what you'll be talking about.

For further updated about ApacheCon, follow us on Twitter, @ApacheCon,
or drop by our IRC channel, #apachecon on the Freenode IRC network.

-- 
Rich Bowen
WWW: http://apachecon.com/
Twitter: @ApacheCon

[jira] [Updated] (ATLAS-1146) Hive lineage with falcon doesn't depict correctly

2016-08-30 Thread Shwetha G S (JIRA) 

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

Shwetha G S updated ATLAS-1146:
---
Description: With the lineage, process1 -> output feed1 and feed1 maps to 
hive table table1. Showing lineage for table1 doesn't show inputs of process1, 
need to click on feed1 to get process1 inputs which doesn't look right  (was: 
With the lineage, process1 -> output feed1 and feed1 maps to hive table table1. 
Showing lineage for tabl1 doesn't show inputs of process1)

> Hive lineage with falcon doesn't depict correctly
> -
>
> Key: ATLAS-1146
> URL: https://issues.apache.org/jira/browse/ATLAS-1146
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>
> With the lineage, process1 -> output feed1 and feed1 maps to hive table 
> table1. Showing lineage for table1 doesn't show inputs of process1, need to 
> click on feed1 to get process1 inputs which doesn't look right



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-1146) Hive lineage with falcon doesn't depict correctly

2016-08-30 Thread Shwetha G S (JIRA) 
Shwetha G S created ATLAS-1146:
--

 Summary: Hive lineage with falcon doesn't depict correctly
 Key: ATLAS-1146
 URL: https://issues.apache.org/jira/browse/ATLAS-1146
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S


With the lineage, process1 -> output feed1 and feed1 maps to hive table table1. 
Showing lineage for tabl1 doesn't show inputs of process1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-1143) Fail to create hive_table entity with void comment

2016-08-30 Thread Ayub Khan (JIRA) 

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

Ayub Khan edited comment on ATLAS-1143 at 8/30/16 1:49 PM:
---

[~bbonnet] Even with empty 'comment' is working fine with latest bits.

{noformat}
2016-08-30 13:40:51,354 INFO  - [NotificationHookConsumer thread-0:] ~ updating 
entities {
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
  "id":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-2713140355078",
"version":0,
"typeName":"hive_db",
"state":"ACTIVE"
  },
  "typeName":"hive_db",
  "values":{
"name":"default",

"location":"hdfs://atlas-r7-parallel-classes-3.openstacklocal:8020/apps/hive/warehouse",
"description":"Default Hive database",
"ownerType":2,
"qualifiedName":"default@cl1",
"owner":"public",
"clusterName":"cl1",
"parameters":{

}
  },
  "traitNames":[

  ],
  "traits":{

  }
},{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
  "id":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-2713140355077",
"version":0,
"typeName":"hive_table",
"state":"ACTIVE"
  },
  "typeName":"hive_table",
  "values":{
"tableType":"MANAGED_TABLE",
"name":"t5",
"createTime":"2016-08-30T13:40:51.000Z",
"temporary":false,
"db":{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
  "id":{

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-2713140355078",
"version":0,
"typeName":"hive_db",
"state":"ACTIVE"
  },
  "typeName":"hive_db",
  "values":{
"name":"default",

"location":"hdfs://atlas-r7-parallel-classes-3.openstacklocal:8020/apps/hive/warehouse",
"description":"Default Hive database",
"ownerType":2,
"qualifiedName":"default@cl1",
"owner":"public",
"clusterName":"cl1",
"parameters":{

}
  },
  "traitNames":[

  ],
  "traits":{

  }
},
"retention":0,
"qualifiedName":"default.t5@cl1",
"columns":[
  {

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
"id":{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
  "id":"-2713140355075",
  "version":0,
  "typeName":"hive_column",
  "state":"ACTIVE"
},
"typeName":"hive_column",
"values":{
  "name":"abc",
  "qualifiedName":"default.t5.abc@cl1",
  "owner":"hrt_qa",
  "type":"string",
  "table":{

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-2713140355077",
"version":0,
"typeName":"hive_table",
"state":"ACTIVE"
  }
},
"traitNames":[

],
"traits":{

}
  }
],
"comment":"",
"lastAccessTime":"2016-08-30T13:40:51.000Z",
"owner":"hrt_qa",
"sd":{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
  "id":{

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-2713140355076",
"version":0,
"typeName":"hive_storagedesc",
"state":"ACTIVE"
  },
  "typeName":"hive_storagedesc",
  "values":{

"location":"hdfs://atlas-r7-parallel-classes-3.openstacklocal:8020/apps/hive/warehouse/t5",
"serdeInfo":{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
  "typeName":"hive_serde",
  "values":{

"serializationLib":"org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe",
"parameters":{
  "serialization.format":"1"
}
  }
},
"qualifiedName":"default.t5@cl1_storage",

"outputFormat":"org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat",
"compressed":false,
"numBuckets":-1,
"inputFormat":"org.apache.hadoop.mapred.TextInputFormat",
"parameters":{

},
"storedAsSubDirectories":false,
"table":{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
  "id":"-2713140355077",
  "version":0,
  "typeName":"hive_table",
  "state":"ACTIVE"
}
  },
  "traitNames":[

  ],
  "traits":{

  }
},
"parameters":{
  "rawDataSize":"0",
  "numFiles":"0",
  "transient_lastDdlTime":"1472564451",
  "totalSize":"0",
  "comment":"",
  "COLUMN_STATS_ACCURATE":"{\"BASIC_STATS\":\"true\"}",
  "numRows":"0"
},

[jira] [Created] (ATLAS-1145) Storm hook with kafka topic and hive bolt picks wrong hive table name

2016-08-30 Thread Shwetha G S (JIRA) 
Shwetha G S created ATLAS-1145:
--

 Summary: Storm hook with kafka topic and hive bolt picks wrong 
hive table name 
 Key: ATLAS-1145
 URL: https://issues.apache.org/jira/browse/ATLAS-1145
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S


Storm hook with kafka topic and hive bolt picks kafka topic name as hive table 
name



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ATLAS-1143) Fail to create hive_table entity with void comment

2016-08-30 Thread Ayub Khan (JIRA) 

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

Ayub Khan edited comment on ATLAS-1143 at 8/30/16 1:49 PM:
---

[~bbonnet] Even with empty 'comment' is working fine with latest bits.

{noformat}
2016-08-30 13:40:51,354 INFO  - [NotificationHookConsumer thread-0:] ~ updating 
entities {
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
  "id":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-2713140355078",
"version":0,
"typeName":"hive_db",
"state":"ACTIVE"
  },
  "typeName":"hive_db",
  "values":{
"name":"default",

"location":"hdfs://atlas-r7-parallel-classes-3.openstacklocal:8020/apps/hive/warehouse",
"description":"Default Hive database",
"ownerType":2,
"qualifiedName":"default@cl1",
"owner":"public",
"clusterName":"cl1",
"parameters":{

}
  },
  "traitNames":[

  ],
  "traits":{

  }
},{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
  "id":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-2713140355077",
"version":0,
"typeName":"hive_table",
"state":"ACTIVE"
  },
  "typeName":"hive_table",
  "values":{
"tableType":"MANAGED_TABLE",
"name":"t5",
"createTime":"2016-08-30T13:40:51.000Z",
"temporary":false,
"db":{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
  "id":{

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-2713140355078",
"version":0,
"typeName":"hive_db",
"state":"ACTIVE"
  },
  "typeName":"hive_db",
  "values":{
"name":"default",

"location":"hdfs://atlas-r7-parallel-classes-3.openstacklocal:8020/apps/hive/warehouse",
"description":"Default Hive database",
"ownerType":2,
"qualifiedName":"default@cl1",
"owner":"public",
"clusterName":"cl1",
"parameters":{

}
  },
  "traitNames":[

  ],
  "traits":{

  }
},
"retention":0,
"qualifiedName":"default.t5@cl1",
"columns":[
  {

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
"id":{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
  "id":"-2713140355075",
  "version":0,
  "typeName":"hive_column",
  "state":"ACTIVE"
},
"typeName":"hive_column",
"values":{
  "name":"abc",
  "qualifiedName":"default.t5.abc@cl1",
  "owner":"hrt_qa",
  "type":"string",
  "table":{

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-2713140355077",
"version":0,
"typeName":"hive_table",
"state":"ACTIVE"
  }
},
"traitNames":[

],
"traits":{

}
  }
],
"comment":"",
"lastAccessTime":"2016-08-30T13:40:51.000Z",
"owner":"hrt_qa",
"sd":{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
  "id":{

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-2713140355076",
"version":0,
"typeName":"hive_storagedesc",
"state":"ACTIVE"
  },
  "typeName":"hive_storagedesc",
  "values":{

"location":"hdfs://atlas-r7-parallel-classes-3.openstacklocal:8020/apps/hive/warehouse/t5",
"serdeInfo":{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
  "typeName":"hive_serde",
  "values":{

"serializationLib":"org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe",
"parameters":{
  "serialization.format":"1"
}
  }
},
"qualifiedName":"default.t5@cl1_storage",

"outputFormat":"org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat",
"compressed":false,
"numBuckets":-1,
"inputFormat":"org.apache.hadoop.mapred.TextInputFormat",
"parameters":{

},
"storedAsSubDirectories":false,
"table":{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
  "id":"-2713140355077",
  "version":0,
  "typeName":"hive_table",
  "state":"ACTIVE"
}
  },
  "traitNames":[

  ],
  "traits":{

  }
},
"parameters":{
  "rawDataSize":"0",
  "numFiles":"0",
  "transient_lastDdlTime":"1472564451",
  "totalSize":"0",
  "comment":"",
  "COLUMN_STATS_ACCURATE":"{\"BASIC_STATS\":\"true\"}",
  "numRows":"0"
},

Re: Review Request 51492: ATLAS-1141: UI-Issue - Tag with spaces, when searched, then it is wrongly set in search textbox.

2016-08-30 Thread Kalyani Kashikar 

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

(Updated Aug. 30, 2016, 12:24 p.m.)


Review request for atlas, keval bhatt, Madhan Neethiraj, Shwetha GS, Selvamohan 
Neethiraj, and Suma Shivaprasad.


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


Repository: atlas


Description
---

Patch includes fix for below issues - 

* If a Tag is created with space i.e "Tags for Test" and through "Search Tag" 
link it is searched, then in search box it only displays "for Test" instead of 
whole Tag name.
* In firefox and safari the date is showing invaid on taxonomy page.


Diffs (updated)
-

  
dashboardv2/public/js/views/business_catalog/BusinessCatalogDetailLayoutView.js 
d592d1e 
  dashboardv2/public/js/views/business_catalog/TreeLayoutView.js be47725 
  dashboardv2/public/js/views/tag/TagLayoutView.js b1cb6cc 

Diff: https://reviews.apache.org/r/51492/diff/


Testing
---

Tested following scenarios : 

* The Date on business taxonomy page is showing in proper format on firefox and 
safari browser.
* The whole tag is set with space after searched through "search tag" and tag 
search page results is showing properly.


Thanks,

Kalyani Kashikar

[jira] [Updated] (ATLAS-1141) UI-Issue - Tag with spaces, when searched, then it is wrongly set in search textbox.

2016-08-30 Thread Kalyani Kashikar (JIRA) 

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

Kalyani Kashikar updated ATLAS-1141:

Attachment: ATLAS-1141.1.patch

> UI-Issue - Tag with spaces, when searched, then it is wrongly set in search 
> textbox.
> 
>
> Key: ATLAS-1141
> URL: https://issues.apache.org/jira/browse/ATLAS-1141
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-1141.1.patch, ATLAS-1141.patch
>
>
> If a Tag is created with space i.e "Tags for Test" and through "Search Tag" 
> link it is searched, then in search box it only displays " for Test` " 
> instead ​ of whole Tag name



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-1140) All the tag's attributes are not seen while applying a tag to entity.

2016-08-30 Thread Keval Bhatt (JIRA) 

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

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

> All the tag's attributes are not seen while applying a tag to entity.
> -
>
> Key: ATLAS-1140
> URL: https://issues.apache.org/jira/browse/ATLAS-1140
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Keval Bhatt
> Attachments: ATLAS-1140.patch
>
>
> All the tag attributes (self + inherited ) are not while adding its value 
> when tag is applied to an entity, the tag was created with attribute 
> inherited from other tag.
> Steps to reproduce the issue.
> 1.Create a Tag with Attribute e.g Tag - T1, Attribute - A1 & Attribute - A2
> 2.Create another Tag having parent Tag as T1 and few Attribute e.g Tag 2 - 
> T2, Attribute - A3 & Attribute - A4
> 3.Now go to any entity and click on it Add tag button
> 4.Now select second Tag i.e T2
> Error:-
> Only attribute A1 and A2 (ie inheritated one's) are displayed, Second Tag(T2) 
> Attributes (A3 & A4) are not displayed"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Podling Report Reminder - September 2016

2016-08-30 Thread johndament 
Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 21 September 2016, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, September 07).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.

This should be appended to the Incubator Wiki page at:

http://wiki.apache.org/incubator/September2016

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

[jira] [Commented] (ATLAS-772) Ordering of columns is not maintained in schema query response, where as hive table entity response maintains the ordering

2016-08-30 Thread Vimal Sharma (JIRA) 

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

Vimal Sharma commented on ATLAS-772:


+1 for patch

> Ordering of columns is not maintained in schema query response, where as hive 
> table entity response maintains the ordering
> --
>
> Key: ATLAS-772
> URL: https://issues.apache.org/jira/browse/ATLAS-772
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Sarath Subramanian
>  Labels: patch
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-772.patch
>
>
> Ordering of columns is not maintained in schema query response, where as hive 
> table entity response maintains the ordering
> Table schema
> {noformat}
> 0: jdbc:hive2://localhost:1/default> describe formatted table_pbrscdldkm;
> +---+--++--+
> |   col_name|  data_type  
>  |comment |
> +---+--++--+
> | # col_name| data_type   
>  | comment|
> |   | NULL
>  | NULL   |
> | viewtime  | int 
>  ||
> | userid| bigint  
>  ||
> | page_url  | string  
>  ||
> | referrer_url  | string  
>  ||
> | ip| string  
>  ||
> |   | NULL
>  | NULL   |
> | # Partition Information   | NULL
>  | NULL   |
> | # col_name| data_type   
>  | comment|
> |   | NULL
>  | NULL   |
> | dt| string  
>  ||
> | country   | string  
>  | partitioned columns comments.  |
> |   | NULL
>  | NULL   |
> | # Detailed Table Information  | NULL
>  | NULL   |
> | Database: | db2pbrscdldkm   
>  | NULL   |
> | Owner:| apathan 
>  | NULL   |
> | CreateTime:   | Tue May 10 16:36:56 IST 2016
>  | NULL   |
> | LastAccessTime:   | UNKNOWN 
>  | NULL   |
> | Protect Mode: | None
>  | NULL   |
> | Retention:| 0   
>  | NULL   |
> | Location: | 
> hdfs://localhost:9000/user/hive/warehouse/db2pbrscdldkm.db/table_pbrscdldkm  
> | NULL   |
> | Table Type:   | MANAGED_TABLE   
>

[jira] [Commented] (ATLAS-1143) Fail to create hive_table entity with void comment

2016-08-30 Thread Benjamin BONNET (JIRA) 

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

Benjamin BONNET commented on ATLAS-1143:


Hi,

actually, I am using the 0.7 that is shipped into HDP2.5 preview (sandbox).
On my sandbox, I tried to PUT the json that your log shows. I get a HTTP 200 
and the 't3' hive_table is created OK in Atlas.

Nevertheless I noticed that 'comment' value is not empty in your json : it is a 
one space character. Editing the json to make comment empty et PUTting the 
json, I get the same stacktrace as the one I posted.

Regards

> Fail to create hive_table entity with void comment
> --
>
> Key: ATLAS-1143
> URL: https://issues.apache.org/jira/browse/ATLAS-1143
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Benjamin BONNET
>
> Atlas server fails to create a hive_table entity representing a Hive table 
> taht was created with an empty comment. No comment at all is ok, but a '' 
> comment will lead to that error log :
> {code}
> 2016-08-19 15:23:11,143 INFO  - [NotificationHookConsumer thread-0:] ~ 
> updating entities {
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-870799112922",
> "version":0,
> "typeName":"hive_db",
> "state":"ACTIVE"
>   },
>   "typeName":"hive_db",
>   "values":{
> "name":"default",
> "location":"hdfs://sandbox.hortonworks.com:8020/apps/hive/warehouse",
> "description":"Default Hive database",
> "ownerType":2,
> "qualifiedName":"default@Sandbox",
> "owner":"public",
> "clusterName":"Sandbox",
> "parameters":{
> }
>   },
>   "traitNames":[
>   ],
>   "traits":{
>   }
> },{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-870922191414",
> "version":0,
> "typeName":"hive_table",
> "state":"ACTIVE"
>   },
>   "typeName":"hive_table",
>   "values":{
> "tableType":"MANAGED_TABLE",
> "name":"toto",
> "createTime":"2016-08-19T15:23:09.000Z",
> "temporary":false,
> "db":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-870799112922",
> "version":0,
> "typeName":"hive_db",
> "state":"ACTIVE"
>   },
>   "typeName":"hive_db",
>   "values":{
> "name":"default",
> "location":"hdfs://sandbox.hortonworks.com:8020/apps/hive/warehouse",
> "description":"Default Hive database",
> "ownerType":2,
> "qualifiedName":"default@Sandbox",
> "owner":"public",
> "clusterName":"Sandbox",
> "parameters":{
> }
>   },
>   "traitNames":[
>   ],
>   "traits":{
>   }
> },
> "retention":0,
> "qualifiedName":"default.toto@Sandbox",
> "columns":[
>   {
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
> "id":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>   "id":"-870922398553",
>   "version":0,
>   "typeName":"hive_column",
>   "state":"ACTIVE"
> },
> "typeName":"hive_column",
> "values":{
>   "qualifiedName":"default.toto.valeur@Sandbox",
>   "type":"string",
>   "name":"valeur",
>   "table":{
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-870922191414",
> "version":0,
> "typeName":"hive_table",
> "state":"ACTIVE"
>   }
> },
> "traitNames":[
> ],
> "traits":{
> }
>   }
> ],
> "comment":"",
> "lastAccessTime":"2016-08-19T15:23:09.000Z",
> "sd":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> 
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-870922339393",
> "version":0,
> "typeName":"hive_storagedesc",
> "state":"ACTIVE"
>   },
>   "typeName":"hive_storagedesc",
>   "values":{
> 
> "location":"hdfs://sandbox.hortonworks.com:8020/apps/hive/warehouse/toto",
> "serdeInfo":{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
>   "typeName":"hive_serde",
>   "values":{
> 
>

[jira] [Commented] (ATLAS-1143) Fail to create hive_table entity with void comment

2016-08-30 Thread Ayub Khan (JIRA) 

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

Ayub Khan commented on ATLAS-1143:
--

[~bbonnet] Thanks for the details.

I tried to repro this issue with the latest bits but i dont see any exception 
in the atlas logs. 
{noformat}
2016-08-30 08:29:28,701 INFO  - [NotificationHookConsumer thread-0:] ~ Audit: 
hrt_qa/LocalAtlasClient-localhost performed request PUT api/atlas/entities 
(localhost) at time 2016-08-30T08:29Z (AUDIT:104)
2016-08-30 08:29:28,702 INFO  - [NotificationHookConsumer thread-0:] ~ updating 
entities {
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
  "id":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-90715884798176",
"version":0,
"typeName":"hive_db",
"state":"ACTIVE"
  },
  "typeName":"hive_db",
  "values":{
"name":"default",

"location":"hdfs://atlas-r7-parallel-classes-3.openstacklocal:8020/apps/hive/warehouse",
"description":"Default Hive database",
"ownerType":2,
"qualifiedName":"default@cl1",
"owner":"public",
"clusterName":"cl1",
"parameters":{

}
  },
  "traitNames":[

  ],
  "traits":{

  }
},{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
  "id":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-90715884798175",
"version":0,
"typeName":"hive_table",
"state":"ACTIVE"
  },
  "typeName":"hive_table",
  "values":{
"tableType":"MANAGED_TABLE",
"name":"t3",
"createTime":"2016-08-30T08:29:24.000Z",
"temporary":false,
"db":{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
  "id":{

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-90715884798176",
"version":0,
"typeName":"hive_db",
"state":"ACTIVE"
  },
  "typeName":"hive_db",
  "values":{
"name":"default",

"location":"hdfs://atlas-r7-parallel-classes-3.openstacklocal:8020/apps/hive/warehouse",
"description":"Default Hive database",
"ownerType":2,
"qualifiedName":"default@cl1",
"owner":"public",
"clusterName":"cl1",
"parameters":{

}
  },
  "traitNames":[

  ],
  "traits":{

  }
},
"retention":0,
"qualifiedName":"default.t3@cl1",
"columns":[
  {

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
"id":{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
  "id":"-90715884798173",
  "version":0,
  "typeName":"hive_column",
  "state":"ACTIVE"
},
"typeName":"hive_column",
"values":{
  "name":"abc",
  "qualifiedName":"default.t3.abc@cl1",
  "owner":"hrt_qa",
  "type":"string",
  "table":{

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-90715884798175",
"version":0,
"typeName":"hive_table",
"state":"ACTIVE"
  }
},
"traitNames":[

],
"traits":{

}
  }
],
"comment":" ",
"lastAccessTime":"2016-08-30T08:29:24.000Z",
"owner":"hrt_qa",
"sd":{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
  "id":{

"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-90715884798174",
"version":0,
"typeName":"hive_storagedesc",
"state":"ACTIVE"
  },
  "typeName":"hive_storagedesc",
  "values":{

"location":"hdfs://atlas-r7-parallel-classes-3.openstacklocal:8020/apps/hive/warehouse/t3",
"serdeInfo":{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
  "typeName":"hive_serde",
  "values":{

"serializationLib":"org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe",
"parameters":{
  "serialization.format":"1"
}
  }
},
"qualifiedName":"default.t3@cl1_storage",

"outputFormat":"org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat",
"compressed":false,
"numBuckets":-1,
"inputFormat":"org.apache.hadoop.mapred.TextInputFormat",
"parameters":{

},
"storedAsSubDirectories":false,
"table":{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
  "id":"-90715884798175",
  "version":0,
  "typeName":"hive_table",
  "state":"ACTIVE"
}
  },
  "traitNames":[

  ],
  "traits":{

  }
},
"parameters":{

[jira] [Commented] (ATLAS-1143) Fail to create hive_table entity with void comment

2016-08-30 Thread Benjamin BONNET (JIRA) 

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

Benjamin BONNET commented on ATLAS-1143:


Hi,
Thanks, [~ayubkhan]. Here is hive_table model I get, requesting the API :
{code}
{
"typeName": "hive_table",
"definition": {
"enumTypes": [],
"structTypes": [],
"traitTypes": [],
"classTypes": [
{
"superTypes": [
"DataSet"
],
"hierarchicalMetaTypeName": "org.apache.atlas.typesystem.types.ClassType",
"typeName": "hive_table",
"typeDescription": null,
"attributeDefinitions": [
{
"name": "db",
"dataTypeName": "hive_db",
"multiplicity": "required",
"isComposite": false,
"isUnique": false,
"isIndexable": true,
"reverseAttributeName": null
},
{
"name": "createTime",
"dataTypeName": "date",
"multiplicity": "optional",
"isComposite": false,
"isUnique": false,
"isIndexable": true,
"reverseAttributeName": null
},
{
"name": "lastAccessTime",
"dataTypeName": "date",
"multiplicity": "optional",
"isComposite": false,
"isUnique": false,
"isIndexable": true,
"reverseAttributeName": null
},
{
"name": "comment",
"dataTypeName": "string",
"multiplicity": "optional",
"isComposite": false,
"isUnique": false,
"isIndexable": true,
"reverseAttributeName": null
},
{
"name": "retention",
"dataTypeName": "int",
"multiplicity": "optional",
"isComposite": false,
"isUnique": false,
"isIndexable": true,
"reverseAttributeName": null
},
{
"name": "sd",
"dataTypeName": "hive_storagedesc",
"multiplicity": "optional",
"isComposite": true,
"isUnique": false,
"isIndexable": true,
"reverseAttributeName": null
},
{
"name": "partitionKeys",
"dataTypeName": "array",
"multiplicity": "optional",
"isComposite": true,
"isUnique": false,
"isIndexable": true,
"reverseAttributeName": null
},
{
"name": "aliases",
"dataTypeName": "array",
"multiplicity": "optional",
"isComposite": true,
"isUnique": false,
"isIndexable": true,
"reverseAttributeName": null
},
{
"name": "columns",
"dataTypeName": "array",
"multiplicity": "optional",
"isComposite": true,
"isUnique": false,
"isIndexable": true,
"reverseAttributeName": null
},
{
"name": "parameters",
"dataTypeName": "map",
"multiplicity": "optional",
"isComposite": false,
"isUnique": false,
"isIndexable": true,
"reverseAttributeName": null
},
{
"name": "viewOriginalText",
"dataTypeName": "string",
"multiplicity": "optional",
"isComposite": false,
"isUnique": false,
"isIndexable": true,
"reverseAttributeName": null
},
{
"name": "viewExpandedText",
"dataTypeName": "string",
"multiplicity": "optional",
"isComposite": false,
"isUnique": false,
"isIndexable": true,
"reverseAttributeName": null
},
{
"name": "tableType",
"dataTypeName": "string",
"multiplicity": "optional",
"isComposite": false,
"isUnique": false,
"isIndexable": true,
"reverseAttributeName": null
},
{
"name": "temporary",
"dataTypeName": "boolean",
"multiplicity": "optional",
"isComposite": false,
"isUnique": false,
"isIndexable": true,
"reverseAttributeName": null
}
]
}
]
},
"requestId": "qtp86996017-16 - bed8abd3-b7a0-47de-aad5-a959a3f25997"
}
{code}
As you can see, parameters attribute is optionnal, but I think the problem 
occurs because Atals considers attributes inside parameters should not be empty 
strings.


> Fail to create hive_table entity with void comment
> --
>
> Key: ATLAS-1143
> URL: https://issues.apache.org/jira/browse/ATLAS-1143
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Benjamin BONNET
>
> Atlas server fails to create a hive_table entity representing a Hive table 
> taht was created with an empty comment. No comment at all is ok, but a '' 
> comment will lead to that error log :
> {code}
> 2016-08-19 15:23:11,143 INFO  - [NotificationHookConsumer thread-0:] ~ 
> updating entities {
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-870799112922",
> "version":0,
> "typeName":"hive_db",
> "state":"ACTIVE"
>   },
>   "typeName":"hive_db",
>   "values":{
> "name":"default",
> "location":"hdfs://sandbox.hortonworks.com:8020/apps/hive/warehouse",
> "description":"Default Hive database",
> "ownerType":2,
> "qualifiedName":"default@Sandbox",
> "owner":"public",
> "clusterName":"Sandbox",
> "parameters":{
> }
>   },
>   "traitNames":[
>   ],
>   "traits":{
>   }
> },{
>   
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id":{
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id":"-870922191414",
> "version":0,
> "typeName":"hive_table",
> "state":"ACTIVE"
>   },
>   "typeName":"hive_table",
>   "values":{
> "tableType":"MANAGED_TABLE",
> "name":"toto",

Re: Review Request 51514: [ATLAS-1144] Create/update entity API call should return more definitions

2016-08-30 Thread Vimal Sharma 


> On Aug. 30, 2016, 7:02 a.m., Vimal Sharma wrote:
> >

Please generate the patch from atlas repo root. This patch is not applying 
successfully since it has been created from inside webapp directory.


- Vimal


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


On Aug. 30, 2016, 6:32 a.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/51514/
> ---
> 
> (Updated Aug. 30, 2016, 6:32 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Suma Shivaprasad.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> The bug states that the API response only shows one entity definition in the 
> response of an update/create call wherease the expectation seems to be of 
> getting the entire list of the entities that were created/updated.
> 
> The fix adds the required capability by the means of a query parameter 
> responseType with the value as "full", if the API call is made with this 
> extra parameter, the response would contain an additional field called 
> "definitionList" which is of type JsonArray. If the parameter is unspecified, 
> the API response remains unaffected.
> 
> 
> Diffs
> -
> 
>   webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
> 82016d0 
> 
> Diff: https://reviews.apache.org/r/51514/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Apoorv Naik
> 
>

Re: Review Request 51514: [ATLAS-1144] Create/update entity API call should return more definitions

2016-08-30 Thread Vimal Sharma 

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




webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java (line 
186)


It would make sense to add the first entity definition to definitionList



webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java (line 
203)


Entity definition of first entity will get repeated since the first one has 
already been added in DEFINITION


- Vimal Sharma


On Aug. 30, 2016, 6:32 a.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/51514/
> ---
> 
> (Updated Aug. 30, 2016, 6:32 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Suma Shivaprasad.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> The bug states that the API response only shows one entity definition in the 
> response of an update/create call wherease the expectation seems to be of 
> getting the entire list of the entities that were created/updated.
> 
> The fix adds the required capability by the means of a query parameter 
> responseType with the value as "full", if the API call is made with this 
> extra parameter, the response would contain an additional field called 
> "definitionList" which is of type JsonArray. If the parameter is unspecified, 
> the API response remains unaffected.
> 
> 
> Diffs
> -
> 
>   webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
> 82016d0 
> 
> Diff: https://reviews.apache.org/r/51514/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Apoorv Naik
> 
>

Review Request 51515: ATLAS-772 : New attribute has been added to the hive_column type to capture the position of hive columns for sorting

2016-08-30 Thread Sarath Kumar Subramanian 

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

Review request for atlas, Madhan Neethiraj and Suma Shivaprasad.


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


Repository: atlas


Description
---

When a schema query is issued against a hive table, the hive_column entities 
are retrieved from the titan database. Each hive_column entity is a vertex in 
titan and currently titan doesn't store any column order position in its vertex 
attributes. The hive_columns are retrieved in the sort order of the Vertex ID 
which is not same as the Hive column order position. The fix attached is to 
introduce a new "position" attribute in hive_column type, which maintains the 
column order position. This column order position can be consumed by any 
clients - including UI to display the columns in the original position/order.


Diffs
-

  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/bridge/HiveMetaStoreBridge.java
 1f13d74 
  
addons/hive-bridge/src/main/java/org/apache/atlas/hive/model/HiveDataModelGenerator.java
 b308cc9 

Diff: https://reviews.apache.org/r/51515/diff/


Testing
---

Tested the changes with hive column operations – Add new column, Drop column, 
Rename column, Move column to first or at a position.


Thanks,

Sarath Kumar Subramanian