[jira] [Commented] (ATLAS-331) UI: Keep UI, Backward compatibility.

[Darshan Kumar (JIRA)]

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

Darshan Kumar commented on ATLAS-331:
-

[~bergenholtz] UI should be backward compatible in a sense that after releasing 
a first version of an application some API response structure is changed. 
In this case, UI code should be written in a way that it should work with both 
the version with released and the new one[changed one]

For example: We had a release of ATLAS as 0.5-incubating. Now in new release 
0.6-incubating backend API [ api/atlas/entity ] response structure is changed. 
So UI code should work with both the releases 0.5-incubating and 
0.6-incubationg.

> UI: Keep UI, Backward compatibility.
> 
>
> Key: ATLAS-331
> URL: https://issues.apache.org/jira/browse/ATLAS-331
> Project: Atlas
>  Issue Type: Task
>Reporter: roshni gadiyar
>Priority: Minor
>  Labels: Atlas-UI
>
> Keep UI, Backward compatibility.



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

[jira] [Updated] (ATLAS-331) UI: Keep UI, Backward compatibility.

[Darshan Kumar (JIRA)]

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

Darshan Kumar updated ATLAS-331:

Description: 
We had a release of ATLAS as 0.5-incubating. Now in new release 0.6-incubating 
backend API [ api/atlas/entity ] response structure is changed. 
So UI code should work with both the releases 0.5-incubating and 0.6-incubating

  was:Keep UI, Backward compatibility.


> UI: Keep UI, Backward compatibility.
> 
>
> Key: ATLAS-331
> URL: https://issues.apache.org/jira/browse/ATLAS-331
> Project: Atlas
>  Issue Type: Task
>Reporter: roshni gadiyar
>Priority: Minor
>  Labels: Atlas-UI
>
> We had a release of ATLAS as 0.5-incubating. Now in new release 
> 0.6-incubating backend API [ api/atlas/entity ] response structure is 
> changed. 
> So UI code should work with both the releases 0.5-incubating and 
> 0.6-incubating



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

[jira] [Assigned] (ATLAS-324) UI: In Create tag add multiplicity,data type attribute.

[Darshan Kumar (JIRA)]

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

Darshan Kumar reassigned ATLAS-324:
---

Assignee: Darshan Kumar

> UI: In Create tag add multiplicity,data type attribute.
> ---
>
> Key: ATLAS-324
> URL: https://issues.apache.org/jira/browse/ATLAS-324
> Project: Atlas
>  Issue Type: Task
>Reporter: roshni gadiyar
>Assignee: Darshan Kumar
>Priority: Minor
>  Labels: Atlas-UI
>
> In Create tag add multiplicity,data type attribute.



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

RE: [jira] [Commented] (ATLAS-199) webapp build fails (grunt + tests)

[sonali.parthasarathy]

Thanks Hemanth!

I can access the nightly build. Downloading it now.

Thanks!
Sonali

-Original Message-
From: Hemanth Yamijala [mailto:yhema...@gmail.com]
Sent: November 18, 2015 9:20 PM
To: dev@atlas.incubator.apache.org
Subject: Re: [jira] [Commented] (ATLAS-199) webapp build fails (grunt + tests)

It appears you can download the binary bits that come off master from the 
nightly builds that are published here:
https://builds.apache.org/job/apache-atlas-nightly/ - Can you check if this is 
accessible for you?

Thanks
Hemanth

On Thu, Nov 19, 2015 at 10:18 AM, Hemanth Yamijala 
wrote:

