[jira] [Commented] (KYLIN-3569) Server with query mode still can submit/build job
[ https://issues.apache.org/jira/browse/KYLIN-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620142#comment-16620142 ] Shaofeng SHI commented on KYLIN-3569: - This is by design; Query server won't execute job. The job can only be executed by job node. Please send your question to u...@kylin.apache.org. > Server with query mode still can submit/build job > - > > Key: KYLIN-3569 > URL: https://issues.apache.org/jira/browse/KYLIN-3569 > Project: Kylin > Issue Type: Bug > Components: Job Engine, REST Service, Security >Affects Versions: v2.4.1 > Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 >Reporter: Zongwei Li >Priority: Major > Labels: build, documentation, security > Attachments: kylinCode.png > > > From the Docs at Kylin site, > [http://kylin.apache.org/docs24/install/kylin_cluster.html] > * *query* : run query engine only; Kylin query engine accepts and answers > your SQL queries > It seems that if server set with 'kylin.server.mode=query', it should not can > support submit/build job. But as we tested, server with query mode still can > submit/build job from UI or RESTFul API. > We analyzed the source code, found that there didn't exist any protect logic > to check whether server is at 'job' or 'build' mode in service layer for > submit/build job. Already attach the source code in this issue. > This issue really confused us, because we considered query server cannot > build job in Kylin Docs and many Kylin books. And query server will exposed > to 3rd BI tool to query the data, if we forget to configure the suitable ACL > for Cubes, then the 3rd BI tool can trigger build job in any time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3526) No check for hybrid name with special character
[ https://issues.apache.org/jira/browse/KYLIN-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-3526: Fix Version/s: (was: v2.6.0) v2.5.1 > No check for hybrid name with special character > --- > > Key: KYLIN-3526 > URL: https://issues.apache.org/jira/browse/KYLIN-3526 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Na Zhai >Assignee: Roger >Priority: Minor > Fix For: v2.5.1 > > Attachments: 名称没做限制.png > > > When create hybrid，there is no check for hybrid name with special character. > Such as !@&. > Hybrid can be created successfully with name like hy! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3528) No details page for hybrid
[ https://issues.apache.org/jira/browse/KYLIN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-3528: Fix Version/s: (was: v2.6.0) v2.5.1 > No details page for hybrid > -- > > Key: KYLIN-3528 > URL: https://issues.apache.org/jira/browse/KYLIN-3528 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Na Zhai >Assignee: Roger >Priority: Minor > Fix For: v2.5.1 > > > When I click hybrid name, there is no detail page for that hybrid. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3526) No check for hybrid name with special character
[ https://issues.apache.org/jira/browse/KYLIN-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620136#comment-16620136 ] ASF subversion and git services commented on KYLIN-3526: Commit 01f45f0b1b1fefb8651e6e8bf99ad671080dccc1 in kylin's branch refs/heads/2.5.x from Emiya0306 [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=01f45f0 ] KYLIN-3526 Add check for hybrid name with special character > No check for hybrid name with special character > --- > > Key: KYLIN-3526 > URL: https://issues.apache.org/jira/browse/KYLIN-3526 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Na Zhai >Assignee: Roger >Priority: Minor > Fix For: v2.6.0 > > Attachments: 名称没做限制.png > > > When create hybrid，there is no check for hybrid name with special character. > Such as !@&. > Hybrid can be created successfully with name like hy! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3565) User login error message is inaccurate
[ https://issues.apache.org/jira/browse/KYLIN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620133#comment-16620133 ] ASF subversion and git services commented on KYLIN-3565: Commit b62b457a595c8201381c373764e370363bb6994b in kylin's branch refs/heads/2.5.x from Emiya0306 [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=b62b457 ] KYLIN-3565 User login error message is inaccurate > User login error message is inaccurate > -- > > Key: KYLIN-3565 > URL: https://issues.apache.org/jira/browse/KYLIN-3565 > Project: Kylin > Issue Type: Bug > Components: REST Service, Web >Affects Versions: v2.4.1 > Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 >Reporter: Marc Wu >Assignee: Roger >Priority: Minor > Labels: usability > Fix For: v2.5.1 > > Attachments: 2018-09-17_16-56-12.png, 2018-09-17_16-56-38.png, > 2018-09-17_16-59-31.png, image-2018-09-17-20-22-20-294.png, > image-2018-09-17-20-25-54-896.png > > > Hi Kylin team, > > We found one issue when log in Kylin. The error message will misunderstood > user. > > I couldn't log in Kylin even I input correct username & password (enable > LDAP). > So I checked the log on server, it showed me that there exist HBase > connection issues. > Root cause is that the HBase server which Kylin used as metadata server is > down, but the login message showed me that I should check my username or > password. It's really confusing. > Then I read some source codes about login module, and found out Kylin shares > the same error message for different cases. > > We suggested two options: > # redirect to global error page when HBase connection fail after login, > shows error message(e.g. System Error, please contact system administrator). > # enhance the error code for login logic, make the error message more > specific. > > There are login error message and the log. And I log in successfully after > recover HBase servers. > !image-2018-09-17-20-25-54-896.png!!image-2018-09-17-20-22-20-294.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3439) configuration "kylin.web.timezone" is Inconsistent between kylin-defaults.properties and KylinConfigBase.java
[ https://issues.apache.org/jira/browse/KYLIN-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620134#comment-16620134 ] ASF subversion and git services commented on KYLIN-3439: Commit 11387aba88d81fea074563d85125e820b8d74202 in kylin's branch refs/heads/2.5.x from tttMelody [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=11387ab ] KYLIN-3439, make default kylin.web.timezone in KylinConfigBase the same with kylin-defaults.properties > configuration "kylin.web.timezone" is Inconsistent between > kylin-defaults.properties and KylinConfigBase.java > -- > > Key: KYLIN-3439 > URL: https://issues.apache.org/jira/browse/KYLIN-3439 > Project: Kylin > Issue Type: Bug >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Minor > Fix For: v2.6.0, v2.5.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3531) Login failed with case-insensitive username
[
https://issues.apache.org/jira/browse/KYLIN-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620135#comment-16620135
]
ASF subversion and git services commented on KYLIN-3531:
Commit 683b0d997674ef8c82c64878ea94a7c576a3adff in kylin's branch
refs/heads/2.5.x from [~yichen.zhou]
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=683b0d9 ]
KYLIN-3531 Save uppercase of usernames to metadata
> Login failed with case-insensitive username
> ---
>
> Key: KYLIN-3531
> URL: https://issues.apache.org/jira/browse/KYLIN-3531
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
>Affects Versions: v2.4.0
>Reporter: Yichen Zhou
>Assignee: Yichen Zhou
>Priority: Major
> Fix For: v2.5.1
>
>
> Username is case-insensitive in login authentication but case-sensitive in
> hbase metadata.
> {quote}org.apache.kylin.common.persistence.WriteConflictException:
> Overwriting conflict /user/Admin, expect old TS 1536031295060, but it is 0
>
> org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
>
> org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:323)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:308)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:287)
>
> org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192)
>
> org.apache.kylin.rest.security.KylinUserManager.update(KylinUserManager.java:122)
>
> org.apache.kylin.rest.service.KylinUserService.updateUser(KylinUserService.java:85)
>
> org.apache.kylin.rest.security.KylinAuthenticationProvider.authenticate(KylinAuthenticationProvider.java:117)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:174)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:199)
>
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:180)
>
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3543) Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
[
https://issues.apache.org/jira/browse/KYLIN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620132#comment-16620132
]
ASF subversion and git services commented on KYLIN-3543:
Commit f3da67746e730b9f69a8bf128854c5c9d2a207a0 in kylin's branch
refs/heads/2.5.x from [~yichen.zhou]
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=f3da677 ]
KYLIN-3543 Export HBase configuration only for Spark engine
> Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
> -
>
> Key: KYLIN-3543
> URL: https://issues.apache.org/jira/browse/KYLIN-3543
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v2.5.0
>Reporter: Ted Yu
>Assignee: Yichen Zhou
>Priority: Minor
> Fix For: v2.5.1
>
>
> {code}
> out = fs.create(new Path(hbaseConfPath));
> job.getConfiguration().writeXml(out);
> {code}
> The job instance should be closed upon return from the method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3528) No details page for hybrid
[ https://issues.apache.org/jira/browse/KYLIN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620137#comment-16620137 ] ASF subversion and git services commented on KYLIN-3528: Commit 8a437773a4366919e2409ad870823c3b820952e0 in kylin's branch refs/heads/2.5.x from Emiya0306 [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=8a43777 ] KYLIN-3528 Add details page for hybrid > No details page for hybrid > -- > > Key: KYLIN-3528 > URL: https://issues.apache.org/jira/browse/KYLIN-3528 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Na Zhai >Assignee: Roger >Priority: Minor > Fix For: v2.6.0 > > > When I click hybrid name, there is no detail page for that hybrid. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KYLIN-3565) User login error message is inaccurate
[ https://issues.apache.org/jira/browse/KYLIN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI reassigned KYLIN-3565: --- Assignee: Roger (was: XiaoXiang Yu) Fix Version/s: (was: v2.6.0) v2.5.1 > User login error message is inaccurate > -- > > Key: KYLIN-3565 > URL: https://issues.apache.org/jira/browse/KYLIN-3565 > Project: Kylin > Issue Type: Bug > Components: REST Service, Web >Affects Versions: v2.4.1 > Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 >Reporter: Marc Wu >Assignee: Roger >Priority: Minor > Labels: usability > Fix For: v2.5.1 > > Attachments: 2018-09-17_16-56-12.png, 2018-09-17_16-56-38.png, > 2018-09-17_16-59-31.png, image-2018-09-17-20-22-20-294.png, > image-2018-09-17-20-25-54-896.png > > > Hi Kylin team, > > We found one issue when log in Kylin. The error message will misunderstood > user. > > I couldn't log in Kylin even I input correct username & password (enable > LDAP). > So I checked the log on server, it showed me that there exist HBase > connection issues. > Root cause is that the HBase server which Kylin used as metadata server is > down, but the login message showed me that I should check my username or > password. It's really confusing. > Then I read some source codes about login module, and found out Kylin shares > the same error message for different cases. > > We suggested two options: > # redirect to global error page when HBase connection fail after login, > shows error message(e.g. System Error, please contact system administrator). > # enhance the error code for login logic, make the error message more > specific. > > There are login error message and the log. And I log in successfully after > recover HBase servers. > !image-2018-09-17-20-25-54-896.png!!image-2018-09-17-20-22-20-294.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KYLIN-3543) Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
[
https://issues.apache.org/jira/browse/KYLIN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI resolved KYLIN-3543.
-
Resolution: Fixed
> Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
> -
>
> Key: KYLIN-3543
> URL: https://issues.apache.org/jira/browse/KYLIN-3543
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v2.5.0
>Reporter: Ted Yu
>Assignee: Yichen Zhou
>Priority: Minor
> Fix For: v2.5.1
>
>
> {code}
> out = fs.create(new Path(hbaseConfPath));
> job.getConfiguration().writeXml(out);
> {code}
> The job instance should be closed upon return from the method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KYLIN-3543) Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
[
https://issues.apache.org/jira/browse/KYLIN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI reassigned KYLIN-3543:
---
Assignee: Yichen Zhou
Affects Version/s: v2.5.0
Fix Version/s: v2.5.1
> Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
> -
>
> Key: KYLIN-3543
> URL: https://issues.apache.org/jira/browse/KYLIN-3543
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v2.5.0
>Reporter: Ted Yu
>Assignee: Yichen Zhou
>Priority: Minor
> Fix For: v2.5.1
>
>
> {code}
> out = fs.create(new Path(hbaseConfPath));
> job.getConfiguration().writeXml(out);
> {code}
> The job instance should be closed upon return from the method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3439) configuration "kylin.web.timezone" is Inconsistent between kylin-defaults.properties and KylinConfigBase.java
[
https://issues.apache.org/jira/browse/KYLIN-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620128#comment-16620128
]
ASF GitHub Bot commented on KYLIN-3439:
---
shaofengshi closed pull request #164: KYLIN-3439, make default
kylin.web.timezone in KylinConfigBase the same with kylin-defaults.properties
URL: https://github.com/apache/kylin/pull/164
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/core-common/src/main/java/org/apache/kylin/common/KylinConfigBase.java
b/core-common/src/main/java/org/apache/kylin/common/KylinConfigBase.java
index 3ae6c2d48b..3544e94145 100644
--- a/core-common/src/main/java/org/apache/kylin/common/KylinConfigBase.java
+++ b/core-common/src/main/java/org/apache/kylin/common/KylinConfigBase.java
@@ -27,6 +27,7 @@
import java.util.Map.Entry;
import java.util.Properties;
import java.util.SortedSet;
+import java.util.TimeZone;
import java.util.regex.Matcher;
import java.util.regex.Pattern;
@@ -1536,7 +1537,11 @@ public String getLDAPAdminRole() {
//
public String getTimeZone() {
-return getOptional("kylin.web.timezone", "PST");
+String timezone = getOptional("kylin.web.timezone");
+if (StringUtils.isBlank(timezone)) {
+timezone = TimeZone.getDefault().getID();
+}
+return timezone;
}
public boolean isWebCrossDomainEnabled() {
diff --git a/core-common/src/main/resources/kylin-defaults.properties
b/core-common/src/main/resources/kylin-defaults.properties
index b391b5e202..9387112981 100644
--- a/core-common/src/main/resources/kylin-defaults.properties
+++ b/core-common/src/main/resources/kylin-defaults.properties
@@ -41,7 +41,7 @@ kylin.server.mode=all
kylin.server.cluster-servers=localhost:7070
# Display timezone on UI,format like[GMT+N or GMT-N]
-kylin.web.timezone=GMT+8
+kylin.web.timezone=
# Timeout value for the queries submitted through the Web UI, in milliseconds
kylin.web.query-timeout=30
diff --git
a/server/src/test/java/org/apache/kylin/rest/service/AdminServiceTest.java
b/server/src/test/java/org/apache/kylin/rest/service/AdminServiceTest.java
index 99d47e25d9..4b7b13390d 100644
--- a/server/src/test/java/org/apache/kylin/rest/service/AdminServiceTest.java
+++ b/server/src/test/java/org/apache/kylin/rest/service/AdminServiceTest.java
@@ -47,6 +47,7 @@ public void testGetPublicConfig() throws IOException {
String path =
Thread.currentThread().getContextClassLoader().getResource("kylin.properties").getPath();
KylinConfig config = KylinConfig.createInstanceFromUri(path);
+String timeZone = config.getTimeZone();
try (SetAndUnsetThreadLocalConfig autoUnset =
KylinConfig.setAndUnsetThreadLocalConfig(config)) {
String expected =
"kylin.web.link-streaming-guide=http://kylin.apache.org/\n; +
@@ -55,7 +56,7 @@ public void testGetPublicConfig() throws IOException {
"kylin.query.cache-enabled=true\n" +
"kylin.web.link-diagnostic=\n" +
"kylin.web.help.length=4\n" +
-"kylin.web.timezone=GMT+8\n" +
+"kylin.web.timezone=\n" +
"kylin.server.external-acl-provider=\n" +
"kylin.tool.auto-migrate-cube.enabled=\n" +
"kylin.storage.default=2\n" +
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> configuration "kylin.web.timezone" is Inconsistent between
> kylin-defaults.properties and KylinConfigBase.java
> --
>
> Key: KYLIN-3439
> URL: https://issues.apache.org/jira/browse/KYLIN-3439
> Project: Kylin
> Issue Type: Bug
>Reporter: jiatao.tao
>Assignee: jiatao.tao
>Priority: Minor
> Fix For: v2.6.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3439) configuration "kylin.web.timezone" is Inconsistent between kylin-defaults.properties and KylinConfigBase.java
[ https://issues.apache.org/jira/browse/KYLIN-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620129#comment-16620129 ] ASF subversion and git services commented on KYLIN-3439: Commit dd9909ca02bf0375b588849a5fd87aad3a201fcb in kylin's branch refs/heads/master from tttMelody [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=dd9909c ] KYLIN-3439, make default kylin.web.timezone in KylinConfigBase the same with kylin-defaults.properties > configuration "kylin.web.timezone" is Inconsistent between > kylin-defaults.properties and KylinConfigBase.java > -- > > Key: KYLIN-3439 > URL: https://issues.apache.org/jira/browse/KYLIN-3439 > Project: Kylin > Issue Type: Bug >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Minor > Fix For: v2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3565) User login error message is inaccurate
[ https://issues.apache.org/jira/browse/KYLIN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620106#comment-16620106 ] Marc Wu commented on KYLIN-3565: Thanks a lot! That would be helpful. > User login error message is inaccurate > -- > > Key: KYLIN-3565 > URL: https://issues.apache.org/jira/browse/KYLIN-3565 > Project: Kylin > Issue Type: Bug > Components: REST Service, Web >Affects Versions: v2.4.1 > Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 >Reporter: Marc Wu >Assignee: XiaoXiang Yu >Priority: Minor > Labels: usability > Fix For: v2.6.0 > > Attachments: 2018-09-17_16-56-12.png, 2018-09-17_16-56-38.png, > 2018-09-17_16-59-31.png, image-2018-09-17-20-22-20-294.png, > image-2018-09-17-20-25-54-896.png > > > Hi Kylin team, > > We found one issue when log in Kylin. The error message will misunderstood > user. > > I couldn't log in Kylin even I input correct username & password (enable > LDAP). > So I checked the log on server, it showed me that there exist HBase > connection issues. > Root cause is that the HBase server which Kylin used as metadata server is > down, but the login message showed me that I should check my username or > password. It's really confusing. > Then I read some source codes about login module, and found out Kylin shares > the same error message for different cases. > > We suggested two options: > # redirect to global error page when HBase connection fail after login, > shows error message(e.g. System Error, please contact system administrator). > # enhance the error code for login logic, make the error message more > specific. > > There are login error message and the log. And I log in successfully after > recover HBase servers. > !image-2018-09-17-20-25-54-896.png!!image-2018-09-17-20-22-20-294.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3565) User login error message is inaccurate
[ https://issues.apache.org/jira/browse/KYLIN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620091#comment-16620091 ] XiaoXiang Yu commented on KYLIN-3565: - When a RuntimeExecption was thrown, the status code of response is 500(server error). But when authentication failed, the status code is 401(unauthorized). So the front end will show different msg according to status code. > User login error message is inaccurate > -- > > Key: KYLIN-3565 > URL: https://issues.apache.org/jira/browse/KYLIN-3565 > Project: Kylin > Issue Type: Bug > Components: REST Service, Web >Affects Versions: v2.4.1 > Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 >Reporter: Marc Wu >Assignee: XiaoXiang Yu >Priority: Minor > Labels: usability > Fix For: v2.6.0 > > Attachments: 2018-09-17_16-56-12.png, 2018-09-17_16-56-38.png, > 2018-09-17_16-59-31.png, image-2018-09-17-20-22-20-294.png, > image-2018-09-17-20-25-54-896.png > > > Hi Kylin team, > > We found one issue when log in Kylin. The error message will misunderstood > user. > > I couldn't log in Kylin even I input correct username & password (enable > LDAP). > So I checked the log on server, it showed me that there exist HBase > connection issues. > Root cause is that the HBase server which Kylin used as metadata server is > down, but the login message showed me that I should check my username or > password. It's really confusing. > Then I read some source codes about login module, and found out Kylin shares > the same error message for different cases. > > We suggested two options: > # redirect to global error page when HBase connection fail after login, > shows error message(e.g. System Error, please contact system administrator). > # enhance the error code for login logic, make the error message more > specific. > > There are login error message and the log. And I log in successfully after > recover HBase servers. > !image-2018-09-17-20-25-54-896.png!!image-2018-09-17-20-22-20-294.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3565) User login error message is inaccurate
[
https://issues.apache.org/jira/browse/KYLIN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620043#comment-16620043
]
ASF GitHub Bot commented on KYLIN-3565:
---
luguosheng1314 closed pull request #238: KYLIN-3565 User login error message is
inaccurate
URL: https://github.com/apache/kylin/pull/238
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/webapp/app/js/controllers/auth.js
b/webapp/app/js/controllers/auth.js
index 6e5fa30d56..949093ee4e 100644
--- a/webapp/app/js/controllers/auth.js
+++ b/webapp/app/js/controllers/auth.js
@@ -36,7 +36,9 @@ KylinApp.controller('LoginCtrl', function ($scope,
$rootScope, $location, $base6
$location.path(UserService.getHomePage());
}, function (error) {
$scope.loading = false;
- $scope.error = "Unable to login, please check your username/password.";
+ $scope.error = error.status < 500
+? "Unable to login, please check your username/password."
+: "System error, please contact your administrator.";
});
};
});
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> User login error message is inaccurate
> --
>
> Key: KYLIN-3565
> URL: https://issues.apache.org/jira/browse/KYLIN-3565
> Project: Kylin
> Issue Type: Bug
> Components: REST Service, Web
>Affects Versions: v2.4.1
> Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456
>Reporter: Marc Wu
>Assignee: XiaoXiang Yu
>Priority: Minor
> Labels: usability
> Fix For: v2.6.0
>
> Attachments: 2018-09-17_16-56-12.png, 2018-09-17_16-56-38.png,
> 2018-09-17_16-59-31.png, image-2018-09-17-20-22-20-294.png,
> image-2018-09-17-20-25-54-896.png
>
>
> Hi Kylin team,
>
> We found one issue when log in Kylin. The error message will misunderstood
> user.
>
> I couldn't log in Kylin even I input correct username & password (enable
> LDAP).
> So I checked the log on server, it showed me that there exist HBase
> connection issues.
> Root cause is that the HBase server which Kylin used as metadata server is
> down, but the login message showed me that I should check my username or
> password. It's really confusing.
> Then I read some source codes about login module, and found out Kylin shares
> the same error message for different cases.
>
> We suggested two options:
> # redirect to global error page when HBase connection fail after login,
> shows error message(e.g. System Error, please contact system administrator).
> # enhance the error code for login logic, make the error message more
> specific.
>
> There are login error message and the log. And I log in successfully after
> recover HBase servers.
> !image-2018-09-17-20-25-54-896.png!!image-2018-09-17-20-22-20-294.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3565) User login error message is inaccurate
[ https://issues.apache.org/jira/browse/KYLIN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620044#comment-16620044 ] ASF subversion and git services commented on KYLIN-3565: Commit aee4b57ece21ad1bd5f33efd23feb79542235d91 in kylin's branch refs/heads/master from Emiya0306 [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=aee4b57 ] KYLIN-3565 User login error message is inaccurate > User login error message is inaccurate > -- > > Key: KYLIN-3565 > URL: https://issues.apache.org/jira/browse/KYLIN-3565 > Project: Kylin > Issue Type: Bug > Components: REST Service, Web >Affects Versions: v2.4.1 > Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 >Reporter: Marc Wu >Assignee: XiaoXiang Yu >Priority: Minor > Labels: usability > Fix For: v2.6.0 > > Attachments: 2018-09-17_16-56-12.png, 2018-09-17_16-56-38.png, > 2018-09-17_16-59-31.png, image-2018-09-17-20-22-20-294.png, > image-2018-09-17-20-25-54-896.png > > > Hi Kylin team, > > We found one issue when log in Kylin. The error message will misunderstood > user. > > I couldn't log in Kylin even I input correct username & password (enable > LDAP). > So I checked the log on server, it showed me that there exist HBase > connection issues. > Root cause is that the HBase server which Kylin used as metadata server is > down, but the login message showed me that I should check my username or > password. It's really confusing. > Then I read some source codes about login module, and found out Kylin shares > the same error message for different cases. > > We suggested two options: > # redirect to global error page when HBase connection fail after login, > shows error message(e.g. System Error, please contact system administrator). > # enhance the error code for login logic, make the error message more > specific. > > There are login error message and the log. And I log in successfully after > recover HBase servers. > !image-2018-09-17-20-25-54-896.png!!image-2018-09-17-20-22-20-294.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3569) Server with query mode still can submit/build job
[ https://issues.apache.org/jira/browse/KYLIN-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620023#comment-16620023 ] Zongwei Li commented on KYLIN-3569: --- For ' job server is responsible to schedule jobs', what's case for the schedule jobs? Can you help to give detail information about it, we want to know which function only can Job server take. It will help us to design the deployment architecture. Thanks > Server with query mode still can submit/build job > - > > Key: KYLIN-3569 > URL: https://issues.apache.org/jira/browse/KYLIN-3569 > Project: Kylin > Issue Type: Bug > Components: Job Engine, REST Service, Security >Affects Versions: v2.4.1 > Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 >Reporter: Zongwei Li >Priority: Major > Labels: build, documentation, security > Attachments: kylinCode.png > > > From the Docs at Kylin site, > [http://kylin.apache.org/docs24/install/kylin_cluster.html] > * *query* : run query engine only; Kylin query engine accepts and answers > your SQL queries > It seems that if server set with 'kylin.server.mode=query', it should not can > support submit/build job. But as we tested, server with query mode still can > submit/build job from UI or RESTFul API. > We analyzed the source code, found that there didn't exist any protect logic > to check whether server is at 'job' or 'build' mode in service layer for > submit/build job. Already attach the source code in this issue. > This issue really confused us, because we considered query server cannot > build job in Kylin Docs and many Kylin books. And query server will exposed > to 3rd BI tool to query the data, if we forget to configure the suitable ACL > for Cubes, then the 3rd BI tool can trigger build job in any time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3565) User login error message is inaccurate
[ https://issues.apache.org/jira/browse/KYLIN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620015#comment-16620015 ] ASF GitHub Bot commented on KYLIN-3565: --- asfgit commented on issue #238: KYLIN-3565 User login error message is inaccurate URL: https://github.com/apache/kylin/pull/238#issuecomment-422632052 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > User login error message is inaccurate > -- > > Key: KYLIN-3565 > URL: https://issues.apache.org/jira/browse/KYLIN-3565 > Project: Kylin > Issue Type: Bug > Components: REST Service, Web >Affects Versions: v2.4.1 > Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 >Reporter: Marc Wu >Assignee: XiaoXiang Yu >Priority: Minor > Labels: usability > Fix For: v2.6.0 > > Attachments: 2018-09-17_16-56-12.png, 2018-09-17_16-56-38.png, > 2018-09-17_16-59-31.png, image-2018-09-17-20-22-20-294.png, > image-2018-09-17-20-25-54-896.png > > > Hi Kylin team, > > We found one issue when log in Kylin. The error message will misunderstood > user. > > I couldn't log in Kylin even I input correct username & password (enable > LDAP). > So I checked the log on server, it showed me that there exist HBase > connection issues. > Root cause is that the HBase server which Kylin used as metadata server is > down, but the login message showed me that I should check my username or > password. It's really confusing. > Then I read some source codes about login module, and found out Kylin shares > the same error message for different cases. > > We suggested two options: > # redirect to global error page when HBase connection fail after login, > shows error message(e.g. System Error, please contact system administrator). > # enhance the error code for login logic, make the error message more > specific. > > There are login error message and the log. And I log in successfully after > recover HBase servers. > !image-2018-09-17-20-25-54-896.png!!image-2018-09-17-20-22-20-294.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3565) User login error message is inaccurate
[ https://issues.apache.org/jira/browse/KYLIN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620016#comment-16620016 ] ASF GitHub Bot commented on KYLIN-3565: --- asfgit commented on issue #238: KYLIN-3565 User login error message is inaccurate URL: https://github.com/apache/kylin/pull/238#issuecomment-422632054 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > User login error message is inaccurate > -- > > Key: KYLIN-3565 > URL: https://issues.apache.org/jira/browse/KYLIN-3565 > Project: Kylin > Issue Type: Bug > Components: REST Service, Web >Affects Versions: v2.4.1 > Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 >Reporter: Marc Wu >Assignee: XiaoXiang Yu >Priority: Minor > Labels: usability > Fix For: v2.6.0 > > Attachments: 2018-09-17_16-56-12.png, 2018-09-17_16-56-38.png, > 2018-09-17_16-59-31.png, image-2018-09-17-20-22-20-294.png, > image-2018-09-17-20-25-54-896.png > > > Hi Kylin team, > > We found one issue when log in Kylin. The error message will misunderstood > user. > > I couldn't log in Kylin even I input correct username & password (enable > LDAP). > So I checked the log on server, it showed me that there exist HBase > connection issues. > Root cause is that the HBase server which Kylin used as metadata server is > down, but the login message showed me that I should check my username or > password. It's really confusing. > Then I read some source codes about login module, and found out Kylin shares > the same error message for different cases. > > We suggested two options: > # redirect to global error page when HBase connection fail after login, > shows error message(e.g. System Error, please contact system administrator). > # enhance the error code for login logic, make the error message more > specific. > > There are login error message and the log. And I log in successfully after > recover HBase servers. > !image-2018-09-17-20-25-54-896.png!!image-2018-09-17-20-22-20-294.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3565) User login error message is inaccurate
[ https://issues.apache.org/jira/browse/KYLIN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620014#comment-16620014 ] ASF GitHub Bot commented on KYLIN-3565: --- Emiya0306 opened a new pull request #238: KYLIN-3565 User login error message is inaccurate URL: https://github.com/apache/kylin/pull/238 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > User login error message is inaccurate > -- > > Key: KYLIN-3565 > URL: https://issues.apache.org/jira/browse/KYLIN-3565 > Project: Kylin > Issue Type: Bug > Components: REST Service, Web >Affects Versions: v2.4.1 > Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 >Reporter: Marc Wu >Assignee: XiaoXiang Yu >Priority: Minor > Labels: usability > Fix For: v2.6.0 > > Attachments: 2018-09-17_16-56-12.png, 2018-09-17_16-56-38.png, > 2018-09-17_16-59-31.png, image-2018-09-17-20-22-20-294.png, > image-2018-09-17-20-25-54-896.png > > > Hi Kylin team, > > We found one issue when log in Kylin. The error message will misunderstood > user. > > I couldn't log in Kylin even I input correct username & password (enable > LDAP). > So I checked the log on server, it showed me that there exist HBase > connection issues. > Root cause is that the HBase server which Kylin used as metadata server is > down, but the login message showed me that I should check my username or > password. It's really confusing. > Then I read some source codes about login module, and found out Kylin shares > the same error message for different cases. > > We suggested two options: > # redirect to global error page when HBase connection fail after login, > shows error message(e.g. System Error, please contact system administrator). > # enhance the error code for login logic, make the error message more > specific. > > There are login error message and the log. And I log in successfully after > recover HBase servers. > !image-2018-09-17-20-25-54-896.png!!image-2018-09-17-20-22-20-294.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3562) TS conflict when kylin update metadata in HBase
[
https://issues.apache.org/jira/browse/KYLIN-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620010#comment-16620010
]
Yichen Zhou commented on KYLIN-3562:
Hi [~chitin], KYLIN-3531 was merged to master to fix this bug. If you use kylin
2.4, you can run this command and start Kylin again.
{quote}$KYLIN_HOME/bin/metastore.sh remove /user
{quote}
I hope this will help you!
> TS conflict when kylin update metadata in HBase
> ---
>
> Key: KYLIN-3562
> URL: https://issues.apache.org/jira/browse/KYLIN-3562
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v2.4.0
>Reporter: Lingang Deng
>Priority: Major
> Attachments: image-2018-09-17-16-40-56-212.png
>
>
> Error log was as follows,
> {code:java}
> org.apache.kylin.common.persistence.WriteConflictException: Overwriting
> conflict /user/admin, expect old TS 1536928877043, but it is 1536928907207
> at
> org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
> at
> org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:318)
> at
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:303)
> at
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:282)
> at
> org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192){code}
>
> what disturbs me the most was that the error was happened several hours,
> then my all build job and query job failed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3569) Server with query mode still can submit/build job
[ https://issues.apache.org/jira/browse/KYLIN-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619993#comment-16619993 ] Ma Gang commented on KYLIN-3569: I think that is by design, query server can accept any restful request(including submit job request), and job server is responsible to schedule jobs. In a typical Kylin cluster setup, Kylin servers that behind LB(nginx, F5, etc) should have query server permission, so that it can accept any restful request, and the servers that are configured only as job server should not be configured in LB. For the permission issue, you should configure the ACL properly, to ensure that the BI tools use the user that only have read permission for your project. > Server with query mode still can submit/build job > - > > Key: KYLIN-3569 > URL: https://issues.apache.org/jira/browse/KYLIN-3569 > Project: Kylin > Issue Type: Bug > Components: Job Engine, REST Service, Security >Affects Versions: v2.4.1 > Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 >Reporter: Zongwei Li >Priority: Major > Labels: build, documentation, security > Attachments: kylinCode.png > > > From the Docs at Kylin site, > [http://kylin.apache.org/docs24/install/kylin_cluster.html] > * *query* : run query engine only; Kylin query engine accepts and answers > your SQL queries > It seems that if server set with 'kylin.server.mode=query', it should not can > support submit/build job. But as we tested, server with query mode still can > submit/build job from UI or RESTFul API. > We analyzed the source code, found that there didn't exist any protect logic > to check whether server is at 'job' or 'build' mode in service layer for > submit/build job. Already attach the source code in this issue. > This issue really confused us, because we considered query server cannot > build job in Kylin Docs and many Kylin books. And query server will exposed > to 3rd BI tool to query the data, if we forget to configure the suitable ACL > for Cubes, then the 3rd BI tool can trigger build job in any time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KYLIN-1454) Add how to use python to generate authorization data for rest api
[ https://issues.apache.org/jira/browse/KYLIN-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI resolved KYLIN-1454. - Resolution: Fixed Fix Version/s: v2.5.0 Patch merged, thank you yongjie! > Add how to use python to generate authorization data for rest api > - > > Key: KYLIN-1454 > URL: https://issues.apache.org/jira/browse/KYLIN-1454 > Project: Kylin > Issue Type: Improvement > Components: Documentation >Reporter: yunjiong zhao >Assignee: yunjiong zhao >Priority: Major > Fix For: v2.5.0 > > Attachments: KYLIN-1454.patch > > > Currently in document, we only have how to use js to generate authorization > data. I believe use python is more convenient for most of people. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (KYLIN-1876) Star Schema also supports more than one fact table
[ https://issues.apache.org/jira/browse/KYLIN-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI closed KYLIN-1876. --- Resolution: Won't Fix > Star Schema also supports more than one fact table > -- > > Key: KYLIN-1876 > URL: https://issues.apache.org/jira/browse/KYLIN-1876 > Project: Kylin > Issue Type: Bug >Reporter: Rahul Choubey >Priority: Major > > As per the document of Apache Kylin, it supports Star Schema but in the Kylin > we have the option to select only one Fact Table. Is there is any planning to > support more than one Fact Table.? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (KYLIN-1454) Add how to use python to generate authorization data for rest api
[ https://issues.apache.org/jira/browse/KYLIN-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI closed KYLIN-1454. --- > Add how to use python to generate authorization data for rest api > - > > Key: KYLIN-1454 > URL: https://issues.apache.org/jira/browse/KYLIN-1454 > Project: Kylin > Issue Type: Improvement > Components: Documentation >Reporter: yunjiong zhao >Assignee: yunjiong zhao >Priority: Major > Fix For: v2.5.0 > > Attachments: KYLIN-1454.patch > > > Currently in document, we only have how to use js to generate authorization > data. I believe use python is more convenient for most of people. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-1454) Add how to use python to generate authorization data for rest api
[ https://issues.apache.org/jira/browse/KYLIN-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619969#comment-16619969 ] ASF subversion and git services commented on KYLIN-1454: Commit e67017f2a73465c3637c806f7dfa3a098ce5e71c in kylin's branch refs/heads/document from [~johnzhao] [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=e67017f ] KYLIN-1454 Add how to use python to generate authorization data for rest api Signed-off-by: shaofengshi > Add how to use python to generate authorization data for rest api > - > > Key: KYLIN-1454 > URL: https://issues.apache.org/jira/browse/KYLIN-1454 > Project: Kylin > Issue Type: Improvement > Components: Documentation >Reporter: yunjiong zhao >Assignee: yunjiong zhao >Priority: Major > Attachments: KYLIN-1454.patch > > > Currently in document, we only have how to use js to generate authorization > data. I believe use python is more convenient for most of people. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KYLIN-1295) Add new document to describe key concepts like model/cube/segment etc
[ https://issues.apache.org/jira/browse/KYLIN-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI reassigned KYLIN-1295: --- Assignee: Shaofeng SHI (was: liyang) > Add new document to describe key concepts like model/cube/segment etc > - > > Key: KYLIN-1295 > URL: https://issues.apache.org/jira/browse/KYLIN-1295 > Project: Kylin > Issue Type: Improvement > Components: Documentation >Reporter: liyang >Assignee: Shaofeng SHI >Priority: Major > Fix For: v2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3232) Need document for ops tools
[ https://issues.apache.org/jira/browse/KYLIN-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-3232: Fix Version/s: v2.6.0 Issue Type: Task (was: Improvement) > Need document for ops tools > --- > > Key: KYLIN-3232 > URL: https://issues.apache.org/jira/browse/KYLIN-3232 > Project: Kylin > Issue Type: Task > Components: Documentation >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI >Priority: Major > Fix For: v2.6.0 > > > Kylin has many good ops tool, like CubeMigrationCLI, CubeMetaIngester, etc; > They can greatly improve administrators productivity. But now there is no > document about them (you need check the code to know what they're doing) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-2615) Need better documents that explains design choices
[ https://issues.apache.org/jira/browse/KYLIN-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-2615: Fix Version/s: v2.6.0 Issue Type: Task (was: Wish) > Need better documents that explains design choices > -- > > Key: KYLIN-2615 > URL: https://issues.apache.org/jira/browse/KYLIN-2615 > Project: Kylin > Issue Type: Task > Components: Documentation >Reporter: nirav patel >Assignee: Shaofeng SHI >Priority: Major > Fix For: v2.6.0 > > > I see there are documents that explains how Kylin ingest hive tables and > build cubes/cuboids using MR and/or spark but there is hardly anything about > how it defines Metadata for cubes/segments, what are Segments, how it builds > indexes (Dictionaries, Inverted index if any) and how that helps querying > against cubes stored on hbase. > Other thing is how Kylin manages read-write isolation (read while write). Is > it snapshot based or something that user needs to take care of? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-1295) Add new document to describe key concepts like model/cube/segment etc
[ https://issues.apache.org/jira/browse/KYLIN-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1295: Fix Version/s: v2.6.0 Component/s: Documentation > Add new document to describe key concepts like model/cube/segment etc > - > > Key: KYLIN-1295 > URL: https://issues.apache.org/jira/browse/KYLIN-1295 > Project: Kylin > Issue Type: Improvement > Components: Documentation >Reporter: liyang >Assignee: Shaofeng SHI >Priority: Major > Fix For: v2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KYLIN-2615) Need better documents that explains design choices
[ https://issues.apache.org/jira/browse/KYLIN-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI reassigned KYLIN-2615: --- Assignee: Shaofeng SHI > Need better documents that explains design choices > -- > > Key: KYLIN-2615 > URL: https://issues.apache.org/jira/browse/KYLIN-2615 > Project: Kylin > Issue Type: Wish > Components: Documentation >Reporter: nirav patel >Assignee: Shaofeng SHI >Priority: Major > > I see there are documents that explains how Kylin ingest hive tables and > build cubes/cuboids using MR and/or spark but there is hardly anything about > how it defines Metadata for cubes/segments, what are Segments, how it builds > indexes (Dictionaries, Inverted index if any) and how that helps querying > against cubes stored on hbase. > Other thing is how Kylin manages read-write isolation (read while write). Is > it snapshot based or something that user needs to take care of? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (KYLIN-2057) Tidy up the website document landing page and left nav
[ https://issues.apache.org/jira/browse/KYLIN-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI closed KYLIN-2057. --- Resolution: Fixed > Tidy up the website document landing page and left nav > -- > > Key: KYLIN-2057 > URL: https://issues.apache.org/jira/browse/KYLIN-2057 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Priority: Major > > Right now the landing page of Kylin document is quite messy. > http://kylin.apache.org/docs15/index.html > The left-nav and landing page content is not in consistent and reasonable > order. Need a clean up. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3543) Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
[
https://issues.apache.org/jira/browse/KYLIN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619965#comment-16619965
]
ASF subversion and git services commented on KYLIN-3543:
Commit 6dcd79566e3a8a65650dfde3a3962bf51d52c4b6 in kylin's branch
refs/heads/master from [~yichen.zhou]
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=6dcd795 ]
KYLIN-3543 Export HBase configuration only for Spark engine
> Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
> -
>
> Key: KYLIN-3543
> URL: https://issues.apache.org/jira/browse/KYLIN-3543
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
>
> {code}
> out = fs.create(new Path(hbaseConfPath));
> job.getConfiguration().writeXml(out);
> {code}
> The job instance should be closed upon return from the method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3543) Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
[
https://issues.apache.org/jira/browse/KYLIN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619964#comment-16619964
]
ASF GitHub Bot commented on KYLIN-3543:
---
shaofengshi closed pull request #237: KYLIN-3543 Export HBase configuration
only for Spark engine
URL: https://github.com/apache/kylin/pull/237
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/storage-hbase/src/main/java/org/apache/kylin/storage/hbase/steps/CreateHTableJob.java
b/storage-hbase/src/main/java/org/apache/kylin/storage/hbase/steps/CreateHTableJob.java
index 93c12960de..7205802388 100644
---
a/storage-hbase/src/main/java/org/apache/kylin/storage/hbase/steps/CreateHTableJob.java
+++
b/storage-hbase/src/main/java/org/apache/kylin/storage/hbase/steps/CreateHTableJob.java
@@ -53,6 +53,7 @@
import org.apache.kylin.engine.mr.common.CubeStatsReader;
import org.apache.kylin.engine.mr.common.CuboidShardUtil;
import org.apache.kylin.job.exception.ExecuteException;
+import org.apache.kylin.metadata.model.IEngineAware;
import org.apache.kylin.storage.hbase.HBaseConnection;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
@@ -119,7 +120,11 @@ public int run(String[] args) throws Exception {
partitionFilePath.getParent());
CubeHTableUtil.createHTable(cubeSegment, splitKeys);
-exportHBaseConfiguration(cubeSegment.getStorageLocationIdentifier());
+
+// export configuration in advance to avoid connecting to hbase from
spark
+if (cubeDesc.getEngineType()== IEngineAware.ID_SPARK){
+
exportHBaseConfiguration(cubeSegment.getStorageLocationIdentifier());
+}
return 0;
}
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
> -
>
> Key: KYLIN-3543
> URL: https://issues.apache.org/jira/browse/KYLIN-3543
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
>
> {code}
> out = fs.create(new Path(hbaseConfPath));
> job.getConfiguration().writeXml(out);
> {code}
> The job instance should be closed upon return from the method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3531) Login failed with case-insensitive username
[
https://issues.apache.org/jira/browse/KYLIN-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619963#comment-16619963
]
ASF subversion and git services commented on KYLIN-3531:
Commit 5413975a94ea41ba17cd5e02359038d7a7affb45 in kylin's branch
refs/heads/master from [~yichen.zhou]
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=5413975 ]
KYLIN-3531 Save uppercase of usernames to metadata
> Login failed with case-insensitive username
> ---
>
> Key: KYLIN-3531
> URL: https://issues.apache.org/jira/browse/KYLIN-3531
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
>Affects Versions: v2.4.0
>Reporter: Yichen Zhou
>Assignee: Yichen Zhou
>Priority: Major
> Fix For: v2.5.1
>
>
> Username is case-insensitive in login authentication but case-sensitive in
> hbase metadata.
> {quote}org.apache.kylin.common.persistence.WriteConflictException:
> Overwriting conflict /user/Admin, expect old TS 1536031295060, but it is 0
>
> org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
>
> org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:323)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:308)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:287)
>
> org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192)
>
> org.apache.kylin.rest.security.KylinUserManager.update(KylinUserManager.java:122)
>
> org.apache.kylin.rest.service.KylinUserService.updateUser(KylinUserService.java:85)
>
> org.apache.kylin.rest.security.KylinAuthenticationProvider.authenticate(KylinAuthenticationProvider.java:117)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:174)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:199)
>
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:180)
>
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3531) Login failed with case-insensitive username
[
https://issues.apache.org/jira/browse/KYLIN-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619962#comment-16619962
]
ASF GitHub Bot commented on KYLIN-3531:
---
shaofengshi closed pull request #235: KYLIN-3531 Save uppercase of usernames to
metadata
URL: https://github.com/apache/kylin/pull/235
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/server-base/src/main/java/org/apache/kylin/rest/security/KylinUserManager.java
b/server-base/src/main/java/org/apache/kylin/rest/security/KylinUserManager.java
index c4b457de53..acbc0084c2 100644
---
a/server-base/src/main/java/org/apache/kylin/rest/security/KylinUserManager.java
+++
b/server-base/src/main/java/org/apache/kylin/rest/security/KylinUserManager.java
@@ -25,6 +25,7 @@
import java.util.Collections;
import java.util.Comparator;
import java.util.List;
+import java.util.Locale;
import org.apache.kylin.common.KylinConfig;
import org.apache.kylin.common.persistence.ResourceStore;
@@ -119,6 +120,7 @@ public void update(ManagedUser user) {
if (exist != null) {
user.setLastModified(exist.getLastModified());
}
+user.setUsername(user.getUsername().toUpperCase(Locale.ROOT));
crud.save(user);
} catch (IOException e) {
throw new RuntimeException("Can not update user.", e);
@@ -127,7 +129,7 @@ public void update(ManagedUser user) {
public void delete(String username) {
try (AutoReadWriteLock.AutoLock l = lock.lockForWrite()) {
-crud.delete(username);
+crud.delete(username.toUpperCase(Locale.ROOT));
} catch (IOException e) {
throw new RuntimeException("Can not delete user.", e);
}
diff --git
a/server-base/src/main/java/org/apache/kylin/rest/service/KylinUserService.java
b/server-base/src/main/java/org/apache/kylin/rest/service/KylinUserService.java
index 8571aec9e7..eea8cd7096 100644
---
a/server-base/src/main/java/org/apache/kylin/rest/service/KylinUserService.java
+++
b/server-base/src/main/java/org/apache/kylin/rest/service/KylinUserService.java
@@ -90,7 +90,7 @@ public void updateUser(UserDetails user) {
@Override
public void deleteUser(String userName) {
-if (userName.equals(SUPER_ADMIN)) {
+if (userName.equalsIgnoreCase(SUPER_ADMIN)) {
throw new InternalErrorException("User " + userName + " is not
allowed to be deleted.");
}
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Login failed with case-insensitive username
> ---
>
> Key: KYLIN-3531
> URL: https://issues.apache.org/jira/browse/KYLIN-3531
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
>Affects Versions: v2.4.0
>Reporter: Yichen Zhou
>Assignee: Yichen Zhou
>Priority: Major
> Fix For: v2.5.1
>
>
> Username is case-insensitive in login authentication but case-sensitive in
> hbase metadata.
> {quote}org.apache.kylin.common.persistence.WriteConflictException:
> Overwriting conflict /user/Admin, expect old TS 1536031295060, but it is 0
>
> org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
>
> org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:323)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:308)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:287)
>
> org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192)
>
> org.apache.kylin.rest.security.KylinUserManager.update(KylinUserManager.java:122)
>
> org.apache.kylin.rest.service.KylinUserService.updateUser(KylinUserService.java:85)
>
> org.apache.kylin.rest.security.KylinAuthenticationProvider.authenticate(KylinAuthenticationProvider.java:117)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:174)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:199)
>
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:180)
>
>
[jira] [Updated] (KYLIN-3569) Server with query mode still can submit/build job
[ https://issues.apache.org/jira/browse/KYLIN-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zongwei Li updated KYLIN-3569: -- Description: >From the Docs at Kylin site, >[http://kylin.apache.org/docs24/install/kylin_cluster.html] * *query* : run query engine only; Kylin query engine accepts and answers your SQL queries It seems that if server set with 'kylin.server.mode=query', it should not can support submit/build job. But as we tested, server with query mode still can submit/build job from UI or RESTFul API. We analyzed the source code, found that there didn't exist any protect logic to check whether server is at 'job' or 'build' mode in service layer for submit/build job. Already attach the source code in this issue. This issue really confused us, because we considered query server cannot build job in Kylin Docs and many Kylin books. And query server will exposed to 3rd BI tool to query the data, if we forget to configure the suitable ACL for Cubes, then the 3rd BI tool can trigger build job in any time. was: >From the Docs at Kylin site, >[http://kylin.apache.org/docs24/install/kylin_cluster.html] * *query* : run query engine only; Kylin query engine accepts and answers your SQL queries It seems that if server set with 'kylin.server.mode=query', it should not can support submit/build job. But as we tested, server with query mode still can submit/build job from UI or RESTFul API. We analyzed the source code, found that there didn't exist any protect logic to check whether server is at 'job' or 'build' mode in service layer for submit/build job. Will attach the source code is this issue. This issue really confused us, because we considered query server cannot build job in Kylin Docs and many Kylin books. And query server will exposed to 3rd BI tool to query the data, if we forget to configure the suitable ACL for Cubes, then the 3rd BI tool can trigger build job in any time. > Server with query mode still can submit/build job > - > > Key: KYLIN-3569 > URL: https://issues.apache.org/jira/browse/KYLIN-3569 > Project: Kylin > Issue Type: Bug > Components: Job Engine, REST Service, Security >Affects Versions: v2.4.1 > Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 >Reporter: Zongwei Li >Priority: Major > Labels: build, documentation, security > Attachments: kylinCode.png > > > From the Docs at Kylin site, > [http://kylin.apache.org/docs24/install/kylin_cluster.html] > * *query* : run query engine only; Kylin query engine accepts and answers > your SQL queries > It seems that if server set with 'kylin.server.mode=query', it should not can > support submit/build job. But as we tested, server with query mode still can > submit/build job from UI or RESTFul API. > We analyzed the source code, found that there didn't exist any protect logic > to check whether server is at 'job' or 'build' mode in service layer for > submit/build job. Already attach the source code in this issue. > This issue really confused us, because we considered query server cannot > build job in Kylin Docs and many Kylin books. And query server will exposed > to 3rd BI tool to query the data, if we forget to configure the suitable ACL > for Cubes, then the 3rd BI tool can trigger build job in any time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3569) Server with query mode still can submit/build job
[ https://issues.apache.org/jira/browse/KYLIN-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zongwei Li updated KYLIN-3569: -- Attachment: kylinCode.png > Server with query mode still can submit/build job > - > > Key: KYLIN-3569 > URL: https://issues.apache.org/jira/browse/KYLIN-3569 > Project: Kylin > Issue Type: Bug > Components: Job Engine, REST Service, Security >Affects Versions: v2.4.1 > Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 >Reporter: Zongwei Li >Priority: Major > Labels: build, documentation, security > Attachments: kylinCode.png > > > From the Docs at Kylin site, > [http://kylin.apache.org/docs24/install/kylin_cluster.html] > * *query* : run query engine only; Kylin query engine accepts and answers > your SQL queries > It seems that if server set with 'kylin.server.mode=query', it should not can > support submit/build job. But as we tested, server with query mode still can > submit/build job from UI or RESTFul API. > We analyzed the source code, found that there didn't exist any protect logic > to check whether server is at 'job' or 'build' mode in service layer for > submit/build job. Will attach the source code is this issue. > This issue really confused us, because we considered query server cannot > build job in Kylin Docs and many Kylin books. And query server will exposed > to 3rd BI tool to query the data, if we forget to configure the suitable ACL > for Cubes, then the 3rd BI tool can trigger build job in any time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3569) Server with query mode still can submit/build job
Zongwei Li created KYLIN-3569: - Summary: Server with query mode still can submit/build job Key: KYLIN-3569 URL: https://issues.apache.org/jira/browse/KYLIN-3569 Project: Kylin Issue Type: Bug Components: Job Engine, REST Service, Security Affects Versions: v2.4.1 Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 Reporter: Zongwei Li >From the Docs at Kylin site, >[http://kylin.apache.org/docs24/install/kylin_cluster.html] * *query* : run query engine only; Kylin query engine accepts and answers your SQL queries It seems that if server set with 'kylin.server.mode=query', it should not can support submit/build job. But as we tested, server with query mode still can submit/build job from UI or RESTFul API. We analyzed the source code, found that there didn't exist any protect logic to check whether server is at 'job' or 'build' mode in service layer for submit/build job. Will attach the source code is this issue. This issue really confused us, because we considered query server cannot build job in Kylin Docs and many Kylin books. And query server will exposed to 3rd BI tool to query the data, if we forget to configure the suitable ACL for Cubes, then the 3rd BI tool can trigger build job in any time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (KYLIN-3568) User login error message is inaccurate
[ https://issues.apache.org/jira/browse/KYLIN-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zongwei Li closed KYLIN-3568. - Resolution: Duplicate Fix Version/s: (was: v2.6.0) Sorry for duplicate bug. Will update it > User login error message is inaccurate > -- > > Key: KYLIN-3568 > URL: https://issues.apache.org/jira/browse/KYLIN-3568 > Project: Kylin > Issue Type: Bug > Components: REST Service, Web >Affects Versions: v2.4.1 > Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 >Reporter: Zongwei Li >Assignee: XiaoXiang Yu >Priority: Minor > Labels: usability > > Hi Kylin team, > > We found one issue when log in Kylin. The error message will misunderstood > user. > > I couldn't log in Kylin even I input correct username & password (enable > LDAP). > So I checked the log on server, it showed me that there exist HBase > connection issues. > Root cause is that the HBase server which Kylin used as metadata server is > down, but the login message showed me that I should check my username or > password. It's really confusing. > Then I read some source codes about login module, and found out Kylin shares > the same error message for different cases. > > We suggested two options: > # redirect to global error page when HBase connection fail after login, > shows error message(e.g. System Error, please contact system administrator). > # enhance the error code for login logic, make the error message more > specific. > > There are login error message and the log. And I log in successfully after > recover HBase servers. > !image-2018-09-17-20-25-54-896.png!!image-2018-09-17-20-22-20-294.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3568) User login error message is inaccurate
Zongwei Li created KYLIN-3568: - Summary: User login error message is inaccurate Key: KYLIN-3568 URL: https://issues.apache.org/jira/browse/KYLIN-3568 Project: Kylin Issue Type: Bug Components: REST Service, Web Affects Versions: v2.4.1 Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 Reporter: Zongwei Li Assignee: XiaoXiang Yu Fix For: v2.6.0 Hi Kylin team, We found one issue when log in Kylin. The error message will misunderstood user. I couldn't log in Kylin even I input correct username & password (enable LDAP). So I checked the log on server, it showed me that there exist HBase connection issues. Root cause is that the HBase server which Kylin used as metadata server is down, but the login message showed me that I should check my username or password. It's really confusing. Then I read some source codes about login module, and found out Kylin shares the same error message for different cases. We suggested two options: # redirect to global error page when HBase connection fail after login, shows error message(e.g. System Error, please contact system administrator). # enhance the error code for login logic, make the error message more specific. There are login error message and the log. And I log in successfully after recover HBase servers. !image-2018-09-17-20-25-54-896.png!!image-2018-09-17-20-22-20-294.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3488) Support MySQL as Kylin metadata storage
[ https://issues.apache.org/jira/browse/KYLIN-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619918#comment-16619918 ] Shaofeng SHI commented on KYLIN-3488: - The document is in https://kylin.apache.org/docs/install/advance_settings.html > Support MySQL as Kylin metadata storage > --- > > Key: KYLIN-3488 > URL: https://issues.apache.org/jira/browse/KYLIN-3488 > Project: Kylin > Issue Type: New Feature > Components: Metadata >Reporter: Shaofeng SHI >Priority: Major > Fix For: v2.5.0 > > > Kylin uses HBase as the metastore; But in some cases user expects the > metadata not in HBase. > Sonny Heer from mailing list mentioned: > "I'm fairly certain anyone using Kylin with AWS EMR will benefit from this. > Having multiple hbase clusters across AZs is a huge benefit. BTW only thing > blocking at the moment is write operations happening from kylin query nodes." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-2650) Update to Apache Calcite Avatica 1.12.0
[ https://issues.apache.org/jira/browse/KYLIN-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KYLIN-2650: -- Summary: Update to Apache Calcite Avatica 1.12.0 (was: Update to Apache Calcite Avatica 1.10.0) > Update to Apache Calcite Avatica 1.12.0 > --- > > Key: KYLIN-2650 > URL: https://issues.apache.org/jira/browse/KYLIN-2650 > Project: Kylin > Issue Type: Improvement >Reporter: Ted Yu >Priority: Minor > > Apache Calcite Avatica 1.10.0 has just been released. > This issue upgrades Avatica dependency. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3095) Use ArrayDeque instead of LinkedList for queue implementation
[
https://issues.apache.org/jira/browse/KYLIN-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated KYLIN-3095:
--
Description:
Use ArrayDeque instead of LinkedList for queue implementation where thread
safety is not needed.
>From https://docs.oracle.com/javase/7/docs/api/java/util/ArrayDeque.html
{quote}
Resizable-array implementation of the Deque interface. Array deques have no
capacity restrictions; they grow as necessary to support usage. They are not
thread-safe; in the absence of external synchronization, they do not support
concurrent access by multiple threads. Null elements are prohibited. This class
is likely to be faster than Stack when used as a stack, and *faster than
LinkedList when used as a queue.*
{quote}
was:
Use ArrayDeque instead of LinkedList for queue implementation where thread
safety is not needed.
>From https://docs.oracle.com/javase/7/docs/api/java/util/ArrayDeque.html
{quote}
Resizable-array implementation of the Deque interface. Array deques have no
capacity restrictions; they grow as necessary to support usage. They are not
thread-safe; in the absence of external synchronization, they do not support
concurrent access by multiple threads. Null elements are prohibited. This class
is likely to be faster than Stack when used as a stack, and *faster than
LinkedList when used as a queue.*
{quote}
> Use ArrayDeque instead of LinkedList for queue implementation
> -
>
> Key: KYLIN-3095
> URL: https://issues.apache.org/jira/browse/KYLIN-3095
> Project: Kylin
> Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Kaige Liu
>Priority: Minor
> Labels: parallel
> Fix For: Backlog
>
>
> Use ArrayDeque instead of LinkedList for queue implementation where thread
> safety is not needed.
> From https://docs.oracle.com/javase/7/docs/api/java/util/ArrayDeque.html
> {quote}
> Resizable-array implementation of the Deque interface. Array deques have no
> capacity restrictions; they grow as necessary to support usage. They are not
> thread-safe; in the absence of external synchronization, they do not support
> concurrent access by multiple threads. Null elements are prohibited. This
> class is likely to be faster than Stack when used as a stack, and *faster
> than LinkedList when used as a queue.*
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KYLIN-3272) Upgrade Spark dependency to 2.3.1
[ https://issues.apache.org/jira/browse/KYLIN-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KYLIN-3272: -- Description: Currently Spark 2.1.2 is used. Spark 2.3.1 was released. We should upgrade the dependency to 2.3.1 was: Currently Spark 2.1.2 is used. Spark 2.3.0 was just released. We should upgrade the dependency to 2.3.0 > Upgrade Spark dependency to 2.3.1 > - > > Key: KYLIN-3272 > URL: https://issues.apache.org/jira/browse/KYLIN-3272 > Project: Kylin > Issue Type: Improvement > Components: Spark Engine >Reporter: Ted Yu >Priority: Minor > > Currently Spark 2.1.2 is used. > Spark 2.3.1 was released. > We should upgrade the dependency to 2.3.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (KYLIN-3334) Prepare for Java 10
[
https://issues.apache.org/jira/browse/KYLIN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473200#comment-16473200
]
Ted Yu edited comment on KYLIN-3334 at 9/18/18 4:17 PM:
Compiling against jdk 11 gives similar error.
was (Author: yuzhih...@gmail.com):
Compiling against jdk 11 gives similar error .
> Prepare for Java 10
> ---
>
> Key: KYLIN-3334
> URL: https://issues.apache.org/jira/browse/KYLIN-3334
> Project: Kylin
> Issue Type: Task
>Reporter: Ted Yu
>Priority: Major
>
> When compiling with Java 10 , MapReduce Engine module fails with
> {code}
> [ERROR] Failed to execute goal on project kylin-engine-mr: Could not resolve
> dependencies for project org.apache.kylin:kylin-engine-mr:jar:2.4.0-SNAPSHOT:
> Could not find artifact jdk.tools:jdk.tools:jar:1.7 at specified path
> /a/jdk-10/../lib/tools.jar -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3543) Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
[
https://issues.apache.org/jira/browse/KYLIN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618932#comment-16618932
]
ASF GitHub Bot commented on KYLIN-3543:
---
asfgit commented on issue #237: KYLIN-3543 Export HBase configuration only for
Spark engine
URL: https://github.com/apache/kylin/pull/237#issuecomment-422351011
Can one of the admins verify this patch?
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
> -
>
> Key: KYLIN-3543
> URL: https://issues.apache.org/jira/browse/KYLIN-3543
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
>
> {code}
> out = fs.create(new Path(hbaseConfPath));
> job.getConfiguration().writeXml(out);
> {code}
> The job instance should be closed upon return from the method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3543) Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
[
https://issues.apache.org/jira/browse/KYLIN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618933#comment-16618933
]
ASF GitHub Bot commented on KYLIN-3543:
---
asfgit commented on issue #237: KYLIN-3543 Export HBase configuration only for
Spark engine
URL: https://github.com/apache/kylin/pull/237#issuecomment-422351010
Can one of the admins verify this patch?
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
> -
>
> Key: KYLIN-3543
> URL: https://issues.apache.org/jira/browse/KYLIN-3543
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
>
> {code}
> out = fs.create(new Path(hbaseConfPath));
> job.getConfiguration().writeXml(out);
> {code}
> The job instance should be closed upon return from the method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3543) Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
[
https://issues.apache.org/jira/browse/KYLIN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618931#comment-16618931
]
ASF GitHub Bot commented on KYLIN-3543:
---
ZhouYC627 opened a new pull request #237: KYLIN-3543 Export HBase configuration
only for Spark engine
URL: https://github.com/apache/kylin/pull/237
https://issues.apache.org/jira/browse/KYLIN-3543
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Unclosed Job instance in CreateHTableJob#exportHBaseConfiguration
> -
>
> Key: KYLIN-3543
> URL: https://issues.apache.org/jira/browse/KYLIN-3543
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
>
> {code}
> out = fs.create(new Path(hbaseConfPath));
> job.getConfiguration().writeXml(out);
> {code}
> The job instance should be closed upon return from the method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KYLIN-3567) remove scala dependency
Chao Long created KYLIN-3567: Summary: remove scala dependency Key: KYLIN-3567 URL: https://issues.apache.org/jira/browse/KYLIN-3567 Project: Kylin Issue Type: Bug Reporter: Chao Long Assignee: Chao Long The scope of scala dependency in "engine-spark" module should be "provided". org.scala-lang scala-library org.scala-lang scala-compiler org.scala-lang scala-reflect -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3528) No details page for hybrid
[ https://issues.apache.org/jira/browse/KYLIN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618850#comment-16618850 ] ASF subversion and git services commented on KYLIN-3528: Commit 51fa4d059a7c90f448af58fa261396647e1e1bb6 in kylin's branch refs/heads/master from Emiya0306 [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=51fa4d0 ] KYLIN-3528 Add details page for hybrid > No details page for hybrid > -- > > Key: KYLIN-3528 > URL: https://issues.apache.org/jira/browse/KYLIN-3528 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Na Zhai >Assignee: Roger >Priority: Minor > Fix For: v2.6.0 > > > When I click hybrid name, there is no detail page for that hybrid. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3528) No details page for hybrid
[
https://issues.apache.org/jira/browse/KYLIN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618849#comment-16618849
]
ASF GitHub Bot commented on KYLIN-3528:
---
luguosheng1314 closed pull request #236: KYLIN-3528 Add details page for hybrid
URL: https://github.com/apache/kylin/pull/236
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/webapp/app/js/controllers/hybridInstance.js
b/webapp/app/js/controllers/hybridInstance.js
index cdf1e40ca7..236eefc14c 100644
--- a/webapp/app/js/controllers/hybridInstance.js
+++ b/webapp/app/js/controllers/hybridInstance.js
@@ -19,7 +19,7 @@
'use strict';
KylinApp.controller('HybridInstanceCtrl', function (
- $scope, $q, $location,
+ $scope, $q, $location, $modal,
ProjectModel, hybridInstanceManager, SweetAlert, HybridInstanceService,
loadingRequest, MessageBox
) {
$scope.projectModel = ProjectModel;
@@ -52,6 +52,30 @@ KylinApp.controller('HybridInstanceCtrl', function (
$scope.list();
});
+ var HybridDetailModalCtrl = function ($scope, $modalInstance, hybrid) {
+$scope.hybrid = hybrid;
+$scope.hybridModels = [{
+ name: hybrid.model
+}];
+
+$scope.cancel = function () {
+ $modalInstance.dismiss('cancel');
+};
+ };
+
+ $scope.openHybridDetailModal = function (hybrid) {
+$modal.open({
+ templateUrl: 'hybridDetail.html',
+ controller: HybridDetailModalCtrl,
+ resolve: {
+hybrid: function () {
+ return hybrid;
+}
+ },
+ windowClass: 'hybrid-detail'
+});
+ };
+
$scope.editHybridInstance = function(hybridInstance){
// check for empty project of header, break the operation.
if (ProjectModel.selectedProject === null) {
diff --git a/webapp/app/less/app.less b/webapp/app/less/app.less
index cb59fab4ff..7a0ca18b8c 100644
--- a/webapp/app/less/app.less
+++ b/webapp/app/less/app.less
@@ -963,7 +963,8 @@ div[ng-controller="ModelConditionsSettingsCtrl"] {
min-height: 100vh;
}
-div[ng-controller="HybridInstanceSchema"] {
+div[ng-controller="HybridInstanceSchema"],
+div.hybrid-detail {
.form-title {
margin-bottom: 43px;
}
@@ -1056,4 +1057,10 @@ div[ng-controller="HybridInstanceSchema"] {
.text-info {
font-size: 18px;
color: #263238;
-}
\ No newline at end of file
+}
+
+div.hybrid-detail {
+ .modal-dialog {
+width: 600px;
+ }
+}
diff --git a/webapp/app/partials/cubes/hybrid_detail.html
b/webapp/app/partials/cubes/hybrid_detail.html
new file mode 100644
index 00..72e77a7fc6
--- /dev/null
+++ b/webapp/app/partials/cubes/hybrid_detail.html
@@ -0,0 +1,71 @@
+
+
+
+
+Hybrid Detail
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/webapp/app/partials/models/models_tree.html
b/webapp/app/partials/models/models_tree.html
index d2064a29de..c0645251fd 100644
--- a/webapp/app/partials/models/models_tree.html
+++
[jira] [Commented] (KYLIN-3528) No details page for hybrid
[ https://issues.apache.org/jira/browse/KYLIN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618843#comment-16618843 ] ASF GitHub Bot commented on KYLIN-3528: --- asfgit commented on issue #236: KYLIN-3528 Add details page for hybrid URL: https://github.com/apache/kylin/pull/236#issuecomment-422336742 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > No details page for hybrid > -- > > Key: KYLIN-3528 > URL: https://issues.apache.org/jira/browse/KYLIN-3528 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Na Zhai >Assignee: Roger >Priority: Minor > Fix For: v2.6.0 > > > When I click hybrid name, there is no detail page for that hybrid. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3528) No details page for hybrid
[ https://issues.apache.org/jira/browse/KYLIN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618842#comment-16618842 ] ASF GitHub Bot commented on KYLIN-3528: --- asfgit commented on issue #236: KYLIN-3528 Add details page for hybrid URL: https://github.com/apache/kylin/pull/236#issuecomment-422336743 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > No details page for hybrid > -- > > Key: KYLIN-3528 > URL: https://issues.apache.org/jira/browse/KYLIN-3528 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Na Zhai >Assignee: Roger >Priority: Minor > Fix For: v2.6.0 > > > When I click hybrid name, there is no detail page for that hybrid. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3528) No details page for hybrid
[ https://issues.apache.org/jira/browse/KYLIN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618841#comment-16618841 ] ASF GitHub Bot commented on KYLIN-3528: --- Emiya0306 opened a new pull request #236: KYLIN-3528 Add details page for hybrid URL: https://github.com/apache/kylin/pull/236 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > No details page for hybrid > -- > > Key: KYLIN-3528 > URL: https://issues.apache.org/jira/browse/KYLIN-3528 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Na Zhai >Assignee: Roger >Priority: Minor > Fix For: v2.6.0 > > > When I click hybrid name, there is no detail page for that hybrid. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3531) Login failed with case-insensitive username
[
https://issues.apache.org/jira/browse/KYLIN-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618821#comment-16618821
]
ASF GitHub Bot commented on KYLIN-3531:
---
ZhouYC627 commented on issue #235: KYLIN-3531 Save uppercase of usernames to
metadata
URL: https://github.com/apache/kylin/pull/235#issuecomment-422334120
If login failed, try this command before kylin starts:
> $KYLIN_HOME/bin/metastore.sh remove /user
Restart Kylin. Now the usernames in metadata are all uppercase and kylin
will ignore case in Web UI.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Login failed with case-insensitive username
> ---
>
> Key: KYLIN-3531
> URL: https://issues.apache.org/jira/browse/KYLIN-3531
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
>Affects Versions: v2.4.0
>Reporter: Yichen Zhou
>Assignee: Yichen Zhou
>Priority: Major
> Fix For: v2.5.1
>
>
> Username is case-insensitive in login authentication but case-sensitive in
> hbase metadata.
> {quote}org.apache.kylin.common.persistence.WriteConflictException:
> Overwriting conflict /user/Admin, expect old TS 1536031295060, but it is 0
>
> org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
>
> org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:323)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:308)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:287)
>
> org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192)
>
> org.apache.kylin.rest.security.KylinUserManager.update(KylinUserManager.java:122)
>
> org.apache.kylin.rest.service.KylinUserService.updateUser(KylinUserService.java:85)
>
> org.apache.kylin.rest.security.KylinAuthenticationProvider.authenticate(KylinAuthenticationProvider.java:117)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:174)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:199)
>
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:180)
>
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3531) Login failed with case-insensitive username
[
https://issues.apache.org/jira/browse/KYLIN-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618610#comment-16618610
]
ASF GitHub Bot commented on KYLIN-3531:
---
asfgit commented on issue #235: KYLIN-3531 Save uppercase of usernames to
metadata
URL: https://github.com/apache/kylin/pull/235#issuecomment-422288461
Can one of the admins verify this patch?
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Login failed with case-insensitive username
> ---
>
> Key: KYLIN-3531
> URL: https://issues.apache.org/jira/browse/KYLIN-3531
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
>Affects Versions: v2.4.0
>Reporter: Yichen Zhou
>Assignee: Yichen Zhou
>Priority: Major
> Fix For: v2.5.1
>
>
> Username is case-insensitive in login authentication but case-sensitive in
> hbase metadata.
> {quote}org.apache.kylin.common.persistence.WriteConflictException:
> Overwriting conflict /user/Admin, expect old TS 1536031295060, but it is 0
>
> org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
>
> org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:323)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:308)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:287)
>
> org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192)
>
> org.apache.kylin.rest.security.KylinUserManager.update(KylinUserManager.java:122)
>
> org.apache.kylin.rest.service.KylinUserService.updateUser(KylinUserService.java:85)
>
> org.apache.kylin.rest.security.KylinAuthenticationProvider.authenticate(KylinAuthenticationProvider.java:117)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:174)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:199)
>
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:180)
>
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3531) Login failed with case-insensitive username
[
https://issues.apache.org/jira/browse/KYLIN-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618609#comment-16618609
]
ASF GitHub Bot commented on KYLIN-3531:
---
asfgit commented on issue #235: KYLIN-3531 Save uppercase of usernames to
metadata
URL: https://github.com/apache/kylin/pull/235#issuecomment-422288460
Can one of the admins verify this patch?
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Login failed with case-insensitive username
> ---
>
> Key: KYLIN-3531
> URL: https://issues.apache.org/jira/browse/KYLIN-3531
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
>Affects Versions: v2.4.0
>Reporter: Yichen Zhou
>Assignee: Yichen Zhou
>Priority: Major
> Fix For: v2.5.1
>
>
> Username is case-insensitive in login authentication but case-sensitive in
> hbase metadata.
> {quote}org.apache.kylin.common.persistence.WriteConflictException:
> Overwriting conflict /user/Admin, expect old TS 1536031295060, but it is 0
>
> org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
>
> org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:323)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:308)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:287)
>
> org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192)
>
> org.apache.kylin.rest.security.KylinUserManager.update(KylinUserManager.java:122)
>
> org.apache.kylin.rest.service.KylinUserService.updateUser(KylinUserService.java:85)
>
> org.apache.kylin.rest.security.KylinAuthenticationProvider.authenticate(KylinAuthenticationProvider.java:117)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:174)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:199)
>
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:180)
>
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KYLIN-3256) Filter of dates do not work
[
https://issues.apache.org/jira/browse/KYLIN-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Cao reassigned KYLIN-3256:
Assignee: Lijun Cao
> Filter of dates do not work
> ---
>
> Key: KYLIN-3256
> URL: https://issues.apache.org/jira/browse/KYLIN-3256
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Affects Versions: v2.2.0
>Reporter: Jean-Luc BELLIER
>Assignee: Lijun Cao
>Priority: Major
> Fix For: v2.6.0
>
>
> Hello,
>
> I am wondering how to filter date columns with Kylin.
> I am working with the sample cube of the learn_kylin project. I have slightly
> modified the cube to add a few more columns, but that is all.
> In the advanced section, I put KYLIN_SALES.PART_DT in the 'Rowkeys' section,
> defined as 'date' type.
>
> I would like to add a filter like 'WHERE KYLIN_SALES.DT_PART = '2012-06-24'
> but the Kylin interface gives me a mistake : 'error while compiling generated
> Java code'
> This works fine with hive console.
> I also tried with TO_DATE('2012-06-24').
> Using "WHERE KYLIN_SALES.DT_PART BETWEEN '2012-06-24' AND '2012-06-25'", it
> works fine.
>
> Are there limitations or internal transformations on the 'date' type in
> Kylin ?
>
> Thank you for your help. Have a good day.
>
> Best regards;
> Jean-Luc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3531) Login failed with case-insensitive username
[
https://issues.apache.org/jira/browse/KYLIN-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618608#comment-16618608
]
ASF GitHub Bot commented on KYLIN-3531:
---
ZhouYC627 opened a new pull request #235: KYLIN-3531 Save uppercase of
usernames to metadata
URL: https://github.com/apache/kylin/pull/235
https://issues.apache.org/jira/browse/KYLIN-3531
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Login failed with case-insensitive username
> ---
>
> Key: KYLIN-3531
> URL: https://issues.apache.org/jira/browse/KYLIN-3531
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
>Affects Versions: v2.4.0
>Reporter: Yichen Zhou
>Assignee: Yichen Zhou
>Priority: Major
> Fix For: v2.5.1
>
>
> Username is case-insensitive in login authentication but case-sensitive in
> hbase metadata.
> {quote}org.apache.kylin.common.persistence.WriteConflictException:
> Overwriting conflict /user/Admin, expect old TS 1536031295060, but it is 0
>
> org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
>
> org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:323)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:308)
>
> org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:287)
>
> org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192)
>
> org.apache.kylin.rest.security.KylinUserManager.update(KylinUserManager.java:122)
>
> org.apache.kylin.rest.service.KylinUserService.updateUser(KylinUserService.java:85)
>
> org.apache.kylin.rest.security.KylinAuthenticationProvider.authenticate(KylinAuthenticationProvider.java:117)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:174)
>
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:199)
>
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:180)
>
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (KYLIN-3558) Kylin for CDH6.0.0
[ https://issues.apache.org/jira/browse/KYLIN-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI closed KYLIN-3558. --- > Kylin for CDH6.0.0 > -- > > Key: KYLIN-3558 > URL: https://issues.apache.org/jira/browse/KYLIN-3558 > Project: Kylin > Issue Type: Wish >Reporter: Lijun Cao >Assignee: Lijun Cao >Priority: Major > Fix For: v2.5.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3565) User login error message is inaccurate
[ https://issues.apache.org/jira/browse/KYLIN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618524#comment-16618524 ] Shaofeng SHI commented on KYLIN-3565: - Xiaoxiang, go ahead! > User login error message is inaccurate > -- > > Key: KYLIN-3565 > URL: https://issues.apache.org/jira/browse/KYLIN-3565 > Project: Kylin > Issue Type: Bug > Components: REST Service, Web >Affects Versions: v2.4.1 > Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456 >Reporter: Marc Wu >Assignee: XiaoXiang Yu >Priority: Minor > Labels: usability > Fix For: v2.6.0 > > Attachments: 2018-09-17_16-56-12.png, 2018-09-17_16-56-38.png, > 2018-09-17_16-59-31.png, image-2018-09-17-20-22-20-294.png, > image-2018-09-17-20-25-54-896.png > > > Hi Kylin team, > > We found one issue when log in Kylin. The error message will misunderstood > user. > > I couldn't log in Kylin even I input correct username & password (enable > LDAP). > So I checked the log on server, it showed me that there exist HBase > connection issues. > Root cause is that the HBase server which Kylin used as metadata server is > down, but the login message showed me that I should check my username or > password. It's really confusing. > Then I read some source codes about login module, and found out Kylin shares > the same error message for different cases. > > We suggested two options: > # redirect to global error page when HBase connection fail after login, > shows error message(e.g. System Error, please contact system administrator). > # enhance the error code for login logic, make the error message more > specific. > > There are login error message and the log. And I log in successfully after > recover HBase servers. > !image-2018-09-17-20-25-54-896.png!!image-2018-09-17-20-22-20-294.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
