[jira] [Commented] (ATLAS-4533) UI: Triggering a third search with basic search filters does not close the filters window

2022-01-19 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on ATLAS-4533:


Commit 5dc5593f07d48be301f96cd77183d02a4bf7d16c in atlas's branch 
refs/heads/branch-2.0 from Farhan Khan
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=5dc5593 ]

ATLAS-4533 : Triggering a third search with basic search filters does not close 
the filters window

Signed-off-by: Pinal Shah 
(cherry picked from commit 224f6ade1e438b930432fa1b461332f72dc4ca3c)


> UI: Triggering a third search with basic search filters does not close the 
> filters window
> -
>
> Key: ATLAS-4533
> URL: https://issues.apache.org/jira/browse/ATLAS-4533
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Farhan Khan
>Priority: Minor
> Attachments: 
> 0001-ATLAS-4533-Triggering-a-third-search-with-basic-sear.patch
>
>
> Steps:
> 1. Execute a basic search with at least one filter successfully.
> 2.After step1, add a search filter group with a different parameter and 
> execute the search. It should be successful
> 3. Go to search filters and try to repeat the search.
> You will see that nothing happens on clicking the search button. Console 
> shows the following error:
> {{Uncaught TypeError: value is undefined
> conditionalURl 
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:280
> X Underscore
> conditionalURl 
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:269
> conditionalURl 
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:270
> X Underscore
> conditionalURl 
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:269
> generateUrl 
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:288
> okAttrFilterButton 
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:292
> openAttrFilter 
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:279
> Backbone 4
> click .ok http://localhost:21000/js/modules/Modal.js?bust=1641881782114:12
> Underscore 3
> jQuery 8
> Backbone 6
> initialize 
> http://localhost:21000/js/views/search/SearchQueryView.js?bust=1641881782114:17
> Backbone 5
> openAttrFilter 
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:267
> execCb 
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> check 
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> enable 
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> init 
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> f http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> setTimeout handler*req.nextTick< 
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> f http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> openAttrFilter 
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:266
>  
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:34
> Underscore 3
> jQuery }}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (ATLAS-4533) UI: Triggering a third search with basic search filters does not close the filters window

2022-01-19 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on ATLAS-4533:


Commit 224f6ade1e438b930432fa1b461332f72dc4ca3c in atlas's branch 
refs/heads/master from Farhan Khan
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=224f6ad ]

ATLAS-4533 : Triggering a third search with basic search filters does not close 
the filters window

Signed-off-by: Pinal Shah 


> UI: Triggering a third search with basic search filters does not close the 
> filters window
> -
>
> Key: ATLAS-4533
> URL: https://issues.apache.org/jira/browse/ATLAS-4533
> Project: Atlas
>  Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Farhan Khan
>Priority: Minor
> Attachments: 
> 0001-ATLAS-4533-Triggering-a-third-search-with-basic-sear.patch
>
>
> Steps:
> 1. Execute a basic search with at least one filter successfully.
> 2.After step1, add a search filter group with a different parameter and 
> execute the search. It should be successful
> 3. Go to search filters and try to repeat the search.
> You will see that nothing happens on clicking the search button. Console 
> shows the following error:
> {{Uncaught TypeError: value is undefined
> conditionalURl 
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:280
> X Underscore
> conditionalURl 
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:269
> conditionalURl 
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:270
> X Underscore
> conditionalURl 
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:269
> generateUrl 
> http://localhost:21000/js/utils/CommonViewFunction.js?bust=1641881782114:288
> okAttrFilterButton 
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:292
> openAttrFilter 
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:279
> Backbone 4
> click .ok http://localhost:21000/js/modules/Modal.js?bust=1641881782114:12
> Underscore 3
> jQuery 8
> Backbone 6
> initialize 
> http://localhost:21000/js/views/search/SearchQueryView.js?bust=1641881782114:17
> Backbone 5
> openAttrFilter 
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:267
> execCb 
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> check 
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> enable 
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> init 
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> f http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> setTimeout handler*req.nextTick< 
> http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> f http://localhost:21000/js/libs/requirejs/require.js?bust=1641881782114:1
> openAttrFilter 
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:266
>  
> http://localhost:21000/js/views/search/SearchLayoutView.js?bust=1641881782114:34
> Underscore 3
> jQuery }}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (ATLAS-4018) 编译失败

2022-01-19 Thread Jira 


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

方磊 commented on ATLAS-4018:
---

you can use node@12

