[
https://issues.apache.org/jira/browse/ATLAS-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17136324#comment-17136324
]
yangchengkai edited comment on ATLAS-3014 at 6/16/20, 5:52 AM:
---
I got the
[
https://issues.apache.org/jira/browse/ATLAS-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17136324#comment-17136324
]
yangchengkai commented on ATLAS-3014:
-
I got the simlie error too.
I solve this problem by set
[
https://issues.apache.org/jira/browse/ATLAS-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17136320#comment-17136320
]
yangchengkai commented on ATLAS-3401:
-
This should be some network problems.You can copy and paste
[
https://issues.apache.org/jira/browse/ATLAS-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17136314#comment-17136314
]
yangchengkai commented on ATLAS-3166:
-
This seems to be some solr and zookeeper compatible problems.I
liang jie created ATLAS-3843:
Summary: why there can only be one active server
Key: ATLAS-3843
URL: https://issues.apache.org/jira/browse/ATLAS-3843
Project: Atlas
Issue Type: Wish
[
https://issues.apache.org/jira/browse/ATLAS-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hannah Amundson updated ATLAS-3842:
---
Affects Version/s: 2.0.0
> Docker image failing
>
>
>
[
https://issues.apache.org/jira/browse/ATLAS-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hannah Amundson updated ATLAS-3842:
---
Labels: Docker atlas build docker maven mvn (was: )
> Docker image failing
>
[
https://issues.apache.org/jira/browse/ATLAS-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hannah Amundson updated ATLAS-3842:
---
Description:
The Dockerfile in dev-tools is not working. I keep getting this error:
Hannah Amundson created ATLAS-3842:
--
Summary: Docker image failing
Key: ATLAS-3842
URL: https://issues.apache.org/jira/browse/ATLAS-3842
Project: Atlas
Issue Type: Bug
Reporter:
Bolke, Melinda,
I think it will help to clarify what I meant by "server-side" and "UI".
- server-side: Atlas REST APIs to perform various operations on
types/entities/glossaries/..
- UI: a web-application running in a browser which calls Atlas REST APIs to
fetch data, render and update data
Hi Keval
I'm happy that you will tackle the UI part of it. However, these are not mere
UI issues and need to be tackled server side IMHO. This opinion is supported by
what the experts say[1]
Can you elaborate on how you will approach this? I have not seen a discussion.
Cheers
Bolke
[1]
Hi Bolke,
Thanks for the details on the UI issues in rendering entity name and
incorrect value storied for user-defined attributes. I am working on
updating UI to address these issues, will send a patch shortly.
If you see further issues that require a server-side update, can you please
add
[
https://issues.apache.org/jira/browse/ATLAS-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandar Ambawane reassigned ATLAS-3841:
--
Assignee: Mandar Ambawane
> Response Headers: Code refactoring
>
Mandar Ambawane created ATLAS-3841:
--
Summary: Response Headers: Code refactoring
Key: ATLAS-3841
URL: https://issues.apache.org/jira/browse/ATLAS-3841
Project: Atlas
Issue Type: Bug
[
https://issues.apache.org/jira/browse/ATLAS-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal updated ATLAS-3838:
-
Description: it will allow user to search with multiple tags and the tag
attribute filters (attribute should
15 matches
Mail list logo