[jira] [Comment Edited] (ATLAS-1877) UI: In Lineage for Process entity process icon is not showing.
[
https://issues.apache.org/jira/browse/ATLAS-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051850#comment-16051850
]
Keval Bhatt edited comment on ATLAS-1877 at 6/16/17 1:00 PM:
-
[~xiaqinglin] If entity it self is a Process or entity super type is process
then there is no need to check further.
you will check if it is not at first level or its is not a Process it self.
The above JSON Is list of Types (i.e entityDef) so you need to create one type
which is derived from Load Process.
and the create a entity from newly created type.
Steps.
# Create a type which has superType as LoadProcess .
URL - http://localhost:/api/atlas/v2/types/typedefs
{code} {
"entityDefs": [{
"category": "ENTITY",
"version": 1,
"name": "child_loadProcess",
"description": "child of load process",
"typeVersion": "1.0",
"attributeDefs": [{
"name": "test_att",
"typeName": "string",
"isOptional": false,
"cardinality": "SINGLE",
"valuesMinCount": 1,
"valuesMaxCount": 1,
"isUnique": false,
"isIndexable": true
}
],
"superTypes": [
"LoadProcess"
]
}
]
}
{code}
# Now create a entity from this newly created type.
# Then use this entity for Lineage.
For more details please go through atlas [Type
system|http://atlas.incubator.apache.org/TypeSystem.html] and [Rest API
|http://atlas.incubator.apache.org/api/v2/index.html] documentation
was (Author: kevalbhatt18):
[~xiaqinglin] If entity it self is a Process or entity super type is process
then there is no need to check further.
you will check if it is not at first level or its is not a Process it self.
The above JSON Is list of Types (i.e entityDef) so you need to create one type
which is derived from Load Process.
and the create a entity from newly created type.
Steps.
# Create a type which has superType as LoadProcess .
URL - http://localhost:/api/atlas/v2/types/typedefs
{code} {
"entityDefs": [{
"category": "ENTITY",
"version": 1,
"name": "child_loadProcess",
"description": "child of load process",
"typeVersion": "1.0",
"attributeDefs": [{
"name": "test_att",
"typeName": "string",
"isOptional": false,
"cardinality": "SINGLE",
"valuesMinCount": 1,
"valuesMaxCount": 1,
"isUnique": false,
"isIndexable": true
}
],
"superTypes": [
"LoadProcess"
]
}
]
}
{code}
# Now create a entity from this newly created type.
# Then use this entity for Lineage.
For more details please go through atlas [Type system
documentation|http://atlas.incubator.apache.org/TypeSystem.html] and [Rest API
|http://atlas.incubator.apache.org/api/v2/index.html]
> UI: In Lineage for Process entity process icon is not showing.
> --
>
> Key: ATLAS-1877
> URL: https://issues.apache.org/jira/browse/ATLAS-1877
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: qinglin,xia
> Labels: atlas
> Fix For: trunk, 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1877.patch, Process_Icon_Fixed.png,
> wrong_process_icon.png
>
>
> UI should check Process entity in all parent superType, right know its
> checking for only 1 level
> Step to reproduce :
> # Run quickstart
> # Create entity of type Process and while creating process select time_dim
> (Table entity) as a input and output.
> # Now got to sales_fact_monthly_mv entity and you will see new output (Please
> find attached screenshot )
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (ATLAS-1877) UI: In Lineage for Process entity process icon is not showing.
[
https://issues.apache.org/jira/browse/ATLAS-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051850#comment-16051850
]
Keval Bhatt edited comment on ATLAS-1877 at 6/16/17 12:59 PM:
--
[~xiaqinglin] If entity it self is a Process or entity super type is process
then there is no need to check further.
you will check if it is not at first level or its is not a Process it self.
The above JSON Is list of Types (i.e entityDef) so you need to create one type
which is derived from Load Process.
and the create a entity from newly created type.
Steps.
# Create a type which has superType as LoadProcess .
URL - http://localhost:/api/atlas/v2/types/typedefs
{code} {
"entityDefs": [{
"category": "ENTITY",
"version": 1,
"name": "child_loadProcess",
"description": "child of load process",
"typeVersion": "1.0",
"attributeDefs": [{
"name": "test_att",
"typeName": "string",
"isOptional": false,
"cardinality": "SINGLE",
"valuesMinCount": 1,
"valuesMaxCount": 1,
"isUnique": false,
"isIndexable": true
}
],
"superTypes": [
"LoadProcess"
]
}
]
}
{code}
# Now create a entity from this newly created type.
# Then use this entity for Lineage.
For more details please go through atlas [Type system
documentation|http://atlas.incubator.apache.org/TypeSystem.html] and [Rest API
|http://atlas.incubator.apache.org/api/v2/index.html]
was (Author: kevalbhatt18):
[~xiaqinglin] If entity it self is a Process or entity super type is process
then there is no need to check further.
you will check if it is not at first level or its is not a Process it self.
The above JSON Is list of Types (i.e entityDef) so you need to create one type
which is derived from Load Process.
and the create a entity from newly created type.
Steps.
# Create a type which has superType as LoadProcess .
URL - http://localhost:/api/atlas/v2/types/typedefs
{code} {
"entityDefs": [{
"category": "ENTITY",
"version": 1,
"name": "child_loadProcess",
"description": "child of load process",
"typeVersion": "1.0",
"attributeDefs": [{
"name": "test_att",
"typeName": "string",
"isOptional": false,
"cardinality": "SINGLE",
"valuesMinCount": 1,
"valuesMaxCount": 1,
"isUnique": false,
"isIndexable": true
}
],
"superTypes": [
"LoadProcess"
]
}
]
}
{code}
# Now create a entity from this newly created type.
# Then use this entity for Lineage.
> UI: In Lineage for Process entity process icon is not showing.
> --
>
> Key: ATLAS-1877
> URL: https://issues.apache.org/jira/browse/ATLAS-1877
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: qinglin,xia
> Labels: atlas
> Fix For: trunk, 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1877.patch, Process_Icon_Fixed.png,
> wrong_process_icon.png
>
>
> UI should check Process entity in all parent superType, right know its
> checking for only 1 level
> Step to reproduce :
> # Run quickstart
> # Create entity of type Process and while creating process select time_dim
> (Table entity) as a input and output.
> # Now got to sales_fact_monthly_mv entity and you will see new output (Please
> find attached screenshot )
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-1877) UI: In Lineage for Process entity process icon is not showing.
[
https://issues.apache.org/jira/browse/ATLAS-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051850#comment-16051850
]
Keval Bhatt commented on ATLAS-1877:
[~xiaqinglin] If entity it self is a Process or entity super type is process
then there is no need to check further.
you will check if it is not at first level or its is not a Process it self.
The above JSON Is list of Types (i.e entityDef) so you need to create one type
which is derived from Load Process.
and the create a entity from newly created type.
Steps.
# Create a type which has superType as LoadProcess .
URL - http://localhost:/api/atlas/v2/types/typedefs
{code} {
"entityDefs": [{
"category": "ENTITY",
"version": 1,
"name": "child_loadProcess",
"description": "child of load process",
"typeVersion": "1.0",
"attributeDefs": [{
"name": "test_att",
"typeName": "string",
"isOptional": false,
"cardinality": "SINGLE",
"valuesMinCount": 1,
"valuesMaxCount": 1,
"isUnique": false,
"isIndexable": true
}
],
"superTypes": [
"LoadProcess"
]
}
]
}
{code}
# Now create a entity from this newly created type.
# Then use this entity for Lineage.
> UI: In Lineage for Process entity process icon is not showing.
> --
>
> Key: ATLAS-1877
> URL: https://issues.apache.org/jira/browse/ATLAS-1877
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: qinglin,xia
> Labels: atlas
> Fix For: trunk, 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1877.patch, Process_Icon_Fixed.png,
> wrong_process_icon.png
>
>
> UI should check Process entity in all parent superType, right know its
> checking for only 1 level
> Step to reproduce :
> # Run quickstart
> # Create entity of type Process and while creating process select time_dim
> (Table entity) as a input and output.
> # Now got to sales_fact_monthly_mv entity and you will see new output (Please
> find attached screenshot )
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (ATLAS-1877) UI: In Lineage for Process entity process icon is not showing.
[
https://issues.apache.org/jira/browse/ATLAS-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051636#comment-16051636
]
Keval Bhatt edited comment on ATLAS-1877 at 6/16/17 9:22 AM:
-
[~xiaqinglin] In master we checking only one level of [superType |
https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/graph/LineageLayoutView.js#L128].
so if any entity which is derived from more then 1 level and Process entity is
not in first level the it will not work. To fix this issue you should check for
current entity is process or not and if it is not then search for all the
nested superType to check whether it has process entity in it.
Example:
{code}
[{
category:"ENTITY",
superTypes:['e2'],
name:"e1",
},
{
category:"ENTITY",
superTypes:['e3'],
name:"e2",
..
},{
category:"ENTITY",
superTypes:["Process"],
name:"e3",
..
},{
category:"ENTITY",
superTypes:[],
name:"Process",
..
}]
{code}
So now to check *e1* entity is process or not, you need to check in e2 -> e3
and in e3 you have process entity so e1 is process.
*Note:* To get all the nested type please use this
[Utility|https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js#L245]
function.
was (Author: kevalbhatt18):
[~xiaqinglin] In master we checking only one level of [superType |
https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/graph/LineageLayoutView.js#L128].
so if any entity which is derived from more then 1 level and Process entity is
not in first level the it will not work. To fix this issue you should check for
current entity is process or not and if it is not then search for all the
nested superType to check whether it has process entity in it.
Example:
{code}
[{
category:"ENTITY",
superTypes:['e2'],
name:"e1",
},
{
category:"ENTITY",
superTypes:['e3'],
name:"e2",
..
},{
category:"ENTITY",
superTypes:["'Process"],
name:"e3",
..
},{
category:"ENTITY",
superTypes:[],
name:"Process",
..
}]
{code}
So now to check *e1* entity is process or not, you need to check in e2 -> e3
and in e3 you have process entity so e1 is process.
*Note:* To get all the nested type please use this
[Utility|https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js#L245]
function.
> UI: In Lineage for Process entity process icon is not showing.
> --
>
> Key: ATLAS-1877
> URL: https://issues.apache.org/jira/browse/ATLAS-1877
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: qinglin,xia
> Labels: atlas
> Fix For: trunk, 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1877.patch, Process_Icon_Fixed.png,
> wrong_process_icon.png
>
>
> UI should check Process entity in all parent superType, right know its
> checking for only 1 level
> Step to reproduce :
> # Run quickstart
> # Create entity of type Process and while creating process select time_dim
> (Table entity) as a input and output.
> # Now got to sales_fact_monthly_mv entity and you will see new output (Please
> find attached screenshot )
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (ATLAS-1877) UI: In Lineage for Process entity process icon is not showing.
[
https://issues.apache.org/jira/browse/ATLAS-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051636#comment-16051636
]
Keval Bhatt edited comment on ATLAS-1877 at 6/16/17 9:22 AM:
-
[~xiaqinglin] In master we checking only one level of [superType |
https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/graph/LineageLayoutView.js#L128].
so if any entity which is derived from more then 1 level and Process entity is
not in first level the it will not work. To fix this issue you should check for
current entity is process or not and if it is not then search for all the
nested superType to check whether it has process entity in it.
Example:
{code}
[{
category:"ENTITY",
superTypes:['e2'],
name:"e1",
},
{
category:"ENTITY",
superTypes:['e3'],
name:"e2",
..
},{
category:"ENTITY",
superTypes:["'Process"],
name:"e3",
..
},{
category:"ENTITY",
superTypes:[],
name:"Process",
..
}]
{code}
So now to check *e1* entity is process or not, you need to check in e2 -> e3
and in e3 you have process entity so e1 is process.
*Note:* To get all the nested type please use this
[Utility|https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js#L245]
function.
was (Author: kevalbhatt18):
[~xiaqinglin] In master we checking only one level of [superType |
https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/graph/LineageLayoutView.js#L128].
so if any entity which is derived from more then 1 level and Process entity is
not in first level the it will not work. To fix this issue you should check for
current entity is process or not and if it is not then search for all the
nested superType to check whether it has process entity in it.
Example:
{code}
[{
category:"ENTITY",
superTypes:['e2'],
name:"e1",
},
{
category:"ENTITY",
superTypes:['e3'],
name:"e2",
..
},{
category:"ENTITY",
superTypes:[''Process"],
name:"e3",
..
},,{
category:"ENTITY",
superTypes:[],
name:"Process",
..
}]
{code}
So now to check *e1* entity is process or not, you need to check in e2 -> e3
and in e3 you have process entity so e1 is process.
*Note:* To get all the nested type please use this
[Utility|https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js#L245]
function.
> UI: In Lineage for Process entity process icon is not showing.
> --
>
> Key: ATLAS-1877
> URL: https://issues.apache.org/jira/browse/ATLAS-1877
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: qinglin,xia
> Labels: atlas
> Fix For: trunk, 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1877.patch, Process_Icon_Fixed.png,
> wrong_process_icon.png
>
>
> UI should check Process entity in all parent superType, right know its
> checking for only 1 level
> Step to reproduce :
> # Run quickstart
> # Create entity of type Process and while creating process select time_dim
> (Table entity) as a input and output.
> # Now got to sales_fact_monthly_mv entity and you will see new output (Please
> find attached screenshot )
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (ATLAS-1877) UI: In Lineage for Process entity process icon is not showing.
[
https://issues.apache.org/jira/browse/ATLAS-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051636#comment-16051636
]
Keval Bhatt edited comment on ATLAS-1877 at 6/16/17 9:12 AM:
-
[~xiaqinglin] In master we checking only one level of [superType |
https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/graph/LineageLayoutView.js#L128].
so if any entity which is derived from more then 1 level and Process entity is
not in first level the it will not work. To fix this issue you should check for
current entity is process or not and if it is not then search for all the
nested superType to check whether it has process entity in it.
Example:
{code}
[{
category:"ENTITY",
superTypes:['e2'],
name:"e1",
},
{
category:"ENTITY",
superTypes:['e3'],
name:"e2",
..
},{
category:"ENTITY",
superTypes:[''Process"],
name:"e3",
..
},,{
category:"ENTITY",
superTypes:[],
name:"Process",
..
}]
{code}
So now to check *e1* entity is process or not, you need to check in e2 -> e3
and in e3 you have process entity so e1 is process.
*Note:* To get all the nested type please use this
[Utility|https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js#L245]
function.
was (Author: kevalbhatt18):
[~xiaqinglin] In master we checking only one level of [superType |
https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/graph/LineageLayoutView.js#L128].
so if any entity which is derived from more then 1 level and Process entity is
not in first level the it will not work. To fix this issue you should check for
current entity is process or not and if it is not then search for all the
nested superType to check whether it has process entity in it.
Example:
{code}
[{
category:"ENTITY",
superTypes:['e2'],
name:"e1",
},
{
category:"ENTITY",
superTypes:['e3'],
name:"e2",
..
},{
category:"ENTITY",
superTypes:[''Process"],
name:"e3",
..
},,{
category:"ENTITY",
superTypes:[],
name:"Process",
..
}]
{code}
So now to check *e1* entity is process or not, you need to check in e2 -> e3
and in e3 you have process entity so e1 is process.
To get all the nested type please follow this
[Utility|https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js#L245]
> UI: In Lineage for Process entity process icon is not showing.
> --
>
> Key: ATLAS-1877
> URL: https://issues.apache.org/jira/browse/ATLAS-1877
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: qinglin,xia
> Labels: atlas
> Fix For: trunk, 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1877.patch, Process_Icon_Fixed.png,
> wrong_process_icon.png
>
>
> UI should check Process entity in all parent superType, right know its
> checking for only 1 level
> Step to reproduce :
> # Run quickstart
> # Create entity of type Process and while creating process select time_dim
> (Table entity) as a input and output.
> # Now got to sales_fact_monthly_mv entity and you will see new output (Please
> find attached screenshot )
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (ATLAS-1877) UI: In Lineage for Process entity process icon is not showing.
[
https://issues.apache.org/jira/browse/ATLAS-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051636#comment-16051636
]
Keval Bhatt edited comment on ATLAS-1877 at 6/16/17 9:10 AM:
-
[~xiaqinglin] In master we checking only one level of [superType |
https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/graph/LineageLayoutView.js#L128].
so if any entity which is derived from more then 1 level and Process entity is
not in first level the it will not work. To fix this issue you should check for
current entity is process or not and if it is not then search for all the
nested superType to check whether it has process entity in it.
Example:
{code}
[{
category:"ENTITY",
superTypes:['e2'],
name:"e1",
},
{
category:"ENTITY",
superTypes:['e3'],
name:"e2",
..
},{
category:"ENTITY",
superTypes:[''Process"],
name:"e3",
..
},,{
category:"ENTITY",
superTypes:[],
name:"Process",
..
}]
{code}
So now to check *e1* entity is process or not, you need to check in e2 -> e3
and in e3 you have process entity so e1 is process.
To get all the nested type please follow this
[Utility|https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js#L245]
was (Author: kevalbhatt18):
[~xiaqinglin] In master we checking only one level of [superType |
https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/graph/LineageLayoutView.js#L128].
so if any entity which is derived from more then 1 level and Process entity is
not in first level the it will not work. To fix this issue you should check for
current entity is process or not and if it is not then search for all the
nested superType to check whether it has process entity in it.
Example:
{code}
[{
category:"ENTITY",
superTypes:['e2'],
name:"e1",
},
{
category:"ENTITY",
superTypes:['e3'],
name:"e2",
..
},{
category:"ENTITY",
superTypes:[''Process"],
name:"e3",
..
},,{
category:"ENTITY",
superTypes:[],
name:"Process",
..
}]
{code}
So now to check *e1* entity is process or not, you need to check in e2 -> e3
and in e3 you have process entity so e1 is process.
> UI: In Lineage for Process entity process icon is not showing.
> --
>
> Key: ATLAS-1877
> URL: https://issues.apache.org/jira/browse/ATLAS-1877
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: qinglin,xia
> Labels: atlas
> Fix For: trunk, 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1877.patch, Process_Icon_Fixed.png,
> wrong_process_icon.png
>
>
> UI should check Process entity in all parent superType, right know its
> checking for only 1 level
> Step to reproduce :
> # Run quickstart
> # Create entity of type Process and while creating process select time_dim
> (Table entity) as a input and output.
> # Now got to sales_fact_monthly_mv entity and you will see new output (Please
> find attached screenshot )
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-1877) UI: In Lineage for Process entity process icon is not showing.
[
https://issues.apache.org/jira/browse/ATLAS-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051636#comment-16051636
]
Keval Bhatt commented on ATLAS-1877:
[~xiaqinglin] In master we checking only one level of [superType |
https://github.com/apache/incubator-atlas/blob/master/dashboardv2/public/js/views/graph/LineageLayoutView.js#L128].
so if any entity which is derived from more then 1 level and Process entity is
not in first level the it will not work. To fix this issue you should check for
current entity is process or not and if it is not then search for all the
nested superType to check whether it has process entity in it.
Example:
{code}
[{
category:"ENTITY",
superTypes:['e2'],
name:"e1",
},
{
category:"ENTITY",
superTypes:['e3'],
name:"e2",
..
},{
category:"ENTITY",
superTypes:[''Process"],
name:"e3",
..
},,{
category:"ENTITY",
superTypes:[],
name:"Process",
..
}]
{code}
So now to check *e1* entity is process or not, you need to check in e2 -> e3
and in e3 you have process entity so e1 is process.
> UI: In Lineage for Process entity process icon is not showing.
> --
>
> Key: ATLAS-1877
> URL: https://issues.apache.org/jira/browse/ATLAS-1877
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 0.8-incubating
>Reporter: Keval Bhatt
>Assignee: qinglin,xia
> Labels: atlas
> Fix For: trunk, 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1877.patch, Process_Icon_Fixed.png,
> wrong_process_icon.png
>
>
> UI should check Process entity in all parent superType, right know its
> checking for only 1 level
> Step to reproduce :
> # Run quickstart
> # Create entity of type Process and while creating process select time_dim
> (Table entity) as a input and output.
> # Now got to sales_fact_monthly_mv entity and you will see new output (Please
> find attached screenshot )
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-1877) UI: In Lineage for Process entity process icon is not showing.
[ https://issues.apache.org/jira/browse/ATLAS-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1877: --- Attachment: wrong_process_icon.png > UI: In Lineage for Process entity process icon is not showing. > -- > > Key: ATLAS-1877 > URL: https://issues.apache.org/jira/browse/ATLAS-1877 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: wrong_process_icon.png > > > UI should check Process entity in all parent superType, right know its > checking for only 1 level > Step to reproduce : > # Run quickstart > # Create entity of type Process and while creating process select time_dim > (Table entity) as a input and output. > # Now got to sales_fact_monthly_mv entity and you will see new output (Please > find attached screenshot ) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1877) UI: In Lineage for Process entity process icon is not showing.
[ https://issues.apache.org/jira/browse/ATLAS-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1877: --- Description: UI should check Process entity in all parent superType, right know its checking for only 1 level Step to reproduce : # Run quickstart # Create entity of type Process and while creating process select time_dim (Table entity) as a input and output. # Now got to sales_fact_monthly_mv entity and you will see new output (Please find attached screenshot ) was: UI should check Process entity in all parent superType, right know its checking for only 1 level Step to reproduce : # Run quickstart # Create entity of type Process and while creating process select time_dim (Table entity) as a input and output. # Now got to time_dim entity and you will see new output (Please find attached screenshot ) > UI: In Lineage for Process entity process icon is not showing. > -- > > Key: ATLAS-1877 > URL: https://issues.apache.org/jira/browse/ATLAS-1877 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt > > UI should check Process entity in all parent superType, right know its > checking for only 1 level > Step to reproduce : > # Run quickstart > # Create entity of type Process and while creating process select time_dim > (Table entity) as a input and output. > # Now got to sales_fact_monthly_mv entity and you will see new output (Please > find attached screenshot ) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1877) UI: In Lineage for Process entity process icon is not showing.
[ https://issues.apache.org/jira/browse/ATLAS-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1877: --- Description: UI should check Process entity in all parent superType, right know its checking for only 1 level Step to reproduce : # Run quickstart # Create entity of type Process and while creating process select time_dim (Table entity) as a input and output. # Now got to time_dim entity and you will see new output (Please find attached screenshot ) was:UI should check Process entity in all parent superType, right know its checking for only 1 level > UI: In Lineage for Process entity process icon is not showing. > -- > > Key: ATLAS-1877 > URL: https://issues.apache.org/jira/browse/ATLAS-1877 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt > > UI should check Process entity in all parent superType, right know its > checking for only 1 level > Step to reproduce : > # Run quickstart > # Create entity of type Process and while creating process select time_dim > (Table entity) as a input and output. > # Now got to time_dim entity and you will see new output (Please find > attached screenshot ) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (ATLAS-1781) Atlas UI cannot show lineage pic when inputs and outputs of lineage are the same entity
[
https://issues.apache.org/jira/browse/ATLAS-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050434#comment-16050434
]
Keval Bhatt edited comment on ATLAS-1781 at 6/15/17 12:57 PM:
--
[~xiaqinglin] for Icon issue I created another jira ATLAS-1877
was (Author: kevalbhatt18):
[~xiaqinglin] For Icon issue I created another jira ATLAS-1877
> Atlas UI cannot show lineage pic when inputs and outputs of lineage are the
> same entity
> ---
>
> Key: ATLAS-1781
> URL: https://issues.apache.org/jira/browse/ATLAS-1781
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: trunk, 0.7-incubating, 0.8-incubating, 0.7.1-incubating,
> 0.9-incubating
>Reporter: qinglin,xia
>Assignee: Xinzhi,Luo
> Labels: atlas
> Fix For: 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1781.patch,
> 0001-fix-not-working-with-more-than-2-nodes-with-ATLAS-17.patch,
> after_test-wrong_op.png, browser_error.png, expected.png, fixed.png, Linage
> fix not working with more than 2 nodes with ATLAS-1781.png,
> Lineage_Create_Successfully_when_inputs_outputs_different.png,
> Lineage_keep_loading.png, Process_Type_Not_Blue.png,
> Starting_point_is_Impact_than_icon_colour_is_wrong(KEVAL_2_review).jpg
>
>
> I was working with the lineage for hbase, when I added a column family in a
> hbase table, I want to create a lineage for the table to show there is a
> change within the table schema, yet when I create a process using the atlas
> api, I found that the process entity is successfully created, but the lineage
> is not shown on the atlas web page.
> Steps to Reproduce this issue is:
> 1. build up an entity extends the DataSet Type
> 2. build up a lineage Process
> 3. set the process input and output to the same entity
> The code is like:
> Referenceable table1 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, input_table_name);
> Referenceable table2 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, output_table_name);
> HBaseProcess process = new HBaseProcess("process");
> process.setInput(table1.getId());
> process.setoutput(table2.getId());
> here I set the input_table_name and output_table_name the same string name,
> when I set them different values, the lineage pic can be shown for table1 and
> table2 successfully
> Screenshots are:
> 1) The lineage pic keep loading on the atlas UI
> 2) The error log reported by the browser console
> 3) The lineage pic showed successfully when set the inputs and outputs of the
> lineage to different entities.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-1781) Atlas UI cannot show lineage pic when inputs and outputs of lineage are the same entity
[
https://issues.apache.org/jira/browse/ATLAS-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050434#comment-16050434
]
Keval Bhatt commented on ATLAS-1781:
[~xiaqinglin] For Icon issue I created another jira ATLAS-1877
> Atlas UI cannot show lineage pic when inputs and outputs of lineage are the
> same entity
> ---
>
> Key: ATLAS-1781
> URL: https://issues.apache.org/jira/browse/ATLAS-1781
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: trunk, 0.7-incubating, 0.8-incubating, 0.7.1-incubating,
> 0.9-incubating
>Reporter: qinglin,xia
>Assignee: Xinzhi,Luo
> Labels: atlas
> Fix For: 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1781.patch,
> 0001-fix-not-working-with-more-than-2-nodes-with-ATLAS-17.patch,
> after_test-wrong_op.png, browser_error.png, expected.png, fixed.png, Linage
> fix not working with more than 2 nodes with ATLAS-1781.png,
> Lineage_Create_Successfully_when_inputs_outputs_different.png,
> Lineage_keep_loading.png, Process_Type_Not_Blue.png,
> Starting_point_is_Impact_than_icon_colour_is_wrong(KEVAL_2_review).jpg
>
>
> I was working with the lineage for hbase, when I added a column family in a
> hbase table, I want to create a lineage for the table to show there is a
> change within the table schema, yet when I create a process using the atlas
> api, I found that the process entity is successfully created, but the lineage
> is not shown on the atlas web page.
> Steps to Reproduce this issue is:
> 1. build up an entity extends the DataSet Type
> 2. build up a lineage Process
> 3. set the process input and output to the same entity
> The code is like:
> Referenceable table1 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, input_table_name);
> Referenceable table2 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, output_table_name);
> HBaseProcess process = new HBaseProcess("process");
> process.setInput(table1.getId());
> process.setoutput(table2.getId());
> here I set the input_table_name and output_table_name the same string name,
> when I set them different values, the lineage pic can be shown for table1 and
> table2 successfully
> Screenshots are:
> 1) The lineage pic keep loading on the atlas UI
> 2) The error log reported by the browser console
> 3) The lineage pic showed successfully when set the inputs and outputs of the
> lineage to different entities.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (ATLAS-1877) UI: In Lineage for Process entity process icon is not showing.
Keval Bhatt created ATLAS-1877: -- Summary: UI: In Lineage for Process entity process icon is not showing. Key: ATLAS-1877 URL: https://issues.apache.org/jira/browse/ATLAS-1877 Project: Atlas Issue Type: Bug Reporter: Keval Bhatt Assignee: Keval Bhatt UI should check Process entity in all parent superType, right know its checking for only 1 level -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1781) Atlas UI cannot show lineage pic when inputs and outputs of lineage are the same entity
[
https://issues.apache.org/jira/browse/ATLAS-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050343#comment-16050343
]
Keval Bhatt commented on ATLAS-1781:
[~xiaqinglin] Will create another bug if icon is not correct for process entity
on master.
[~Xinzhi,Luo] as part of this bug can you please fix arrow color , other
lineage items works fine.
> Atlas UI cannot show lineage pic when inputs and outputs of lineage are the
> same entity
> ---
>
> Key: ATLAS-1781
> URL: https://issues.apache.org/jira/browse/ATLAS-1781
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: trunk, 0.7-incubating, 0.8-incubating, 0.7.1-incubating,
> 0.9-incubating
>Reporter: qinglin,xia
>Assignee: Xinzhi,Luo
> Labels: atlas
> Fix For: 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1781.patch,
> 0001-fix-not-working-with-more-than-2-nodes-with-ATLAS-17.patch,
> after_test-wrong_op.png, browser_error.png, expected.png, fixed.png, Linage
> fix not working with more than 2 nodes with ATLAS-1781.png,
> Lineage_Create_Successfully_when_inputs_outputs_different.png,
> Lineage_keep_loading.png, Process_Type_Not_Blue.png,
> Starting_point_is_Impact_than_icon_colour_is_wrong(KEVAL_2_review).jpg
>
>
> I was working with the lineage for hbase, when I added a column family in a
> hbase table, I want to create a lineage for the table to show there is a
> change within the table schema, yet when I create a process using the atlas
> api, I found that the process entity is successfully created, but the lineage
> is not shown on the atlas web page.
> Steps to Reproduce this issue is:
> 1. build up an entity extends the DataSet Type
> 2. build up a lineage Process
> 3. set the process input and output to the same entity
> The code is like:
> Referenceable table1 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, input_table_name);
> Referenceable table2 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, output_table_name);
> HBaseProcess process = new HBaseProcess("process");
> process.setInput(table1.getId());
> process.setoutput(table2.getId());
> here I set the input_table_name and output_table_name the same string name,
> when I set them different values, the lineage pic can be shown for table1 and
> table2 successfully
> Screenshots are:
> 1) The lineage pic keep loading on the atlas UI
> 2) The error log reported by the browser console
> 3) The lineage pic showed successfully when set the inputs and outputs of the
> lineage to different entities.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-1781) Atlas UI cannot show lineage pic when inputs and outputs of lineage are the same entity
[
https://issues.apache.org/jira/browse/ATLAS-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049023#comment-16049023
]
Keval Bhatt commented on ATLAS-1781:
[~Xinzhi,Luo] I tested your updated patch
(*0001-fix-not-working-with-more-than-2-nodes-with-ATLAS-17.patch*) and I found
few issues regarding Icon and arrow color.
Step to reproduce :
# Run quickstart
# Create entity of type *Process* and while creating process select *time_dim*
(Table entity) as a input and output.
# Now got to time_dim entity and you will see new output (Please find attached
screenshot
Starting_point_is_Impact_than_icon_colour_is_wrong(KEVAL_2_review).jpg )
Expected.
# Icon of *test_process* should be process icon (i.e blue color with gear icon
in it).
# Arrow from *test_process* should be orange.
> Atlas UI cannot show lineage pic when inputs and outputs of lineage are the
> same entity
> ---
>
> Key: ATLAS-1781
> URL: https://issues.apache.org/jira/browse/ATLAS-1781
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: trunk, 0.7-incubating, 0.8-incubating, 0.7.1-incubating,
> 0.9-incubating
>Reporter: qinglin,xia
>Assignee: Xinzhi,Luo
> Labels: atlas
> Fix For: 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1781.patch,
> 0001-fix-not-working-with-more-than-2-nodes-with-ATLAS-17.patch,
> after_test-wrong_op.png, browser_error.png, expected.png, fixed.png, Linage
> fix not working with more than 2 nodes with ATLAS-1781.png,
> Lineage_Create_Successfully_when_inputs_outputs_different.png,
> Lineage_keep_loading.png,
> Starting_point_is_Impact_than_icon_colour_is_wrong(KEVAL_2_review).jpg
>
>
> I was working with the lineage for hbase, when I added a column family in a
> hbase table, I want to create a lineage for the table to show there is a
> change within the table schema, yet when I create a process using the atlas
> api, I found that the process entity is successfully created, but the lineage
> is not shown on the atlas web page.
> Steps to Reproduce this issue is:
> 1. build up an entity extends the DataSet Type
> 2. build up a lineage Process
> 3. set the process input and output to the same entity
> The code is like:
> Referenceable table1 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, input_table_name);
> Referenceable table2 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, output_table_name);
> HBaseProcess process = new HBaseProcess("process");
> process.setInput(table1.getId());
> process.setoutput(table2.getId());
> here I set the input_table_name and output_table_name the same string name,
> when I set them different values, the lineage pic can be shown for table1 and
> table2 successfully
> Screenshots are:
> 1) The lineage pic keep loading on the atlas UI
> 2) The error log reported by the browser console
> 3) The lineage pic showed successfully when set the inputs and outputs of the
> lineage to different entities.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ATLAS-1781) Atlas UI cannot show lineage pic when inputs and outputs of lineage are the same entity
[
https://issues.apache.org/jira/browse/ATLAS-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-1781:
---
Attachment:
Starting_point_is_Impact_than_icon_colour_is_wrong(KEVAL_2_review).jpg
> Atlas UI cannot show lineage pic when inputs and outputs of lineage are the
> same entity
> ---
>
> Key: ATLAS-1781
> URL: https://issues.apache.org/jira/browse/ATLAS-1781
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: trunk, 0.7-incubating, 0.8-incubating, 0.7.1-incubating,
> 0.9-incubating
>Reporter: qinglin,xia
>Assignee: Xinzhi,Luo
> Labels: atlas
> Fix For: 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1781.patch,
> 0001-fix-not-working-with-more-than-2-nodes-with-ATLAS-17.patch,
> after_test-wrong_op.png, browser_error.png, expected.png, fixed.png, Linage
> fix not working with more than 2 nodes with ATLAS-1781.png,
> Lineage_Create_Successfully_when_inputs_outputs_different.png,
> Lineage_keep_loading.png,
> Starting_point_is_Impact_than_icon_colour_is_wrong(KEVAL_2_review).jpg
>
>
> I was working with the lineage for hbase, when I added a column family in a
> hbase table, I want to create a lineage for the table to show there is a
> change within the table schema, yet when I create a process using the atlas
> api, I found that the process entity is successfully created, but the lineage
> is not shown on the atlas web page.
> Steps to Reproduce this issue is:
> 1. build up an entity extends the DataSet Type
> 2. build up a lineage Process
> 3. set the process input and output to the same entity
> The code is like:
> Referenceable table1 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, input_table_name);
> Referenceable table2 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, output_table_name);
> HBaseProcess process = new HBaseProcess("process");
> process.setInput(table1.getId());
> process.setoutput(table2.getId());
> here I set the input_table_name and output_table_name the same string name,
> when I set them different values, the lineage pic can be shown for table1 and
> table2 successfully
> Screenshots are:
> 1) The lineage pic keep loading on the atlas UI
> 2) The error log reported by the browser console
> 3) The lineage pic showed successfully when set the inputs and outputs of the
> lineage to different entities.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-1781) Atlas UI cannot show lineage pic when inputs and outputs of lineage are the same entity
[
https://issues.apache.org/jira/browse/ATLAS-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047711#comment-16047711
]
Keval Bhatt commented on ATLAS-1781:
[~Xinzhi,Luo] I am busy with other tasks on priority , will surely review it in
couple of days.
> Atlas UI cannot show lineage pic when inputs and outputs of lineage are the
> same entity
> ---
>
> Key: ATLAS-1781
> URL: https://issues.apache.org/jira/browse/ATLAS-1781
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: trunk, 0.7-incubating, 0.8-incubating, 0.7.1-incubating,
> 0.9-incubating
>Reporter: qinglin,xia
>Assignee: Xinzhi,Luo
> Labels: atlas
> Fix For: 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1781.patch,
> 0001-fix-not-working-with-more-than-2-nodes-with-ATLAS-17.patch,
> after_test-wrong_op.png, browser_error.png, expected.png, fixed.png, Linage
> fix not working with more than 2 nodes with ATLAS-1781.png,
> Lineage_Create_Successfully_when_inputs_outputs_different.png,
> Lineage_keep_loading.png
>
>
> I was working with the lineage for hbase, when I added a column family in a
> hbase table, I want to create a lineage for the table to show there is a
> change within the table schema, yet when I create a process using the atlas
> api, I found that the process entity is successfully created, but the lineage
> is not shown on the atlas web page.
> Steps to Reproduce this issue is:
> 1. build up an entity extends the DataSet Type
> 2. build up a lineage Process
> 3. set the process input and output to the same entity
> The code is like:
> Referenceable table1 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, input_table_name);
> Referenceable table2 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, output_table_name);
> HBaseProcess process = new HBaseProcess("process");
> process.setInput(table1.getId());
> process.setoutput(table2.getId());
> here I set the input_table_name and output_table_name the same string name,
> when I set them different values, the lineage pic can be shown for table1 and
> table2 successfully
> Screenshots are:
> 1) The lineage pic keep loading on the atlas UI
> 2) The error log reported by the browser console
> 3) The lineage pic showed successfully when set the inputs and outputs of the
> lineage to different entities.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ATLAS-1781) Atlas UI cannot show lineage pic when inputs and outputs of lineage are the same entity
[
https://issues.apache.org/jira/browse/ATLAS-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038809#comment-16038809
]
Keval Bhatt commented on ATLAS-1781:
[~Xinzhi,Luo] Please don't mark jira status as resolved until its committed to
master.
> Atlas UI cannot show lineage pic when inputs and outputs of lineage are the
> same entity
> ---
>
> Key: ATLAS-1781
> URL: https://issues.apache.org/jira/browse/ATLAS-1781
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: trunk, 0.7-incubating, 0.8-incubating, 0.7.1-incubating,
> 0.9-incubating
>Reporter: qinglin,xia
>Assignee: Xinzhi,Luo
> Labels: atlas
> Fix For: 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1781.patch,
> 0001-fix-not-working-with-more-than-2-nodes-with-ATLAS-17.patch,
> after_test-wrong_op.png, browser_error.png, expected.png, fixed.png, Linage
> fix not working with more than 2 nodes with ATLAS-1781.png,
> Lineage_Create_Successfully_when_inputs_outputs_different.png,
> Lineage_keep_loading.png
>
>
> I was working with the lineage for hbase, when I added a column family in a
> hbase table, I want to create a lineage for the table to show there is a
> change within the table schema, yet when I create a process using the atlas
> api, I found that the process entity is successfully created, but the lineage
> is not shown on the atlas web page.
> Steps to Reproduce this issue is:
> 1. build up an entity extends the DataSet Type
> 2. build up a lineage Process
> 3. set the process input and output to the same entity
> The code is like:
> Referenceable table1 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, input_table_name);
> Referenceable table2 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, output_table_name);
> HBaseProcess process = new HBaseProcess("process");
> process.setInput(table1.getId());
> process.setoutput(table2.getId());
> here I set the input_table_name and output_table_name the same string name,
> when I set them different values, the lineage pic can be shown for table1 and
> table2 successfully
> Screenshots are:
> 1) The lineage pic keep loading on the atlas UI
> 2) The error log reported by the browser console
> 3) The lineage pic showed successfully when set the inputs and outputs of the
> lineage to different entities.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Reopened] (ATLAS-1826) UI Create Entity : Type doesn't list the inverseRef constrained attribute options when name length is less than 3.
[ https://issues.apache.org/jira/browse/ATLAS-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reopened ATLAS-1826: @qinglin,xia Please don't mark jira status as resolved until its committed to master. > UI Create Entity : Type doesn't list the inverseRef constrained attribute > options when name length is less than 3. > -- > > Key: ATLAS-1826 > URL: https://issues.apache.org/jira/browse/ATLAS-1826 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: qinglin,xia > Fix For: 0.9-incubating > > Attachments: 0001-fix-ATLAS-1826.patch, fix-ATLAS-1826.png > > > 1. Created a hbase_table h1. > 2. Tried to create a hbase_column_family with hbase table as h1. Since "h1" > has only 2 characters , the drop down didn't display "h1" but displayed > "Please enter 1 or more characters". > 3. When hbase_table name length is more than 2 , the drop down lists the name. > Same happens when adding hbase_column_family with name "hf" to hbase_column. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (ATLAS-1826) UI Create Entity : Type doesn't list the inverseRef constrained attribute options when name length is less than 3.
[ https://issues.apache.org/jira/browse/ATLAS-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038801#comment-16038801 ] Keval Bhatt edited comment on ATLAS-1826 at 6/6/17 12:42 PM: - [~xiaqinglin] Please don't mark jira status as resolved until its committed to master. was (Author: kevalbhatt18): @qinglin,xia Please don't mark jira status as resolved until its committed to master. > UI Create Entity : Type doesn't list the inverseRef constrained attribute > options when name length is less than 3. > -- > > Key: ATLAS-1826 > URL: https://issues.apache.org/jira/browse/ATLAS-1826 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: qinglin,xia > Fix For: 0.9-incubating > > Attachments: 0001-fix-ATLAS-1826.patch, fix-ATLAS-1826.png > > > 1. Created a hbase_table h1. > 2. Tried to create a hbase_column_family with hbase table as h1. Since "h1" > has only 2 characters , the drop down didn't display "h1" but displayed > "Please enter 1 or more characters". > 3. When hbase_table name length is more than 2 , the drop down lists the name. > Same happens when adding hbase_column_family with name "hf" to hbase_column. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1781) Atlas UI cannot show lineage pic when inputs and outputs of lineage are the same entity
[
https://issues.apache.org/jira/browse/ATLAS-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-1781:
---
Attachment: expected.png
after_test-wrong_op.png
> Atlas UI cannot show lineage pic when inputs and outputs of lineage are the
> same entity
> ---
>
> Key: ATLAS-1781
> URL: https://issues.apache.org/jira/browse/ATLAS-1781
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: trunk, 0.7-incubating, 0.8-incubating, 0.7.1-incubating,
> 0.9-incubating
>Reporter: qinglin,xia
>Assignee: Xinzhi,Luo
> Fix For: 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1781.patch, after_test-wrong_op.png,
> browser_error.png, expected.png, fixed.png,
> Lineage_Create_Successfully_when_inputs_outputs_different.png,
> Lineage_keep_loading.png
>
>
> I was working with the lineage for hbase, when I added a column family in a
> hbase table, I want to create a lineage for the table to show there is a
> change within the table schema, yet when I create a process using the atlas
> api, I found that the process entity is successfully created, but the lineage
> is not shown on the atlas web page.
> Steps to Reproduce this issue is:
> 1. build up an entity extends the DataSet Type
> 2. build up a lineage Process
> 3. set the process input and output to the same entity
> The code is like:
> Referenceable table1 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, input_table_name);
> Referenceable table2 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, output_table_name);
> HBaseProcess process = new HBaseProcess("process");
> process.setInput(table1.getId());
> process.setoutput(table2.getId());
> here I set the input_table_name and output_table_name the same string name,
> when I set them different values, the lineage pic can be shown for table1 and
> table2 successfully
> Screenshots are:
> 1) The lineage pic keep loading on the atlas UI
> 2) The error log reported by the browser console
> 3) The lineage pic showed successfully when set the inputs and outputs of the
> lineage to different entities.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Reopened] (ATLAS-1781) Atlas UI cannot show lineage pic when inputs and outputs of lineage are the same entity
[
https://issues.apache.org/jira/browse/ATLAS-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt reopened ATLAS-1781:
[~Xinzhi,Luo] I tested your patch it works good for 2 nodes. if we have more
then 2 nodes it want render correctly. (i.e arrow color are not in correct
order)
To reproduce.
* Run quick start.
* Search for "Table".
* Then go to "sales_fact" entity and check for Lineage.
Please find attached screenshot.
* wrong o/p -> after_test-wrong_op.png
* expected - > expected.png
> Atlas UI cannot show lineage pic when inputs and outputs of lineage are the
> same entity
> ---
>
> Key: ATLAS-1781
> URL: https://issues.apache.org/jira/browse/ATLAS-1781
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: trunk, 0.7-incubating, 0.8-incubating, 0.7.1-incubating,
> 0.9-incubating
>Reporter: qinglin,xia
>Assignee: Xinzhi,Luo
> Fix For: 0.9-incubating
>
> Attachments: 0001-fix-ATLAS-1781.patch, browser_error.png, fixed.png,
> Lineage_Create_Successfully_when_inputs_outputs_different.png,
> Lineage_keep_loading.png
>
>
> I was working with the lineage for hbase, when I added a column family in a
> hbase table, I want to create a lineage for the table to show there is a
> change within the table schema, yet when I create a process using the atlas
> api, I found that the process entity is successfully created, but the lineage
> is not shown on the atlas web page.
> Steps to Reproduce this issue is:
> 1. build up an entity extends the DataSet Type
> 2. build up a lineage Process
> 3. set the process input and output to the same entity
> The code is like:
> Referenceable table1 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, input_table_name);
> Referenceable table2 =
> atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME,
> AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, output_table_name);
> HBaseProcess process = new HBaseProcess("process");
> process.setInput(table1.getId());
> process.setoutput(table2.getId());
> here I set the input_table_name and output_table_name the same string name,
> when I set them different values, the lineage pic can be shown for table1 and
> table2 successfully
> Screenshots are:
> 1) The lineage pic keep loading on the atlas UI
> 2) The error log reported by the browser console
> 3) The lineage pic showed successfully when set the inputs and outputs of the
> lineage to different entities.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (ATLAS-1811) UI : Audit Events are not shown in sorted order based on time sometimes.
[ https://issues.apache.org/jira/browse/ATLAS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-1811: -- Assignee: Kalyani Kashikar > UI : Audit Events are not shown in sorted order based on time sometimes. > > > Key: ATLAS-1811 > URL: https://issues.apache.org/jira/browse/ATLAS-1811 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: trunk, 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Kalyani Kashikar > Attachments: AuditDetailsUnordered.png > > > Created an entity and made did many tag association , dis-association and tag > update to that entity. All audit details are captured but not displayed in > sorted order based on timestamp value present in audit response. A few > entries are missing order. > Attached the screenshot . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1816) UI,excludeDeletedEntities : Next button in Basic query result view is not working if result query has DELETED entities
[ https://issues.apache.org/jira/browse/ATLAS-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1816: --- Attachment: ATLAS-1816.patch > UI,excludeDeletedEntities : Next button in Basic query result view is not > working if result query has DELETED entities > -- > > Key: ATLAS-1816 > URL: https://issues.apache.org/jira/browse/ATLAS-1816 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-1816.patch > > > 1. Created 50 tables > 2. Deleted 5 tables which are shown in the first page of the basic query > search. > 3. Fired a basic query : type name = hive_table > 4. Page showed only 20 results. Because there were only 20 results , Next > button used to navigate to next page was disabled. > 5. Checked the "Include historical entities" check box. 25 results displayed > but still Next button was disabled. > 6. Hence even if one DELETED entity is returned in the basic query , > navigation to next table becomes impossible. > If all returned entities in the limit 25 are ACTIVE , Next button is enabled. > For example out of 150 entities , 5 entities are DELETED . Those DELETED > entities are found in 2nd page. Hence Navigation from 1st page to 2nd page is > possible . From there on , even though "Include Historical entities" is > checked and 25 results are returned for the page , next button is disabled. > [ATLAS-1815|https://issues.apache.org/jira/browse/ATLAS-1815] is one of the > reasons for this bug. > Advanced(DSL) query result window is not suffering from this issue probably > because excludeDeletedEntities parameter is not honored. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1816) UI,excludeDeletedEntities : Next button in Basic query result view is not working if result query has DELETED entities
[ https://issues.apache.org/jira/browse/ATLAS-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1816: --- Attachment: (was: ATLAS-1812.1.patch) > UI,excludeDeletedEntities : Next button in Basic query result view is not > working if result query has DELETED entities > -- > > Key: ATLAS-1816 > URL: https://issues.apache.org/jira/browse/ATLAS-1816 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt > > 1. Created 50 tables > 2. Deleted 5 tables which are shown in the first page of the basic query > search. > 3. Fired a basic query : type name = hive_table > 4. Page showed only 20 results. Because there were only 20 results , Next > button used to navigate to next page was disabled. > 5. Checked the "Include historical entities" check box. 25 results displayed > but still Next button was disabled. > 6. Hence even if one DELETED entity is returned in the basic query , > navigation to next table becomes impossible. > If all returned entities in the limit 25 are ACTIVE , Next button is enabled. > For example out of 150 entities , 5 entities are DELETED . Those DELETED > entities are found in 2nd page. Hence Navigation from 1st page to 2nd page is > possible . From there on , even though "Include Historical entities" is > checked and 25 results are returned for the page , next button is disabled. > [ATLAS-1815|https://issues.apache.org/jira/browse/ATLAS-1815] is one of the > reasons for this bug. > Advanced(DSL) query result window is not suffering from this issue probably > because excludeDeletedEntities parameter is not honored. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1816) UI,excludeDeletedEntities : Next button in Basic query result view is not working if result query has DELETED entities
[ https://issues.apache.org/jira/browse/ATLAS-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1816: --- Attachment: ATLAS-1812.1.patch > UI,excludeDeletedEntities : Next button in Basic query result view is not > working if result query has DELETED entities > -- > > Key: ATLAS-1816 > URL: https://issues.apache.org/jira/browse/ATLAS-1816 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt > > 1. Created 50 tables > 2. Deleted 5 tables which are shown in the first page of the basic query > search. > 3. Fired a basic query : type name = hive_table > 4. Page showed only 20 results. Because there were only 20 results , Next > button used to navigate to next page was disabled. > 5. Checked the "Include historical entities" check box. 25 results displayed > but still Next button was disabled. > 6. Hence even if one DELETED entity is returned in the basic query , > navigation to next table becomes impossible. > If all returned entities in the limit 25 are ACTIVE , Next button is enabled. > For example out of 150 entities , 5 entities are DELETED . Those DELETED > entities are found in 2nd page. Hence Navigation from 1st page to 2nd page is > possible . From there on , even though "Include Historical entities" is > checked and 25 results are returned for the page , next button is disabled. > [ATLAS-1815|https://issues.apache.org/jira/browse/ATLAS-1815] is one of the > reasons for this bug. > Advanced(DSL) query result window is not suffering from this issue probably > because excludeDeletedEntities parameter is not honored. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1816) UI,excludeDeletedEntities : Next button in Basic query result view is not working if result query has DELETED entities
[ https://issues.apache.org/jira/browse/ATLAS-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1816: --- Attachment: (was: ATLAS-1816.patch) > UI,excludeDeletedEntities : Next button in Basic query result view is not > working if result query has DELETED entities > -- > > Key: ATLAS-1816 > URL: https://issues.apache.org/jira/browse/ATLAS-1816 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt > > 1. Created 50 tables > 2. Deleted 5 tables which are shown in the first page of the basic query > search. > 3. Fired a basic query : type name = hive_table > 4. Page showed only 20 results. Because there were only 20 results , Next > button used to navigate to next page was disabled. > 5. Checked the "Include historical entities" check box. 25 results displayed > but still Next button was disabled. > 6. Hence even if one DELETED entity is returned in the basic query , > navigation to next table becomes impossible. > If all returned entities in the limit 25 are ACTIVE , Next button is enabled. > For example out of 150 entities , 5 entities are DELETED . Those DELETED > entities are found in 2nd page. Hence Navigation from 1st page to 2nd page is > possible . From there on , even though "Include Historical entities" is > checked and 25 results are returned for the page , next button is disabled. > [ATLAS-1815|https://issues.apache.org/jira/browse/ATLAS-1815] is one of the > reasons for this bug. > Advanced(DSL) query result window is not suffering from this issue probably > because excludeDeletedEntities parameter is not honored. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1816) UI,excludeDeletedEntities : Next button in Basic query result view is not working if result query has DELETED entities
[ https://issues.apache.org/jira/browse/ATLAS-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-1816: -- Assignee: Keval Bhatt > UI,excludeDeletedEntities : Next button in Basic query result view is not > working if result query has DELETED entities > -- > > Key: ATLAS-1816 > URL: https://issues.apache.org/jira/browse/ATLAS-1816 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt > Attachments: ATLAS-1816.patch > > > 1. Created 50 tables > 2. Deleted 5 tables which are shown in the first page of the basic query > search. > 3. Fired a basic query : type name = hive_table > 4. Page showed only 20 results. Because there were only 20 results , Next > button used to navigate to next page was disabled. > 5. Checked the "Include historical entities" check box. 25 results displayed > but still Next button was disabled. > 6. Hence even if one DELETED entity is returned in the basic query , > navigation to next table becomes impossible. > If all returned entities in the limit 25 are ACTIVE , Next button is enabled. > For example out of 150 entities , 5 entities are DELETED . Those DELETED > entities are found in 2nd page. Hence Navigation from 1st page to 2nd page is > possible . From there on , even though "Include Historical entities" is > checked and 25 results are returned for the page , next button is disabled. > [ATLAS-1815|https://issues.apache.org/jira/browse/ATLAS-1815] is one of the > reasons for this bug. > Advanced(DSL) query result window is not suffering from this issue probably > because excludeDeletedEntities parameter is not honored. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1820) User Is not able to create tag using enum type
Keval Bhatt created ATLAS-1820: -- Summary: User Is not able to create tag using enum type Key: ATLAS-1820 URL: https://issues.apache.org/jira/browse/ATLAS-1820 Project: Atlas Issue Type: Bug Affects Versions: 0.9-incubating Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 0.8-incubating, 0.9-incubating -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1812) On browser refresh if, tag is doesn't exist, then URL should update with the first tag.
[ https://issues.apache.org/jira/browse/ATLAS-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1812: --- Attachment: ATLAS-1812.1.patch > On browser refresh if, tag is doesn't exist, then URL should update with the > first tag. > --- > > Key: ATLAS-1812 > URL: https://issues.apache.org/jira/browse/ATLAS-1812 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1812.1.patch, ATLAS-1812.patch > > > - While clicking on refresh button of tag tab if tag which is deleted from > other sessions and it is active from UI side, then the browser URL should > update with the first tag if available. > - Above scenario should be happened for browser refresh, as well. > - If user type in tag-name into URL which does not exist in tag list, then > the browser URL should update with the first tag if available. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1816) UI,excludeDeletedEntities : Next button in Basic query result view is not working if result query has DELETED entities
[ https://issues.apache.org/jira/browse/ATLAS-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1816: --- Attachment: ATLAS-1816.patch > UI,excludeDeletedEntities : Next button in Basic query result view is not > working if result query has DELETED entities > -- > > Key: ATLAS-1816 > URL: https://issues.apache.org/jira/browse/ATLAS-1816 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath > Attachments: ATLAS-1816.patch > > > 1. Created 50 tables > 2. Deleted 5 tables which are shown in the first page of the basic query > search. > 3. Fired a basic query : type name = hive_table > 4. Page showed only 20 results. Because there were only 20 results , Next > button used to navigate to next page was disabled. > 5. Checked the "Include historical entities" check box. 25 results displayed > but still Next button was disabled. > 6. Hence even if one DELETED entity is returned in the basic query , > navigation to next table becomes impossible. > If all returned entities in the limit 25 are ACTIVE , Next button is enabled. > For example out of 150 entities , 5 entities are DELETED . Those DELETED > entities are found in 2nd page. Hence Navigation from 1st page to 2nd page is > possible . From there on , even though "Include Historical entities" is > checked and 25 results are returned for the page , next button is disabled. > [ATLAS-1815|https://issues.apache.org/jira/browse/ATLAS-1815] is one of the > reasons for this bug. > Advanced(DSL) query result window is not suffering from this issue probably > because excludeDeletedEntities parameter is not honored. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1808) UI : All selected entities are assigned to tag when Assign Tag corresponding to 1 entity is clicked.
[ https://issues.apache.org/jira/browse/ATLAS-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-1808: -- Assignee: Keval Bhatt > UI : All selected entities are assigned to tag when Assign Tag corresponding > to 1 entity is clicked. > > > Key: ATLAS-1808 > URL: https://issues.apache.org/jira/browse/ATLAS-1808 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating, 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt > Attachments: ATLAS-1808.patch > > > Steps: > 1. Searched for type hive_table which listed 10 results. > 2. Selected all the entities (using check box). > 3. Clicked on Assign tag button corresponding to the first result ex : table1 > ( "+" sign button with class a.InputTagAdd.assignTag) > 4. Selected the tag to be assigned ex:tag1 > 5. Expected tag1 would be assigned to only table1 though all the entities are > selected. But all the entities are assigned to tag1. > Note : Didn't click on Button with text " + Assign Tag" (class : > a.inputAssignTag.multiSelectTag.assignTag.btnAssign) after selecting multiple > entities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1812) On browser refresh if, tag is doesn't exist, then URL should update with the first tag.
[ https://issues.apache.org/jira/browse/ATLAS-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1812: --- Attachment: ATLAS-1812.patch > On browser refresh if, tag is doesn't exist, then URL should update with the > first tag. > --- > > Key: ATLAS-1812 > URL: https://issues.apache.org/jira/browse/ATLAS-1812 > Project: Atlas > Issue Type: Bug >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1812.patch > > > - While clicking on refresh button of tag tab if tag which is deleted from > other sessions and it is active from UI side, then the browser URL should > update with the first tag if available. > - Above scenario should be happened for browser refresh, as well. > - If user type in tag-name into URL which does not exist in tag list, then > the browser URL should update with the first tag if available. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1812) On browser refresh if, tag is doesn't exist, then URL should update with the first tag.
Keval Bhatt created ATLAS-1812: -- Summary: On browser refresh if, tag is doesn't exist, then URL should update with the first tag. Key: ATLAS-1812 URL: https://issues.apache.org/jira/browse/ATLAS-1812 Project: Atlas Issue Type: Bug Reporter: Keval Bhatt Assignee: Keval Bhatt - While clicking on refresh button of tag tab if tag which is deleted from other sessions and it is active from UI side, then the browser URL should update with the first tag if available. - Above scenario should be happened for browser refresh, as well. - If user type in tag-name into URL which does not exist in tag list, then the browser URL should update with the first tag if available. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1756) Allow user to edit associated Tag (classification)
[ https://issues.apache.org/jira/browse/ATLAS-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1756: --- Attachment: ATLAS-1756.1.patch Rebased the patch with master. > Allow user to edit associated Tag (classification) > -- > > Key: ATLAS-1756 > URL: https://issues.apache.org/jira/browse/ATLAS-1756 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-1756.1.patch, ATLAS-1756.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1763) UI : Atlas lands in the page of Deleted tag (the only tag) on clicking TAGS tab
[ https://issues.apache.org/jira/browse/ATLAS-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004105#comment-16004105 ] Keval Bhatt commented on ATLAS-1763: [~madhan.neethiraj], [~ssainath] I have a solution for this issue will try with the same and if it works the will provide the patch. > UI : Atlas lands in the page of Deleted tag (the only tag) on clicking TAGS > tab > > > Key: ATLAS-1763 > URL: https://issues.apache.org/jira/browse/ATLAS-1763 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Trivial > > 1. Created tag tag1 > 2. Clicked on TAGS tab which landed in > http://localhost:21000/index.html#!/tag/tagAttribute/tag1 > 3. Deleted the tag through REST. > 4. Clicked on the TAGS tab. The TAGS tab listed tag1 . But on disabling cache > , tag1 is removed. > 5.But Atlas lands in > http://localhost:21000/index.html#!/tag/tagAttribute/tag1 which throws 404 > exception while clicking Tags tab . > On opening Atlas in another incognito window , this issue is not seen . Atlas > possibly caches tag1 which lands in /tag/tagAttribute/tag1 and causes issue. > When there are 1 or more ACTIVE tags , this issue is not seen as it lands in > /tag/tagAttribute/. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (ATLAS-1763) UI : Atlas lands in the page of Deleted tag (the only tag) on clicking TAGS tab
[ https://issues.apache.org/jira/browse/ATLAS-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004105#comment-16004105 ] Keval Bhatt edited comment on ATLAS-1763 at 5/10/17 5:36 AM: - [~madhan.neethiraj], [~ssainath] I have a solution for this issue will try with the same and if it works then will provide the patch. was (Author: kevalbhatt18): [~madhan.neethiraj], [~ssainath] I have a solution for this issue will try with the same and if it works the will provide the patch. > UI : Atlas lands in the page of Deleted tag (the only tag) on clicking TAGS > tab > > > Key: ATLAS-1763 > URL: https://issues.apache.org/jira/browse/ATLAS-1763 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Trivial > > 1. Created tag tag1 > 2. Clicked on TAGS tab which landed in > http://localhost:21000/index.html#!/tag/tagAttribute/tag1 > 3. Deleted the tag through REST. > 4. Clicked on the TAGS tab. The TAGS tab listed tag1 . But on disabling cache > , tag1 is removed. > 5.But Atlas lands in > http://localhost:21000/index.html#!/tag/tagAttribute/tag1 which throws 404 > exception while clicking Tags tab . > On opening Atlas in another incognito window , this issue is not seen . Atlas > possibly caches tag1 which lands in /tag/tagAttribute/tag1 and causes issue. > When there are 1 or more ACTIVE tags , this issue is not seen as it lands in > /tag/tagAttribute/. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1763) UI : Atlas lands in the page of Deleted tag (the only tag) on clicking TAGS tab
[ https://issues.apache.org/jira/browse/ATLAS-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15998052#comment-15998052 ] Keval Bhatt commented on ATLAS-1763: [~madhan.neethiraj] You mean to say application cache ? > UI : Atlas lands in the page of Deleted tag (the only tag) on clicking TAGS > tab > > > Key: ATLAS-1763 > URL: https://issues.apache.org/jira/browse/ATLAS-1763 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Trivial > > 1. Created tag tag1 > 2. Clicked on TAGS tab which landed in > http://localhost:21000/index.html#!/tag/tagAttribute/tag1 > 3. Deleted the tag through REST. > 4. Clicked on the TAGS tab. The TAGS tab listed tag1 . But on disabling cache > , tag1 is removed. > 5.But Atlas lands in > http://localhost:21000/index.html#!/tag/tagAttribute/tag1 which throws 404 > exception while clicking Tags tab . > On opening Atlas in another incognito window , this issue is not seen . Atlas > possibly caches tag1 which lands in /tag/tagAttribute/tag1 and causes issue. > When there are 1 or more ACTIVE tags , this issue is not seen as it lands in > /tag/tagAttribute/. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1707) Atlas WUI on continues loading behind FireWall
[ https://issues.apache.org/jira/browse/ATLAS-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15992683#comment-15992683 ] Keval Bhatt commented on ATLAS-1707: + 1 for the patch > Atlas WUI on continues loading behind FireWall > -- > > Key: ATLAS-1707 > URL: https://issues.apache.org/jira/browse/ATLAS-1707 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.7-incubating > Environment: Atlas: Version":"0.7.0.2.5.3 > JDK 1.8 > Linux >Reporter: Ernani Pereira de Mattos Junior >Assignee: Nixon Rodrigues > Labels: patch, test > Fix For: 0.9-incubating > > Attachments: ATLAS-1707.2.patch, ATLAS-1707.3.patch, > ATLAS-1707.patch, index.html, index.html.original > > > Atlas is behind a FW in which does return a response. We Identify index.html > was loading googleapis css does not have a timeout and proceed with the WUI; > ref:http://tinyurl.com/lan4by9 > By removing the bellow line from the html file, there were no problem. > href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,400italic,600,600italic,700,700italic; > rel="stylesheet" type="text/css"> > 1. Shouldn't be applications self-contain in case of such situation? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1750: --- Attachment: ATLAS-1750.2.patch > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.1.patch, ATLAS-1750.2.patch, > ATLAS-1750.patch, ATLAS-1750-without-attrName-queryParam.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1760) For rendering property tab use type definition of the entity
[ https://issues.apache.org/jira/browse/ATLAS-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1760: --- Attachment: ATLAS-1760.patch > For rendering property tab use type definition of the entity > > > Key: ATLAS-1760 > URL: https://issues.apache.org/jira/browse/ATLAS-1760 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.8-incubating, 0.9-incubating > > Attachments: ATLAS-1760.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1750: --- Attachment: ATLAS-1750-without-attrName-queryParam.patch > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.1.patch, ATLAS-1750.patch, > ATLAS-1750-without-attrName-queryParam.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1750: --- Attachment: (was: ATLAS-1750.1.patch) > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.1.patch, ATLAS-1750.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1750: --- Attachment: ATLAS-1750.1.patch > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.1.patch, ATLAS-1750.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1750: --- Attachment: (was: ATLAS-1750-without-attrName-queryParam.patch) > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.1.patch, ATLAS-1750.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1750: --- Attachment: ATLAS-1750-without-attrName-queryParam.patch > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.1.patch, ATLAS-1750.patch, > ATLAS-1750-without-attrName-queryParam.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1750: --- Attachment: (was: ATLAS-1750-without-attrName-queryParam.patch) > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.1.patch, ATLAS-1750.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1750: --- Attachment: (was: ATLAS-1750.1.patch) > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.1.patch, ATLAS-1750.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1750: --- Attachment: ATLAS-1750.1.patch > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.1.patch, ATLAS-1750.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1750: --- Attachment: ATLAS-1750-without-attrName-queryParam.patch > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.1.patch, ATLAS-1750.patch, > ATLAS-1750-without-attrName-queryParam.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1750: --- Attachment: (was: ATLAS-1750-without-attrName-queryParam.patch) > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.1.patch, ATLAS-1750.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1750: --- Attachment: ATLAS-1750.1.patch > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.1.patch, ATLAS-1750.patch, > ATLAS-1750-without-attrName-queryParam.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1760) For rendering property tab use type definition of the entity
Keval Bhatt created ATLAS-1760: -- Summary: For rendering property tab use type definition of the entity Key: ATLAS-1760 URL: https://issues.apache.org/jira/browse/ATLAS-1760 Project: Atlas Issue Type: Bug Affects Versions: 0.9-incubating Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 0.8-incubating, 0.9-incubating -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15988720#comment-15988720 ] Keval Bhatt commented on ATLAS-1750: [~sarath.ku...@gmail.com] , [~madhan.neethiraj] I have attached two patches i.e ATLAS-1750-without-attrName-queryParam.patch and ATLAS-1750.1.patch. ATLAS-1750.1.patch has queryParam *attrName* while ATLAS-1750-without-attrName-queryParam.patch don't have queryParam attrName > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.1.patch, ATLAS-1750.patch, > ATLAS-1750-without-attrName-queryParam.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1750: --- Attachment: ATLAS-1750-without-attrName-queryParam.patch > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.1.patch, ATLAS-1750.patch, > ATLAS-1750-without-attrName-queryParam.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1750: --- Attachment: ATLAS-1750.1.patch > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.1.patch, ATLAS-1750.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1750) Typeahead Search Implemented on create entity.
[
https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15988413#comment-15988413
]
Keval Bhatt commented on ATLAS-1750:
[~sarath.ku...@gmail.com] I found one issue in search attribute api i.e if I
search for *Column* entity it wont return data because Column entity don't have
qualifiedName and from UI side we send attrName = 'qualifiedName'.
{code}
http://localhost:21000/api/atlas/v2/search/attribute?attrName=qualifiedName=time_id=Column=10=0
{code}
So to fix this issue I tried with *attrName = 'name'* and it worked for Column
entity but there are few entity which don't have name property as well example
*StorageDesc* so for StorageDesc I need to pass attrName = 'id' and it worked
Let me know if this can be handled from server side or do you require
queryParam in API from UI.
@CC [~madhan.neethiraj]
> Typeahead Search Implemented on create entity.
> --
>
> Key: ATLAS-1750
> URL: https://issues.apache.org/jira/browse/ATLAS-1750
> Project: Atlas
> Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Attachments: ATLAS-1750.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1756) Allow user to edit associated Tag (classification)
[ https://issues.apache.org/jira/browse/ATLAS-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1756: --- Summary: Allow user to edit associated Tag (classification) (was: Allow user to edit associated Tag (classication)) > Allow user to edit associated Tag (classification) > -- > > Key: ATLAS-1756 > URL: https://issues.apache.org/jira/browse/ATLAS-1756 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.8-incubating, 0.9-incubating > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1756) Allow user to edit associated Tag (classication)
Keval Bhatt created ATLAS-1756: -- Summary: Allow user to edit associated Tag (classication) Key: ATLAS-1756 URL: https://issues.apache.org/jira/browse/ATLAS-1756 Project: Atlas Issue Type: Improvement Components: atlas-webui Affects Versions: 0.9-incubating Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 0.8-incubating, 0.9-incubating -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1750) Typeahead Search Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1750: --- Attachment: ATLAS-1750.patch > Typeahead Search Implemented on create entity. > -- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Attachments: ATLAS-1750.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1750) Typeahead Implemented on create entity.
[ https://issues.apache.org/jira/browse/ATLAS-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-1750: -- Assignee: Keval Bhatt > Typeahead Implemented on create entity. > --- > > Key: ATLAS-1750 > URL: https://issues.apache.org/jira/browse/ATLAS-1750 > Project: Atlas > Issue Type: Improvement >Reporter: Keval Bhatt >Assignee: Keval Bhatt > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1750) Typeahead Implemented on create entity.
Keval Bhatt created ATLAS-1750: -- Summary: Typeahead Implemented on create entity. Key: ATLAS-1750 URL: https://issues.apache.org/jira/browse/ATLAS-1750 Project: Atlas Issue Type: Improvement Reporter: Keval Bhatt -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (ATLAS-1433) Atlas allows creation of tag with attributes' name same as that of its parent tags.
[ https://issues.apache.org/jira/browse/ATLAS-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964398#comment-15964398 ] Keval Bhatt edited comment on ATLAS-1433 at 4/12/17 1:01 PM: - committed to master (http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/c9a91264) committed to 0.8-incubating (http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/f6d9698a) was (Author: kevalbhatt18): committed to master (http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/c9a91264) > Atlas allows creation of tag with attributes' name same as that of its parent > tags. > --- > > Key: ATLAS-1433 > URL: https://issues.apache.org/jira/browse/ATLAS-1433 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Sharmadha Sainath >Assignee: Kalyani Kashikar > Attachments: ATLAS-1433.1.patch, ATLAS-1433.patch > > > Created a tag parent_tag with attributes name and id. Created an other tag > child_tag inheriting from parent_tag . And gave attribute names for > child_tag same as that of parent_tag. child_tag is successfully created. > Associated child_tag to an entity. Atlas UI prompts values for 4 attributes > as : > name : > id: > name: > id: > Values provided for last set of name ,id are finally assigned to the tag > associated for the entity. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (ATLAS-1714) UI : Properties tab doesn't load when an entity has attribute of type array of integers
[
https://issues.apache.org/jira/browse/ATLAS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964358#comment-15964358
]
Keval Bhatt edited comment on ATLAS-1714 at 4/12/17 1:00 PM:
-
Thanks [~nixonrodrigues] for review, Patch is committed in master
(http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/97209e81) and
committed in 0.8-incubating
(http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/080b14ee)
was (Author: kevalbhatt18):
Thanks [~nixonrodrigues] for review, Patch committed in master
(http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/97209e81)
> UI : Properties tab doesn't load when an entity has attribute of type array
> of integers
>
>
> Key: ATLAS-1714
> URL: https://issues.apache.org/jira/browse/ATLAS-1714
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
> Attachments: ATLAS-1714.patch
>
>
> Created a type with array of integers as on of its attributes :
> {code}
> {
>"name":"type_set_int",
>"isOptional":true,
>"isUnique":false,
>"isIndexable":false,
>"typeName":"array",
>"valuesMaxCount":1,
>"cardinality":"SET",
>"valuesMinCount":0
> }
> {code}
> Created an entity of the type with value for type_set_int as [1,2,3]. Entity
> is created with 200 OK.
> Following exception is thrown in console tab :
> {code}
> Uncaught TypeError: inputOutputField.indexOf is not a function
> at http://172.27.16.74:21000/js/utils/CommonViewFunction.js:148:46
> at Array.map (native)
> at Object.CommonViewFunction.propertyTable
> (http://172.27.16.74:21000/js/utils/CommonViewFunction.js:129:39)
> at n.entityTableGenerate
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:68:48)
> at n.onRender
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:56:22)
> at
> http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:7823
> at n.triggerMethod
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:20703)
> at n.render
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:21699)
> at n.render
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:30148)
> at constructor.show
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:11890)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1732) After Zoom_out from Lineage view scroll stopped working
[ https://issues.apache.org/jira/browse/ATLAS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1732: --- Attachment: ATLAS-1732.patch > After Zoom_out from Lineage view scroll stopped working > --- > > Key: ATLAS-1732 > URL: https://issues.apache.org/jira/browse/ATLAS-1732 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating > > Attachments: ATLAS-1732.patch > > > Steps to reproduce. > * Collapse Lineage window. > * Then click on zoom-in button > * Then click on zoom-out button > After performing the above step you will see scroll stopped working. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1714) UI : Properties tab doesn't load when an entity has attribute of type array of integers
[
https://issues.apache.org/jira/browse/ATLAS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-1714:
---
Attachment: ATLAS-1714.patch
> UI : Properties tab doesn't load when an entity has attribute of type array
> of integers
>
>
> Key: ATLAS-1714
> URL: https://issues.apache.org/jira/browse/ATLAS-1714
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
> Attachments: ATLAS-1714.patch
>
>
> Created a type with array of integers as on of its attributes :
> {code}
> {
>"name":"type_set_int",
>"isOptional":true,
>"isUnique":false,
>"isIndexable":false,
>"typeName":"array",
>"valuesMaxCount":1,
>"cardinality":"SET",
>"valuesMinCount":0
> }
> {code}
> Created an entity of the type with value for type_set_int as [1,2,3]. Entity
> is created with 200 OK.
> Following exception is thrown in console tab :
> {code}
> Uncaught TypeError: inputOutputField.indexOf is not a function
> at http://172.27.16.74:21000/js/utils/CommonViewFunction.js:148:46
> at Array.map (native)
> at Object.CommonViewFunction.propertyTable
> (http://172.27.16.74:21000/js/utils/CommonViewFunction.js:129:39)
> at n.entityTableGenerate
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:68:48)
> at n.onRender
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:56:22)
> at
> http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:7823
> at n.triggerMethod
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:20703)
> at n.render
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:21699)
> at n.render
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:30148)
> at constructor.show
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:11890)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1714) UI : Properties tab doesn't load when an entity has attribute of type array of integers
[
https://issues.apache.org/jira/browse/ATLAS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-1714:
---
Attachment: (was: ATLAS-1714.patch)
> UI : Properties tab doesn't load when an entity has attribute of type array
> of integers
>
>
> Key: ATLAS-1714
> URL: https://issues.apache.org/jira/browse/ATLAS-1714
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>
> Created a type with array of integers as on of its attributes :
> {code}
> {
>"name":"type_set_int",
>"isOptional":true,
>"isUnique":false,
>"isIndexable":false,
>"typeName":"array",
>"valuesMaxCount":1,
>"cardinality":"SET",
>"valuesMinCount":0
> }
> {code}
> Created an entity of the type with value for type_set_int as [1,2,3]. Entity
> is created with 200 OK.
> Following exception is thrown in console tab :
> {code}
> Uncaught TypeError: inputOutputField.indexOf is not a function
> at http://172.27.16.74:21000/js/utils/CommonViewFunction.js:148:46
> at Array.map (native)
> at Object.CommonViewFunction.propertyTable
> (http://172.27.16.74:21000/js/utils/CommonViewFunction.js:129:39)
> at n.entityTableGenerate
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:68:48)
> at n.onRender
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:56:22)
> at
> http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:7823
> at n.triggerMethod
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:20703)
> at n.render
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:21699)
> at n.render
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:30148)
> at constructor.show
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:11890)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1732) After Zoom_out from Lineage view scroll stopped working
[ https://issues.apache.org/jira/browse/ATLAS-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1732: --- Description: Steps to reproduce. * Collapse Lineage window. * Then click on zoom-in button * Then click on zoom-out button After performing the above step you will see scroll stopped working. > After Zoom_out from Lineage view scroll stopped working > --- > > Key: ATLAS-1732 > URL: https://issues.apache.org/jira/browse/ATLAS-1732 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating > > > Steps to reproduce. > * Collapse Lineage window. > * Then click on zoom-in button > * Then click on zoom-out button > After performing the above step you will see scroll stopped working. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1732) After Zoom_out from Lineage view scroll stopped working
Keval Bhatt created ATLAS-1732: -- Summary: After Zoom_out from Lineage view scroll stopped working Key: ATLAS-1732 URL: https://issues.apache.org/jira/browse/ATLAS-1732 Project: Atlas Issue Type: Bug Components: atlas-webui Affects Versions: 0.9-incubating Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 0.9-incubating -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1433) Atlas allows creation of tag with attributes' name same as that of its parent tags.
[ https://issues.apache.org/jira/browse/ATLAS-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964398#comment-15964398 ] Keval Bhatt commented on ATLAS-1433: committed to master (http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/c9a91264) > Atlas allows creation of tag with attributes' name same as that of its parent > tags. > --- > > Key: ATLAS-1433 > URL: https://issues.apache.org/jira/browse/ATLAS-1433 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Sharmadha Sainath >Assignee: Kalyani Kashikar > Attachments: ATLAS-1433.1.patch, ATLAS-1433.patch > > > Created a tag parent_tag with attributes name and id. Created an other tag > child_tag inheriting from parent_tag . And gave attribute names for > child_tag same as that of parent_tag. child_tag is successfully created. > Associated child_tag to an entity. Atlas UI prompts values for 4 attributes > as : > name : > id: > name: > id: > Values provided for last set of name ,id are finally assigned to the tag > associated for the entity. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1718) In Create tag UI, attribute datatype should provide enum-types in drop-down along with built-in types
[ https://issues.apache.org/jira/browse/ATLAS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964388#comment-15964388 ] Keval Bhatt commented on ATLAS-1718: [~Kalyanikashikar] you will have to wait for enum API success then show content. i.e show loader first at popup initialize and hide loader after api complete. > In Create tag UI, attribute datatype should provide enum-types in drop-down > along with built-in types > - > > Key: ATLAS-1718 > URL: https://issues.apache.org/jira/browse/ATLAS-1718 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.9-incubating >Reporter: Kalyani Kashikar >Assignee: Kalyani Kashikar > Fix For: 0.9-incubating > > Attachments: ATLAS-1718.patch > > > In Create/update tag UI, attribute datatype should provide enum-types in > drop-down along with built-in types. ( like hive_principal_type, file_action) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1433) Atlas allows creation of tag with attributes' name same as that of its parent tags.
[ https://issues.apache.org/jira/browse/ATLAS-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964364#comment-15964364 ] Keval Bhatt commented on ATLAS-1433: +1 for the patch > Atlas allows creation of tag with attributes' name same as that of its parent > tags. > --- > > Key: ATLAS-1433 > URL: https://issues.apache.org/jira/browse/ATLAS-1433 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Sharmadha Sainath >Assignee: Kalyani Kashikar > Attachments: ATLAS-1433.1.patch, ATLAS-1433.patch > > > Created a tag parent_tag with attributes name and id. Created an other tag > child_tag inheriting from parent_tag . And gave attribute names for > child_tag same as that of parent_tag. child_tag is successfully created. > Associated child_tag to an entity. Atlas UI prompts values for 4 attributes > as : > name : > id: > name: > id: > Values provided for last set of name ,id are finally assigned to the tag > associated for the entity. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1714) UI : Properties tab doesn't load when an entity has attribute of type array of integers
[
https://issues.apache.org/jira/browse/ATLAS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt updated ATLAS-1714:
---
Attachment: ATLAS-1714.patch
> UI : Properties tab doesn't load when an entity has attribute of type array
> of integers
>
>
> Key: ATLAS-1714
> URL: https://issues.apache.org/jira/browse/ATLAS-1714
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
> Attachments: ATLAS-1714.patch
>
>
> Created a type with array of integers as on of its attributes :
> {code}
> {
>"name":"type_set_int",
>"isOptional":true,
>"isUnique":false,
>"isIndexable":false,
>"typeName":"array",
>"valuesMaxCount":1,
>"cardinality":"SET",
>"valuesMinCount":0
> }
> {code}
> Created an entity of the type with value for type_set_int as [1,2,3]. Entity
> is created with 200 OK.
> Following exception is thrown in console tab :
> {code}
> Uncaught TypeError: inputOutputField.indexOf is not a function
> at http://172.27.16.74:21000/js/utils/CommonViewFunction.js:148:46
> at Array.map (native)
> at Object.CommonViewFunction.propertyTable
> (http://172.27.16.74:21000/js/utils/CommonViewFunction.js:129:39)
> at n.entityTableGenerate
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:68:48)
> at n.onRender
> (http://172.27.16.74:21000/js/views/entity/EntityDetailTableLayoutView.js:56:22)
> at
> http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:7823
> at n.triggerMethod
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:20703)
> at n.render
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:21699)
> at n.render
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:30148)
> at constructor.show
> (http://172.27.16.74:21000/js/libs/backbone-marionette/backbone.marionette.min.js:20:11890)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1688) Resize Lineage window will move legend out of the Lineage panel
[ https://issues.apache.org/jira/browse/ATLAS-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1688: --- Attachment: ATLAS-1688.3.patch > Resize Lineage window will move legend out of the Lineage panel > --- > > Key: ATLAS-1688 > URL: https://issues.apache.org/jira/browse/ATLAS-1688 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating > > Attachments: ATLAS-1688.2.patch, ATLAS-1688.3.patch, > ATLAS-1688.patch, Lineage_out_of_the_panel.png, tooltip.png > > > 1 ) In Detail page of entity try to resize the panel of Lineage it will move > both Legend and graph out of the panel. > 2 ) Tool tip size is too big it should have scroll inside it. > I have attached the screen shot for better understanding. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1688) Resize Lineage window will move legend out of the Lineage panel
[ https://issues.apache.org/jira/browse/ATLAS-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1688: --- Attachment: ATLAS-1688.2.patch > Resize Lineage window will move legend out of the Lineage panel > --- > > Key: ATLAS-1688 > URL: https://issues.apache.org/jira/browse/ATLAS-1688 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating > > Attachments: ATLAS-1688.2.patch, ATLAS-1688.patch, > Lineage_out_of_the_panel.png, tooltip.png > > > 1 ) In Detail page of entity try to resize the panel of Lineage it will move > both Legend and graph out of the panel. > 2 ) Tool tip size is too big it should have scroll inside it. > I have attached the screen shot for better understanding. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1688) Resize Lineage window will move legend out of the Lineage panel
[ https://issues.apache.org/jira/browse/ATLAS-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1688: --- Attachment: Lineage_out_of_the_panel.png > Resize Lineage window will move legend out of the Lineage panel > --- > > Key: ATLAS-1688 > URL: https://issues.apache.org/jira/browse/ATLAS-1688 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating > > Attachments: ATLAS-1688.patch, Lineage_out_of_the_panel.png, > tooltip.png > > > 1 ) In Detail page of entity try to resize the panel of Lineage it will move > both Legend and graph out of the panel. > 2 ) Tool tip size is too big it should have scroll inside it. > I have attached the screen shot for better understanding. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1688) Resize Lineage window will move legend out of the Lineage panel
[ https://issues.apache.org/jira/browse/ATLAS-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1688: --- Attachment: tooltip.png > Resize Lineage window will move legend out of the Lineage panel > --- > > Key: ATLAS-1688 > URL: https://issues.apache.org/jira/browse/ATLAS-1688 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating > > Attachments: ATLAS-1688.patch, tooltip.png > > > 1 ) In Detail page of entity try to resize the panel of Lineage it will move > both Legend and graph out of the panel. > 2 ) Tool tip size is too big it should have scroll inside it. > I have attached the screen shot for better understanding. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1688) Resize Lineage window will move legend out of the Lineage panel
[ https://issues.apache.org/jira/browse/ATLAS-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1688: --- Description: 1 ) In Detail page of entity try to resize the panel of Lineage it will move both Legend and graph out of the panel. 2 ) Tool tip size is too big it should have scroll inside it. I have attached the screen shot for better understanding. was: In Detail page of entity try to resize the panel of Lineage it will move both Legend and graph out of the panel. I have attached the screen shot for better understanding. > Resize Lineage window will move legend out of the Lineage panel > --- > > Key: ATLAS-1688 > URL: https://issues.apache.org/jira/browse/ATLAS-1688 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating > > Attachments: ATLAS-1688.patch > > > 1 ) In Detail page of entity try to resize the panel of Lineage it will move > both Legend and graph out of the panel. > 2 ) Tool tip size is too big it should have scroll inside it. > I have attached the screen shot for better understanding. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1688) Resize Lineage window will move legend out of the Lineage panel
[ https://issues.apache.org/jira/browse/ATLAS-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1688: --- Description: In Detail page of entity try to resize the panel of Lineage it will move both Legend and graph out of the panel. I have attached the screen shot for better understanding. > Resize Lineage window will move legend out of the Lineage panel > --- > > Key: ATLAS-1688 > URL: https://issues.apache.org/jira/browse/ATLAS-1688 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating > > Attachments: ATLAS-1688.patch > > > In Detail page of entity try to resize the panel of Lineage it will move both > Legend and graph out of the panel. > I have attached the screen shot for better understanding. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1688) Resize Lineage window will move legend out of the Lineage panel
[ https://issues.apache.org/jira/browse/ATLAS-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1688: --- Summary: Resize Lineage window will move legend out of the Lineage panel (was: Resize Lineage window will move legends out of the Lineage panel) > Resize Lineage window will move legend out of the Lineage panel > --- > > Key: ATLAS-1688 > URL: https://issues.apache.org/jira/browse/ATLAS-1688 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating > > Attachments: ATLAS-1688.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1688) Resize Lineage window will move legends out of the Lineage panel
[ https://issues.apache.org/jira/browse/ATLAS-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1688: --- Attachment: ATLAS-1688.patch > Resize Lineage window will move legends out of the Lineage panel > > > Key: ATLAS-1688 > URL: https://issues.apache.org/jira/browse/ATLAS-1688 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating > > Attachments: ATLAS-1688.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1688) Resize Lineage window will move legends out of the Lineage panel
Keval Bhatt created ATLAS-1688: -- Summary: Resize Lineage window will move legends out of the Lineage panel Key: ATLAS-1688 URL: https://issues.apache.org/jira/browse/ATLAS-1688 Project: Atlas Issue Type: Bug Affects Versions: 0.9-incubating Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 0.9-incubating -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1682) New overlay loader added in all Tables and toggle between basic and Advance search fix
[ https://issues.apache.org/jira/browse/ATLAS-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1682: --- Summary: New overlay loader added in all Tables and toggle between basic and Advance search fix (was: New Loader added in Table View and toggle between basic and Advance fix) > New overlay loader added in all Tables and toggle between basic and Advance > search fix > -- > > Key: ATLAS-1682 > URL: https://issues.apache.org/jira/browse/ATLAS-1682 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating > > > Patch contain following changes. > # Added Overlay Loader in all Tables. > # Heading change from Lineage to LINEAGE & IMPACT > # While adding attributes if any input is empty and user clicks on add button > it will close popup with warning message and wont add any attribute. > # Click on "..." button from list of Tags it will redirect to Basic search > page. > # Click on "..." button will search for tag with old type selected issue. > # Clicking on refresh button of Search Tab will refresh search table view > also. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1682) New Loader added in Table View and toggle between basic and Advance fix
[ https://issues.apache.org/jira/browse/ATLAS-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1682: --- Description: Patch contain following changes. # Added Overlay Loader in all Tables. # Heading change from Lineage to LINEAGE & IMPACT # While adding attributes if any input is empty and user clicks on add button it will close popup with warning message and wont add any attribute. # Click on "..." button from list of Tags it will redirect to Basic search page. # Click on "..." button will search for tag with old type selected issue. # Clicking on refresh button of Search Tab will refresh search table view also. was: Patch contain following changes. # Added Overlay Loader in all Tables. # Heading change from Lineage to LINEAGE & IMPACT # While adding attributes if any input is empty and user clicks on add button it will close popup with warning message and wont add any attribute. # Click on "..." button from list of Tags it will redirect to Basic search page. # Click on "..." button will search for tag with old type selected issue. > New Loader added in Table View and toggle between basic and Advance fix > --- > > Key: ATLAS-1682 > URL: https://issues.apache.org/jira/browse/ATLAS-1682 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating > > > Patch contain following changes. > # Added Overlay Loader in all Tables. > # Heading change from Lineage to LINEAGE & IMPACT > # While adding attributes if any input is empty and user clicks on add button > it will close popup with warning message and wont add any attribute. > # Click on "..." button from list of Tags it will redirect to Basic search > page. > # Click on "..." button will search for tag with old type selected issue. > # Clicking on refresh button of Search Tab will refresh search table view > also. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1682) New Loader added in Table View and toggle between basic and Advance fix
[ https://issues.apache.org/jira/browse/ATLAS-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1682: --- Description: Patch contain following changes. # Added Overlay Loader in all Tables. # Heading change from Lineage to LINEAGE & IMPACT # While adding attributes if any input is empty and user clicks on add button it will close popup with warning message and wont add any attribute. # Click on "..." button from list of Tags it will redirect to Basic search page. # Click on "..." button will search for tag with old type selected issue. > New Loader added in Table View and toggle between basic and Advance fix > --- > > Key: ATLAS-1682 > URL: https://issues.apache.org/jira/browse/ATLAS-1682 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.9-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.9-incubating > > > Patch contain following changes. > # Added Overlay Loader in all Tables. > # Heading change from Lineage to LINEAGE & IMPACT > # While adding attributes if any input is empty and user clicks on add button > it will close popup with warning message and wont add any attribute. > # Click on "..." button from list of Tags it will redirect to Basic search > page. > # Click on "..." button will search for tag with old type selected issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1658) Terms list is showing incorrectly in Detail page and Search page
[ https://issues.apache.org/jira/browse/ATLAS-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1658: --- Attachment: ATLAS-1658.patch > Terms list is showing incorrectly in Detail page and Search page > > > Key: ATLAS-1658 > URL: https://issues.apache.org/jira/browse/ATLAS-1658 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.8-incubating > > Attachments: ATLAS-1658.patch > > > In Detail page of entity Terms are listed under Tag's tab. > In Search Result Page Terms are not rendered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1658) Terms list is showing incorrectly in Detail page and Search page
Keval Bhatt created ATLAS-1658: -- Summary: Terms list is showing incorrectly in Detail page and Search page Key: ATLAS-1658 URL: https://issues.apache.org/jira/browse/ATLAS-1658 Project: Atlas Issue Type: Bug Affects Versions: 0.8-incubating Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 0.8-incubating In Detail page of entity Terms are listed under Tag's tab. In Search Result Page Terms are not rendered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1652) Change version in 0.8 branch to 0.8-incubating
[ https://issues.apache.org/jira/browse/ATLAS-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898965#comment-15898965 ] Keval Bhatt commented on ATLAS-1652: +1 for the patch > Change version in 0.8 branch to 0.8-incubating > -- > > Key: ATLAS-1652 > URL: https://issues.apache.org/jira/browse/ATLAS-1652 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.8-incubating >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj > Fix For: 0.8-incubating > > Attachments: ATLAS-1652.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1651) Change master version to 0.9-incubating
[ https://issues.apache.org/jira/browse/ATLAS-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898953#comment-15898953 ] Keval Bhatt commented on ATLAS-1651: +1 for the patch > Change master version to 0.9-incubating > --- > > Key: ATLAS-1651 > URL: https://issues.apache.org/jira/browse/ATLAS-1651 > Project: Atlas > Issue Type: Sub-task >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj > Fix For: trunk > > Attachments: ATLAS-1651.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (ATLAS-1644) Taxonomy API /api/atlas/v1/taxonomies is broken.
[
https://issues.apache.org/jira/browse/ATLAS-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keval Bhatt reassigned ATLAS-1644:
--
Assignee: Madhan Neethiraj
> Taxonomy API /api/atlas/v1/taxonomies is broken.
>
>
> Key: ATLAS-1644
> URL: https://issues.apache.org/jira/browse/ATLAS-1644
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Madhan Neethiraj
>Priority: Blocker
>
> The following API throws 500 Internal server error
> {code}
> http://localhost:21000/api/atlas/v1/taxonomies
> {code}
> with the following error notification :
> {code}
> An unexpected error has occurred.
> org.apache.atlas.catalog.exception.CatalogRuntimeException: :
> java.lang.ClassCastException:
> org.apache.atlas.repository.graphdb.titan0.Titan0Vertex cannot be cast to
> com.tinkerpop.blueprints.Element
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (ATLAS-1635) Qualified name in v1 lineage APIs have name even when Qualified name for that entity is available.
[
https://issues.apache.org/jira/browse/ATLAS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15896883#comment-15896883
]
Keval Bhatt commented on ATLAS-1635:
+1 for the patch
> Qualified name in v1 lineage APIs have name even when Qualified name for that
> entity is available.
> --
>
> Key: ATLAS-1635
> URL: https://issues.apache.org/jira/browse/ATLAS-1635
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Sharmadha Sainath
>Assignee: Madhan Neethiraj
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1635.patch
>
>
> Following is the API response of the below V1 API.
> {code}
> http://localhost:21000/api/atlas/lineage/317a2edf-d280-4b36-a385-11d56f99dc66/inputs/graph
> {code}
> {code}
> {
> requestId: "pool-1-thread-9 - 5f7f24de-97a0-467e-9e23-6d9c385701ff",
> results: {
> jsonClass:
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> typeName: "__tempQueryResultStruct2",
> values: {
> vertices: {
> 317 a2edf - d280 - 4 b36 - a385 - 11
> d56f99dc66: {
> jsonClass:
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> typeName: "__tempQueryResultStruct0",
> values: {
> qualifiedName: "t1ctas",
> vertexId: {
> jsonClass:
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> typeName: "__IdType",
> values: {
> guid:
> "317a2edf-d280-4b36-a385-11d56f99dc66",
> state: "ACTIVE",
> typeName:
> "hive_table"
> }
> },
> name: "t1ctas"
> }
> },
> fd9caa83 - c861 - 4314 - a33d - 56e9 dcea1c44: {
> jsonClass:
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> typeName: "__tempQueryResultStruct1",
> values: {
> qualifiedName: "t1",
> vertexId: {
> jsonClass:
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> typeName: "__IdType",
> values: {
> guid:
> "fd9caa83-c861-4314-a33d-56e9dcea1c44",
> state: "ACTIVE",
> typeName:
> "hive_table"
> }
> },
> name: "t1"
> }
> }
> },
> edges: {
> 317 a2edf - d280 - 4 b36 - a385 - 11
> d56f99dc66: [
> "305e65b3-6058-4ac8-be3c-9d60d42df4d4"
> ],
> 305e65 b3 - 6058 - 4 ac8 - be3c - 9
> d60d42df4d4: [
> "fd9caa83-c861-4314-a33d-56e9dcea1c44"
> ]
> }
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (ATLAS-1640) Update entity not showing selected values for array-entity attributes when its is required
[ https://issues.apache.org/jira/browse/ATLAS-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1640: --- Description: * During updating from UI if array-entity attributes is required then value is not showing selected in UI. However valid options are present in drop down. * Create entity button is visible in tag details page it should be visible only on search result page. was:During updating from UI if array-entity attributes is required then value is not showing selected in UI. However valid options are present in drop down. > Update entity not showing selected values for array-entity attributes when > its is required > --- > > Key: ATLAS-1640 > URL: https://issues.apache.org/jira/browse/ATLAS-1640 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.8-incubating > > Attachments: ATLAS-1640.1.patch, ATLAS-1640.patch > > > * During updating from UI if array-entity attributes is required then value > is not showing selected in UI. However valid options are present in drop down. > * Create entity button is visible in tag details page it should be visible > only on search result page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (ATLAS-1641) UI Regression : Clicking on "Add Tag" button in the Search result table in index.html page doesn't open up the Add Tag window.
[ https://issues.apache.org/jira/browse/ATLAS-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt resolved ATLAS-1641. Resolution: Fixed Duplicate ATLAS-1638 > UI Regression : Clicking on "Add Tag" button in the Search result table in > index.html page doesn't open up the Add Tag window. > -- > > Key: ATLAS-1641 > URL: https://issues.apache.org/jira/browse/ATLAS-1641 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 0.8-incubating >Reporter: Sharmadha Sainath >Assignee: Keval Bhatt >Priority: Critical > > Clicking on "Add Tag" button corresponding to any entity in the Search result > table in index.html page doesn't open up the Add Tag window. Network tab in > the browser shows no action or query being fired on clicking the button. > But in the detailsPage of entity , Add tag button is clickable and opens up > the Add Tag Window. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1640) Update entity not showing selected values for array-entity attributes when its is required
[ https://issues.apache.org/jira/browse/ATLAS-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1640: --- Description: While update time if array-entity attribute is required then value is not showing selected However valid options are present in drop down. > Update entity not showing selected values for array-entity attributes when > its is required > --- > > Key: ATLAS-1640 > URL: https://issues.apache.org/jira/browse/ATLAS-1640 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.8-incubating > > Attachments: ATLAS-1640.1.patch, ATLAS-1640.patch > > > While update time if array-entity attribute is required then value is not > showing selected However valid options are present in drop down. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1640) Update entity not showing selected values for array-entity attributes when its is required
[ https://issues.apache.org/jira/browse/ATLAS-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1640: --- Attachment: ATLAS-1640.1.patch > Update entity not showing selected values for array-entity attributes when > its is required > --- > > Key: ATLAS-1640 > URL: https://issues.apache.org/jira/browse/ATLAS-1640 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.8-incubating > > Attachments: ATLAS-1640.1.patch, ATLAS-1640.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1640) Update entity not showing selected values for array-entity attributes when its is required
[ https://issues.apache.org/jira/browse/ATLAS-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1640: --- Attachment: ATLAS-1640.patch > Update entity not showing selected values for array-entity attributes when > its is required > --- > > Key: ATLAS-1640 > URL: https://issues.apache.org/jira/browse/ATLAS-1640 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.8-incubating > > Attachments: ATLAS-1640.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1640) Update entity not showing selected values for array-entity attributes when its is required
Keval Bhatt created ATLAS-1640: -- Summary: Update entity not showing selected values for array-entity attributes when its is required Key: ATLAS-1640 URL: https://issues.apache.org/jira/browse/ATLAS-1640 Project: Atlas Issue Type: Bug Affects Versions: 0.8-incubating Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 0.8-incubating -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ATLAS-1638) Assign Tag to multiple entity send same GUID
[ https://issues.apache.org/jira/browse/ATLAS-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-1638: --- Attachment: ATLAS-1638.patch > Assign Tag to multiple entity send same GUID > - > > Key: ATLAS-1638 > URL: https://issues.apache.org/jira/browse/ATLAS-1638 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.8-incubating >Reporter: Keval Bhatt >Assignee: Keval Bhatt > Fix For: 0.8-incubating > > Attachments: ATLAS-1638.patch > > > * Click on |+| button from search table Add- tag popup is not opened > * Search for entity then select all entity using checkbox now click on > Add-tag button and assign tag, POST API will send same GUID. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ATLAS-1638) Assign Tag to multiple entity send same GUID
Keval Bhatt created ATLAS-1638: -- Summary: Assign Tag to multiple entity send same GUID Key: ATLAS-1638 URL: https://issues.apache.org/jira/browse/ATLAS-1638 Project: Atlas Issue Type: Bug Affects Versions: 0.8-incubating Reporter: Keval Bhatt Assignee: Keval Bhatt Fix For: 0.8-incubating * Click on |+| button from search table Add- tag popup is not opened * Search for entity then select all entity using checkbox now click on Add-tag button and assign tag, POST API will send same GUID. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