> 编译失败
> 
>
> Key: ATLAS-4018
> URL: https://issues.apache.org/jira/browse/ATLAS-4018
> Project: Atlas
>  Issue Type: Improvement
> Environment: apache-maven-3.6.3
> apache-atlas-sources-2.1.0
>Reporter: alanding
>Priority: Major
>
> [ERROR] Unable to save binary 
> /data01/atlas/apache-atlas-sources-2.1.0/dashboardv2/target/node_modules/node-sass/vendor/linux-x64-72
>  : Error: EACCES: permission denied, mkdir 
> '/data01/atlas/apache-atlas-sources-2.1.0/dashboardv2/target/node_modules/node-sass/vendor'
> [ERROR] at Object.mkdirSync (fs.js:840:3)
> [ERROR] at sync 
> (/data01/atlas/apache-atlas-sources-2.1.0/dashboardv2/target/node_modules/mkdirp/index.js:72:13)
> [ERROR] at Function.sync 
> (/data01/atlas/apache-atlas-sources-2.1.0/dashboardv2/target/node_modules/mkdirp/index.js:78:24)
> [ERROR] at checkAndDownloadBinary 
> (/data01/atlas/apache-atlas-sources-2.1.0/dashboardv2/target/node_modules/node-sass/scripts/install.js:114:11)
> [ERROR] at Object. 
> (/data01/atlas/apache-atlas-sources-2.1.0/dashboardv2/target/node_modules/node-sass/scripts/install.js:157:1)
> [ERROR] at Module._compile (internal/modules/cjs/loader.js:1157:30)
> [ERROR] at Object.Module._extensions..js 
> (internal/modules/cjs/loader.js:1177:10)
> [ERROR] at Module.load (internal/modules/cjs/loader.js:1001:32)
> [ERROR] at Function.Module._load (internal/modules/cjs/loader.js:900:14)
> [ERROR] at Function.executeUserEntryPoint [as runMain] 
> (internal/modules/run_main.js:74:12) {
> [ERROR] errno: -13,
> [ERROR] syscall: 'mkdir',
> [ERROR] code: 'EACCES',
> [ERROR] path: 
> '/data01/atlas/apache-atlas-sources-2.1.0/dashboardv2/target/node_modules/node-sass/vendor'
> [ERROR] }
>  
>  
>  
> [INFO] Apache Atlas UI 2.1.0 .. FAILURE [ 11.911 
> s]
> [INFO] Apache Atlas New UI 2.1.0 .. SKIPPED
> [INFO] Apache Atlas Web Application 2.1.0 . SKIPPED
> [INFO] Apache Atlas Documentation 2.1.0 ... SKIPPED
> [INFO] Apache Atlas FileSystem Model 2.1.0  SKIPPED
> [INFO] Apache Atlas Plugin Classloader 2.1.0 .. SKIPPED
> [INFO] Apache Atlas Hive Bridge Shim 2.1.0  SKIPPED
> [INFO] Apache Atlas Hive Bridge 2.1.0 . SKIPPED
> [INFO] Apache Atlas Falcon Bridge Shim 2.1.0 .. SKIPPED
> [INFO] Apache Atlas Falcon Bridge 2.1.0 ... SKIPPED
> [INFO] Apache Atlas Sqoop Bridge Shim 2.1.0 ... SKIPPED
> [INFO] Apache Atlas Sqoop Bridge 2.1.0  SKIPPED
> [INFO] Apache Atlas Storm Bridge Shim 2.1.0 ... SKIPPED
> [INFO] Apache Atlas Storm Bridge 2.1.0  SKIPPED
> [INFO] Apache Atlas Hbase Bridge Shim 2.1.0 ... SKIPPED
> [INFO] Apache Atlas Hbase Bridge 2.1.0  SKIPPED
> [INFO] Apache HBase - Testing Util 2.1.0 .. SKIPPED
> [INFO] Apache Atlas Kafka Bridge 2.1.0  SKIPPED
> [INFO] Apache Atlas classification updater 2.1.0 .. SKIPPED
> [INFO] Apache Atlas Impala Hook API 2.1.0 . SKIPPED
> [INFO] Apache Atlas Impala Bridge Shim 2.1.0 .. SKIPPED
> [INFO] Apache Atlas Impala Bridge 2.1.0 ... SKIPPED
> [INFO] Apache Atlas Distribution 2.1.0  SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 03:29 min
> [INFO] Finished at: 2020-11-10T18:21:18+08:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> com.github.eirslett:frontend-maven-plugin:1.4:npm (npm install) on project 
> atlas-dashboardv2: Failed to run task: 'npm install' failed. 
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1 
> (Exit value: 1) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal com.github.eirslett:frontend-maven-plugin:1.4:npm (npm install) on 
> project atlas-dashboardv2: Failed to run task



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (ATLAS-4537) neet doucment about how to config impala hook

2022-01-19 Thread Jira 
方磊 created ATLAS-4537:
-

 Summary: neet doucment about how to config impala hook
 Key: ATLAS-4537
 URL: https://issues.apache.org/jira/browse/ATLAS-4537
 Project: Atlas
  Issue Type: Wish
Reporter: 方磊


I don't know how to confige the impala hook. where could I found the document?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (ATLAS-4522) Updating typedef with new supertype should be allowed only if attributes are unique compared to other existing supertypes

2022-01-19 Thread Sarath Subramanian (Jira) 


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

Sarath Subramanian updated ATLAS-4522:
--
Fix Version/s: 3.0.0
   2.3.0

