[jira] [Commented] (ATLAS-1155) Errors in Eclipse when I bring in the latest code

[Shwetha G S (JIRA)]

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

Shwetha G S commented on ATLAS-1155:


+1

> Errors in Eclipse when I bring in the latest code
> -
>
> Key: ATLAS-1155
> URL: https://issues.apache.org/jira/browse/ATLAS-1155
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: David Radley
>Assignee: David Radley
> Fix For: 0.8-incubating
>
> Attachments: atlas1155.patch
>
>
> I have brought the latest atlas code into an Eclipse environment and see an 
> error in GraphBackedDiscoveryService, 
> line 154
>  scala.collection.immutable.List.empty()); it says method empty is ambiguous.
> if I replace this expression with null it complies.



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

[jira] [Assigned] (ATLAS-1118) DSL query of few types listed in /api/atlas/types , throws "invalid expression" exception

[Vimal Sharma (JIRA)]

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

Vimal Sharma reassigned ATLAS-1118:
---

Assignee: Vimal Sharma

> DSL query of few types listed in /api/atlas/types , throws "invalid 
> expression" exception
> -
>
> Key: ATLAS-1118
> URL: https://issues.apache.org/jira/browse/ATLAS-1118
> Project: Atlas
>  Issue Type: Bug
>Reporter: Sharmadha Sainath
>Assignee: Vimal Sharma
>Priority: Minor
>
> Few types like
> hive_serde
> fs_permissions
> file_action
> hive_order
> which are listed in /api/atlas/types throw exception when queried in DSL.
> Though New UI has a drop down  "Search For" which lists available valid types 
> and doesn't allow users to enter invald types , "Optional Conditions" text 
> box can also be used to search types.
> Hence , when "hive_order" is entered in the text box , it throws exception.



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

[jira] [Assigned] (ATLAS-1163) Sorting of hive table columns based on position attribute at server end instead UI.

[Vimal Sharma (JIRA)]

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

Vimal Sharma reassigned ATLAS-1163:
---

Assignee: Vimal Sharma

> Sorting of hive table columns based on position attribute at server end 
> instead UI.
> ---
>
> Key: ATLAS-1163
> URL: https://issues.apache.org/jira/browse/ATLAS-1163
> Project: Atlas
>  Issue Type: Bug
>Reporter: Nixon Rodrigues
>Assignee: Vimal Sharma
>
> The UI shouldn't do the sort. Instead we should modify the query used for 
> this (atlas.lineage.schema.query.hive_table=hive_table where __guid='%s'\, 
> columns) to sort by position, so that all clients have the same info. Also, 
> the query should filter deleted columns
> The UI level sort was in done in [ATLAS-1149]



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

Re: Review Request 51800: Support getTrait() API

[Shwetha GS]

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


Fix it, then Ship it!





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


Should be:
Referenceable entity = 
InstanceSerialization.fromJsonReferenceable(entityDefinition, true);
JSONArray traits = new JSONArray();
for (String traitName : entity.getTraits()) {
IStruct trait = entity.getTrait(traitName);
traits.put(new 
JSONObject(InstanceSerialization.toJson(trait, true)));
}


- Shwetha GS


On Sept. 16, 2016, 8:49 a.m., Vimal Sharma wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/51800/
> ---
> 
> (Updated Sept. 16, 2016, 8:49 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Given entity id and trait name, support rest API that returns the trait 
> instance for the entity. Currently, the other way of getting it is 
> getEntity() which returns full entity with all trait instances
> 
> 
> Diffs
> -
> 
>   client/src/main/java/org/apache/atlas/AtlasClient.java 5ed79bc 
>   
> repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java
>  6a937f4 
>   
> repository/src/test/java/org/apache/atlas/service/DefaultMetadataServiceTest.java
>  52dcfde 
>   server-api/src/main/java/org/apache/atlas/services/MetadataService.java 
> 60d8790 
>   webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
> 82016d0 
>   
> webapp/src/test/java/org/apache/atlas/web/resources/EntityJerseyResourceIT.java
>  a1988ef 
> 
> Diff: https://reviews.apache.org/r/51800/diff/
> 
> 
> Testing
> ---
> 
> 
> File Attachments
> 
> 
> ATLAS-712-v2.patch
>   
> https://reviews.apache.org/media/uploaded/files/2016/09/13/b5079426-19d0-48f2-88f7-08e4e645bb32__ATLAS-712-v2.patch
> 
> 
> Thanks,
> 
> Vimal Sharma
> 
>

[jira] [Resolved] (ATLAS-1177) MultipartStream need readBodyDataStream

[shuaib hasan khwaja (JIRA)]

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

shuaib hasan khwaja resolved ATLAS-1177.

Resolution: Resolved

Bug filed in wrong project.

> MultipartStream need readBodyDataStream
> ---
>
> Key: ATLAS-1177
> URL: https://issues.apache.org/jira/browse/ATLAS-1177
> Project: Atlas
>  Issue Type: Improvement
>Reporter: shuaib hasan khwaja
>
> Currently MultipartStream has support for "readBodyData", which basically 
> read the body data and write in out stream. It work great, if plan to have 
> body in memory or write in disk. But not work when you want to upstream some 
> where else.
> Its a good idea to get the InputStream for part body and use it for upload to 
> upstream. Some thing like...
> public InputStream readBodyDataStream(OutputStream output) IOException
> { return newInputStream(); }



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

[jira] [Created] (ATLAS-1177) MultipartStream need readBodyDataStream

[shuaib hasan khwaja (JIRA)]

shuaib hasan khwaja created ATLAS-1177:
--

 Summary: MultipartStream need readBodyDataStream
 Key: ATLAS-1177
 URL: https://issues.apache.org/jira/browse/ATLAS-1177
 Project: Atlas
  Issue Type: Improvement
Reporter: shuaib hasan khwaja


Currently MultipartStream has support for "readBodyData", which basically read 
the body data and write in out stream. It work great, if plan to have body in 
memory or write in disk. But not work when you want to upstream some where else.
Its a good idea to get the InputStream for part body and use it for upload to 
upstream. Some thing like...
public InputStream readBodyDataStream(OutputStream output) IOException
{ return newInputStream(); }



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