> Sonali,
>
> ALTAS-159 & ATLAS-199 are merged with the master branch. However, the
> status of ATLAS-199 is still open, so I assume some work is still
> pending on it (which might also be why you are still seeing the
> error). The only release of the project we’ve had is the 0.5 version,
> and for it I only see the source tarballs here (
> http://www.eu.apache.org/dist/incubator/atlas/0.5.0-incubating/). Will
> check and get back to you if there is a better option for you to get
> started.
>
> In the meantime, can you please update ATLAS-199 with the errors you
> observed when building (- from master branch, I assume?). Any log etc
> that you have may help in getting to resolution.
>
> Thanks
>
> Hemanth
>
> On Thu, Nov 19, 2015 at 4:31 AM, 
> wrote:
>
>> Hi Team,
>>
>> Is there a pre-compiled version of atlas I can use in the meantime?
>>
>> Thanks,
>> Sonali
>>
>> -Original Message-
>> From: Parthasarathy, Sonali
>> Sent: November 17, 2015 4:39 PM
>> To: dev@atlas.incubator.apache.org
>> Subject: RE: [jira] [Commented] (ATLAS-199) webapp build fails (grunt
>> +
>> tests)
>>
>> Hi!
>>
>> I cloned the repo from git today and tried compiling atlas, but I get
>> the same 'grunt bower --no-color' failed error. Have the JIRAs 159
>> and 199 been merged to the git code? Or Do I have to apply the patch 
>> separately?
>>
>> Thanks,
>> Sonali
>>
>> -Original Message-
>> From: Darshan Kumar (JIRA) [mailto:j...@apache.org]
>> Sent: October 26, 2015 5:26 AM
>> To: dev@atlas.incubator.apache.org
>> Subject: [jira] [Commented] (ATLAS-199) webapp build fails (grunt +
>> tests)
>>
>>
>> [
>> https://issues.apache.org/jira/browse/ATLAS-199?page=com.atlassian.ji
>> ra.plugin.system.issuetabpanels:comment-tabpanel=149
>> 74130#comment-14974130
>> ]
>>
>> Darshan Kumar commented on ATLAS-199:
>> -
>>
>> Sure will look into it Thanks [~suma.shivaprasad]
>>
>> > webapp build fails (grunt + tests)
>> > --
>> >
>> > Key: ATLAS-199
>> > URL: https://issues.apache.org/jira/browse/ATLAS-199
>> > Project: Atlas
>> >  Issue Type: Bug
>> >Affects Versions: 0.6-incubating
>> >Reporter: Erik Bergenholtz
>> >Assignee: Darshan Kumar
>> >Priority: Critical
>> >  Labels: patch-available
>> > Fix For: 0.6-incubating
>> >
>> > Attachments: ATLAS-199-v0.patch
>> >
>> >
>> > When building Atlas webapp, I see the following issues:
>> > mvn clean install:
>> > {code}
>> > [INFO] Running 'grunt bower --no-color' in
>> > /Users/ebergenholtz/git3/incubator-atlas/dashboard
>> > [INFO]
>> > ---
>> > ---
>> > --
>> > [INFO] BUILD FAILURE
>> > [INFO]
>> > ---
>> > ---
>> > --
>> > [INFO] Total time: 34.282 s
>> > [INFO] Finished at: 2015-09-30T13:55:30-05:00 [INFO] Final Memory:
>> > 35M/420M [INFO]
>> > ---
>> > ---
>> > -- [ERROR] Failed to execute goal
>> > com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (install
>> > bower) on project atlas-webapp: Failed to run task: 'grunt bower 
>> > --no-color'
>> > failed. java.io.IOException: Cannot run program
>> "/Users/ebergenholtz/git3/incubator-atlas/dashboard/node/node" (in
>> directory "/Users/ebergenholtz/git3/incubator-atlas/dashboard"):
>> error=2, No such file or directory -> [Help 1] {code} Also, if I
>> bypass the grunt task some of the tests fail.
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.4#6332)
>>
>> 
>>
>> This message is for the designated recipient only and may contain
>> privileged, proprietary, or otherwise confidential information. If
>> you have received it in error, please notify the sender immediately
>> and delete the original. Any other use of the e-mail by you is
>> prohibited. Where allowed by local law, electronic communications
>> with Accenture and its affiliates, including e-mail and instant
>> messaging (including content), may be scanned by our systems for the
>> purposes of information security and assessment of internal compliance with 
>> Accenture policy.
>>
>> 

[jira] [Commented] (ATLAS-187) DSL - Fix issues while loading arrays in a select expression

[Thiyagarajan Gnanasekaran (JIRA)]

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

Thiyagarajan Gnanasekaran commented on ATLAS-187:
-

We need to ascertain one more thing.

The resulting JSON is displaying objects of type "hive_column". It has the 
desired 6 rows.

But the Class Object "hive_column" is not expanded to show its members  "name", 
"dataType" & "comment" in the JSON object. Only its "id", "typename" & 
"version" as shown in the result below ?.

Is the result object correct ? or the JSON result object needs to be corrected ?

==
results = {"query":"StorageDesc as _src1 select _src1 cols as 
cols","dataType":{"typeName":"__tempQueryResultStruct36","attributeDefinitions":[{"name":"cols","dataTypeName":"hive_column","multiplicity":{"lower":0,"upper":1,"isUnique":false},"isComposite":false,"isUnique":false,"isIndexable":true,"reverseAttributeName":null}]},"rows":[{"$typeName$":"__tempQueryResultStruct36","cols":{"id":"100f5797-fda8-4474-985d-6a0d21859d17","$typeName$":"hive_column","version":0}},{"$typeName$":"__tempQueryResultStruct36","cols":{"id":"d21c3c2b-e99a-4344-bf45-bab3eaea109c","$typeName$":"hive_column","version":0}},{"$typeName$":"__tempQueryResultStruct36","cols":{"id":"3e50f026-c980-4b3a-91cd-fc3f23562de2","$typeName$":"hive_column","version":0}},{"$typeName$":"__tempQueryResultStruct36","cols":{"id":"ec1b3632-c6f4-48d0-861b-9c5e7676fc39","$typeName$":"hive_column","version":0}},{"$typeName$":"__tempQueryResultStruct36","cols":{"id":"2af3a595-17c0-4591-907d-ed9c86957460","$typeName$":"hive_column","version":0}},{"$typeName$":"__tempQueryResultStruct36","cols":{"id":"4211e851-ab62-40ac-9b32-91af5fbcdded","$typeName$":"hive_column","version":0}}]}
==
query [StorageDesc select cols] returned [6] rows
==

>  DSL - Fix issues while loading arrays in a select expression
> -
>
> Key: ATLAS-187
> URL: https://issues.apache.org/jira/browse/ATLAS-187
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Thiyagarajan Gnanasekaran
> Attachments: atlas-187.patch
>
>
> Currently the loading of lists is not supported and throws an Exception while 
> trying to do do. eg query : StorageDesc cols in 
> GraphBackedDiscoveryServiceTest



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

[jira] [Updated] (ATLAS-162) UI: Full text search

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-162:
--
Summary: UI: Full text search   (was: Full text search )

> UI: Full text search 
> -
>
> Key: ATLAS-162
> URL: https://issues.apache.org/jira/browse/ATLAS-162
> Project: Atlas
>  Issue Type: Task
>Reporter: Darshan Kumar
>Assignee: Darshan Kumar
>




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

[jira] [Updated] (ATLAS-125) Inputs not being set for a hive_process on a plain select query

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-125:
--
Labels: ATLAS-UI-BUGS  (was: )

> Inputs not being set for a hive_process on a plain select query
> ---
>
> Key: ATLAS-125
> URL: https://issues.apache.org/jira/browse/ATLAS-125
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Rohit
>Priority: Critical
>  Labels: ATLAS-UI-BUGS
> Attachments: screenshot-1.png
>
>




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

[jira] [Updated] (ATLAS-170) Result of search based on attributes of a Traits is not displayed correctly

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-170:
---
Priority: Blocker  (was: Critical)

> Result of search based on attributes of a Traits is not displayed correctly
> ---
>
> Key: ATLAS-170
> URL: https://issues.apache.org/jira/browse/ATLAS-170
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating
> Environment: HDP2.3.1
>Reporter: Herman Yu
>Assignee: Rohit
>Priority: Blocker
>  Labels: ATLAS-UI-BUGS
> Attachments: screenshot-1.png
>
>
> when search based on an attribute of a trait, it returns the correct # of 
> entities found, but list of matched entities are not shown.
> for example, a traits ("mytrait") is defined with an attribute (myTraitAttr). 
> then associate this trait to an entity with "myvalue" as the value of the 
> attribute. When search with "mytrait.myTraitAttr="myvalue"", it returns 1 
> record matched, but doesn't show the entity in the list. 



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

[jira] [Updated] (ATLAS-177) Save search History

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-177:
--
Labels: ATLAS-UI-BUGS  (was: )

> Save search History
> ---
>
> Key: ATLAS-177
> URL: https://issues.apache.org/jira/browse/ATLAS-177
> Project: Atlas
>  Issue Type: Bug
>Reporter: Darshan Kumar
>Assignee: Darshan Kumar
>  Labels: ATLAS-UI-BUGS
>




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

[jira] [Updated] (ATLAS-139) DSL - Fix issues while loading maps during select

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-139:
---
Assignee: (was: Suma Shivaprasad)

> DSL - Fix issues while loading maps during select
> -
>
> Key: ATLAS-139
> URL: https://issues.apache.org/jira/browse/ATLAS-139
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Suma Shivaprasad
>




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

[jira] [Resolved] (ATLAS-143) resultMapping for DSL queries

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad resolved ATLAS-143.

Resolution: Duplicate

> resultMapping for DSL queries
> -
>
> Key: ATLAS-143
> URL: https://issues.apache.org/jira/browse/ATLAS-143
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>
> For a DSL query like - Table as t where name='sales_fact', db where 
> name='Reporting', its mapped to - Table as t where (name = "sales_fact") db 
> where (name = "Reporting") as _src1 select t as _col_0, and the results are 
> available in json with key '_col_0'. It should be mapped to 't' as its 
> specified in the user query



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

[jira] [Updated] (ATLAS-170) Result of search based on attributes of a Traits is not displayed correctly

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-170:
--
Labels: UI  (was: )

> Result of search based on attributes of a Traits is not displayed correctly
> ---
>
> Key: ATLAS-170
> URL: https://issues.apache.org/jira/browse/ATLAS-170
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating
> Environment: HDP2.3.1
>Reporter: Herman Yu
>Assignee: Rohit
>Priority: Critical
>  Labels: ATLAS-UI-BUGS
> Attachments: screenshot-1.png
>
>
> when search based on an attribute of a trait, it returns the correct # of 
> entities found, but list of matched entities are not shown.
> for example, a traits ("mytrait") is defined with an attribute (myTraitAttr). 
> then associate this trait to an entity with "myvalue" as the value of the 
> attribute. When search with "mytrait.myTraitAttr="myvalue"", it returns 1 
> record matched, but doesn't show the entity in the list. 



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

[jira] [Updated] (ATLAS-198) Atlas UI Requires Internet Access

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-198:
--
Labels: ATLAS-UI-BUGS  (was: )

> Atlas UI Requires Internet Access
> -
>
> Key: ATLAS-198
> URL: https://issues.apache.org/jira/browse/ATLAS-198
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating, 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Sanjay Patel
>Priority: Blocker
>  Labels: ATLAS-UI-BUGS
> Fix For: 0.6-incubating
>
> Attachments: 0.5_ATLAS-198_v1.patch, 0.6_ATLAS-198_v1.patch, 
> 0.6_ATLAS-198_v2.patch
>
>
> PROBLEM: Web resources are being sourced from the internet for the Atlas web 
> application. Installations do not necessarily have internet access. This 
> results in a timeout for the requested resources. These resources need to be 
> moved into atlas.war so the resources can be served up by the Atlas web 
> application.
> The list needs to be verified, but includes at least:
> http://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/css/bootstrap.min.css 
> http://cdnjs.cloudflare.com/ajax/libs/d3/3.5.5/d3.min.js 
> The fix needs to bundle resources such that Atlas web-app can be utilized 
> without internet connectivity.
> The issue needs to be fixed in master and requires patch for 0.5



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

[jira] [Updated] (ATLAS-170) Result of search based on attributes of a Traits is not displayed correctly

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-170:
--
Labels: ATLAS-UI-BUGS  (was: UI)

> Result of search based on attributes of a Traits is not displayed correctly
> ---
>
> Key: ATLAS-170
> URL: https://issues.apache.org/jira/browse/ATLAS-170
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.5-incubating
> Environment: HDP2.3.1
>Reporter: Herman Yu
>Assignee: Rohit
>Priority: Critical
>  Labels: ATLAS-UI-BUGS
> Attachments: screenshot-1.png
>
>
> when search based on an attribute of a trait, it returns the correct # of 
> entities found, but list of matched entities are not shown.
> for example, a traits ("mytrait") is defined with an attribute (myTraitAttr). 
> then associate this trait to an entity with "myvalue" as the value of the 
> attribute. When search with "mytrait.myTraitAttr="myvalue"", it returns 1 
> record matched, but doesn't show the entity in the list. 



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

[jira] [Updated] (ATLAS-108) UI: integrate ng-inputs-tag library to select super types from types available for autocomeplete

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-108:
--
Labels: ATLAS-UI-BUGS  (was: )

> UI: integrate ng-inputs-tag library to select super types from types 
> available for autocomeplete
> 
>
> Key: ATLAS-108
> URL: https://issues.apache.org/jira/browse/ATLAS-108
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Rohit
>  Labels: ATLAS-UI-BUGS
> Fix For: 0.6-incubating
>
>
> To be detailed.



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

[jira] [Commented] (ATLAS-258) Lineage api performance issue

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-258:


Can you add some comments?

> Lineage api performance issue 
> --
>
> Key: ATLAS-258
> URL: https://issues.apache.org/jira/browse/ATLAS-258
> Project: Atlas
>  Issue Type: Bug
>Reporter: Darshan Kumar
>Assignee: Anilsg
>




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

[jira] [Updated] (ATLAS-187) DSL - Fix issues while loading arrays in a select expression

[Thiyagarajan Gnanasekaran (JIRA)]

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

Thiyagarajan Gnanasekaran updated ATLAS-187:

Attachment: atlas-187.patch

Code Patch for Atlas 187

>  DSL - Fix issues while loading arrays in a select expression
> -
>
> Key: ATLAS-187
> URL: https://issues.apache.org/jira/browse/ATLAS-187
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
> Attachments: atlas-187.patch
>
>
> Currently the loading of lists is not supported and throws an Exception while 
> trying to do do. eg query : StorageDesc cols in 
> GraphBackedDiscoveryServiceTest



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

[jira] [Assigned] (ATLAS-187) DSL - Fix issues while loading arrays in a select expression

[Thiyagarajan Gnanasekaran (JIRA)]

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

Thiyagarajan Gnanasekaran reassigned ATLAS-187:
---

Assignee: Thiyagarajan Gnanasekaran

>  DSL - Fix issues while loading arrays in a select expression
> -
>
> Key: ATLAS-187
> URL: https://issues.apache.org/jira/browse/ATLAS-187
> Project: Atlas
>  Issue Type: Bug
>Reporter: Suma Shivaprasad
>Assignee: Thiyagarajan Gnanasekaran
> Attachments: atlas-187.patch
>
>
> Currently the loading of lists is not supported and throws an Exception while 
> trying to do do. eg query : StorageDesc cols in 
> GraphBackedDiscoveryServiceTest



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