> Updating typedef with new supertype should be allowed only if attributes are 
> unique compared to other existing supertypes
> -
>
> Key: ATLAS-4522
> URL: https://issues.apache.org/jira/browse/ATLAS-4522
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> 1.Typedef1 with attributes \{a,b,c}
> 2. Typedef2 with attributes \{d} and superType\{Typedef1}
> 3. We created entities for these and everything is fine until here
> 4. Typedef3 with attributes\{a,b,c} => Attributes are same as Typedef1
> 5. Now we updated Typedef2 with one more supertype as below
> Typedef2 with superType\{Typedef1, Typedef3}
> 6. All the Typedef2 entities are having \{a,b,c} attribute values as null and 
> because of that when user is searching entity of Typedef2 by it's name not 
> returning the result.
> Root cause of the issue is that attributes in Typedef2 from SuperType- 
> Typedef1 be overridden by SuperType-Typedef2 attributes as attribute names 
> are same for Typedef1 & Typedef2
> Updating typedef with new super types should be allowed only if attributes of 
> new supertype are unique and not present in any other existing supertypes.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (ATLAS-4522) Updating typedef with new supertype should be allowed only if attributes are unique compared to other existing supertypes

2022-01-19 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on ATLAS-4522:


Commit 1d026fa463bbda95ac78b4a8db377412989077b6 in atlas's branch 
refs/heads/branch-2.0 from Radhika Kundam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1d026fa ]

ATLAS-4522: Updating typedef with new supertype should be allowed only if 
attributes are unique compared to other existing supertypes

Signed-off-by: Sarath Subramanian 
(cherry picked from commit 1b0dff89e26ff06f7b14456369975fe696f05ebc)


> Updating typedef with new supertype should be allowed only if attributes are 
> unique compared to other existing supertypes
> -
>
> Key: ATLAS-4522
> URL: https://issues.apache.org/jira/browse/ATLAS-4522
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> 1.Typedef1 with attributes \{a,b,c}
> 2. Typedef2 with attributes \{d} and superType\{Typedef1}
> 3. We created entities for these and everything is fine until here
> 4. Typedef3 with attributes\{a,b,c} => Attributes are same as Typedef1
> 5. Now we updated Typedef2 with one more supertype as below
> Typedef2 with superType\{Typedef1, Typedef3}
> 6. All the Typedef2 entities are having \{a,b,c} attribute values as null and 
> because of that when user is searching entity of Typedef2 by it's name not 
> returning the result.
> Root cause of the issue is that attributes in Typedef2 from SuperType- 
> Typedef1 be overridden by SuperType-Typedef2 attributes as attribute names 
> are same for Typedef1 & Typedef2
> Updating typedef with new super types should be allowed only if attributes of 
> new supertype are unique and not present in any other existing supertypes.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (ATLAS-4534) entity was deleted when edit entity by UI

2022-01-19 Thread Joseph Zhang (Jira) 


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

Joseph Zhang commented on ATLAS-4534:
-

any body has any advice? thanks 

> entity was deleted when edit entity by UI
> -
>
> Key: ATLAS-4534
> URL: https://issues.apache.org/jira/browse/ATLAS-4534
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Joseph Zhang
>Priority: Critical
>
> hi all,
> I'm using the atlas version 2.2.0, when I edit entity attribute value by 
> using the edit button on UI, the entity was deleted instead, status change to 
> "DELETED".
> I did not figure out how this happened, the debug info as below. Please help 
> me on this. thanks in advance.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (ATLAS-4522) Updating typedef with new supertype should be allowed only if attributes are unique compared to other existing supertypes

2022-01-19 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on ATLAS-4522:


Commit 1b0dff89e26ff06f7b14456369975fe696f05ebc in atlas's branch 
refs/heads/master from Radhika Kundam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1b0dff8 ]

ATLAS-4522: Updating typedef with new supertype should be allowed only if 
attributes are unique compared to other existing supertypes

Signed-off-by: Sarath Subramanian 


> Updating typedef with new supertype should be allowed only if attributes are 
> unique compared to other existing supertypes
> -
>
> Key: ATLAS-4522
> URL: https://issues.apache.org/jira/browse/ATLAS-4522
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> 1.Typedef1 with attributes \{a,b,c}
> 2. Typedef2 with attributes \{d} and superType\{Typedef1}
> 3. We created entities for these and everything is fine until here
> 4. Typedef3 with attributes\{a,b,c} => Attributes are same as Typedef1
> 5. Now we updated Typedef2 with one more supertype as below
> Typedef2 with superType\{Typedef1, Typedef3}
> 6. All the Typedef2 entities are having \{a,b,c} attribute values as null and 
> because of that when user is searching entity of Typedef2 by it's name not 
> returning the result.
> Root cause of the issue is that attributes in Typedef2 from SuperType- 
> Typedef1 be overridden by SuperType-Typedef2 attributes as attribute names 
> are same for Typedef1 & Typedef2
> Updating typedef with new super types should be allowed only if attributes of 
> new supertype are unique and not present in any other existing supertypes.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)