[jira] [Commented] (KYLIN-2952) dynamic cube build for time(statTime and endTime)
[
https://issues.apache.org/jira/browse/KYLIN-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16212188#comment-16212188
]
Billy Liu commented on KYLIN-2952:
--
The epoch has no timezone info. All API use epoch only. What's your proposal or
question?
> dynamic cube build for time(statTime and endTime)
> -
>
> Key: KYLIN-2952
> URL: https://issues.apache.org/jira/browse/KYLIN-2952
> Project: Kylin
> Issue Type: Improvement
> Components: REST Service
>Affects Versions: v1.6.0
> Environment: linux
>Reporter: wenxue lin
>Assignee: Zhong,Jason
>Priority: Minor
>
> ex => curl -X PUT -u "ADMIN:KYLIN" -H
> "Content-Type:application/json;charset=utf-8" -d
> '{"startTime":150860160,"endTime":150868800,"buildType":"BUILD"}'
> http://host:port/kylin/api/cubes/bi_dispatch_waiting_service_cube/rebuild
> desc :
> rest api param is startTime:150860160(2017-10-22) and
> endTime:150868800(2017-10-23)， but the actual time of building the cube
> is 1 day ahead of schedule (actually 8 hours ahead of schedule)
> =》【2017-10-21~2017-10-22】，But using kylinUI build without question, the
> actual view kylin code, found that is because the kylin on the server side
> source code for configuration of GMT rather than use the timezone of fixed
> GMT + 8, and front-end UI will according to the configuration of the timezone
> is transformed to the time of the page to add GMT + 8 time, then the back-end
> to GMT + 8 time in into GMT time, so the kylinUI cube build time without
> error, and using restAPI build cube time not making timezone 8 hours is not
> accurate time difference problem。
> *for code:*
> kylinProperties.js
> this.getTimeZone = function () {
> if (!this.timezone) {
> this.timezone = this.getProperty("kylin.rest.timezone").trim();
> }
> return this.timezone;
> }
> org.apache.kylin.cube.CubeSegment
> public static String makeSegmentName(long startDate, long endDate, long
> startOffset, long endOffset) {
> if (startOffset != 0 || endOffset != 0) {
> if (startOffset == 0 && (endOffset == 0 || endOffset ==
> Long.MAX_VALUE)) {
> return "FULL_BUILD";
> }
> return startOffset + "_" + endOffset;
> }
> // using time
> SimpleDateFormat dateFormat = new SimpleDateFormat("MMddHHmmss");
> dateFormat.setTimeZone(TimeZone.getTimeZone("GMT"));
> return dateFormat.format(startDate) + "_" + dateFormat.format(endDate);
> }
> org.apache.kylin.common.util.DateFormat:
> public static FastDateFormat getDateFormat(String datePattern) {
> FastDateFormat r = formatMap.get(datePattern);
> if (r == null) {
> r = FastDateFormat.getInstance(datePattern,
> TimeZone.getTimeZone("GMT")); // NOTE: this must be GMT to calculate epoch
> date correctly
> formatMap.put(datePattern, r);
> }
> return r;
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-2943) 关于kylin设置queuename遇到的问题
[ https://issues.apache.org/jira/browse/KYLIN-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16212164#comment-16212164 ] wang20170707 commented on KYLIN-2943: - hadoophadoop从系统层面，修改了用户的默认queue，并且运行用户使用default队列下 BUILD CUBE第2步运行的mr任务已执行成功，当执行到第3步时失败，谁能帮忙看看什么原因导致的，错误详情如下： #3 Step Name: Extract Fact Table Distinct Columns User: bdcbas1234 Name: Kylin_Fact_Distinct_Columns_w_cub_source_Step Application Type: MAPREDUCE Application Tags: State: FAILED FinalStatus:FAILED Started:星期五 十月 20 13:07:41 +0800 2017 Elapsed:8sec Tracking URL: History Diagnostics: Application application_1507516583223_7366 failed 2 times due to AM Container for appattempt_1507516583223_7366_02 exited with exitCode: 1 due to: Exception from container-launch. Container id: container_1507516583223_7366_02_01 Exit code: 1 Stack trace: ExitCodeException exitCode=1: at org.apache.hadoop.util.Shell.runCommand(Shell.java:538) at org.apache.hadoop.util.Shell.run(Shell.java:455) at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:702) at org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor.launchContainer(LinuxContainerExecutor.java:290) at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:299) at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:81) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Shell output: main : command provided 1 main : user is bdcbas1234 main : requested yarn user is bdcbas1234 Container exited with a non-zero exit code 1 .Failing this attempt.. Failing the application. > 关于kylin设置queuename遇到的问题 > --- > > Key: KYLIN-2943 > URL: https://issues.apache.org/jira/browse/KYLIN-2943 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v2.1.0 > Environment: CDH5.7 >Reporter: wang20170707 >Assignee: Dong Li > > 在CDH5.7环境下新搭建kylin2.1环境 > 1.需要修改队列名称，具体操作如下 > 在kylin.properties文件配置队列参数如下： > kylin.source.kylin.client=beeline > kylin.engine.mr.config-override.mapreduce.job.queuename=cbasQueue > kylin.source.hive.config-override.mapreduce.job.queuename=cbasQueue > 在kylin_hive_conf.xml里面配 > mapred.job.queue.name > 在 > kylin_job_conf_inmem.xml > kylin_job_conf.xml文件里配 > mapreduce.job.queuename=cbasQueue > 2.修改好配置后重启kylin，在load hive table时，运行的mr任务报错，详情如下： > User: bdcbas1234 > Name: Kylin Hive Column Cardinality Job table=CBAS_DB.S_WEB_APP_PAGE > output=hdfs://zhcbdpII/bdcbasApp/kylin/bdcbasApp-kylin_metadata/cardinality/5ae93815-0f53-412e-bb53-07c194c873d7/CBAS_DB.S_WEB_APP_PAGE > Application Type: MAPREDUCE > Application Tags: > State:FAILED > FinalStatus: FAILED > Started: 星期二 十月 17 16:25:47 +0800 2017 > Elapsed: 8sec > Tracking URL: History > Diagnostics: > Application application_1507516583223_4851 failed 2 times due to AM Container > for appattempt_1507516583223_4851_02 exited with exitCode: 1 due to: > Exception from container-launch. > Container id: container_1507516583223_4851_02_01 > Exit code: 1 > Stack trace: ExitCodeException exitCode=1: > at org.apache.hadoop.util.Shell.runCommand(Shell.java:538) > at org.apache.hadoop.util.Shell.run(Shell.java:455) > at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:702) > at > org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor.launchContainer(LinuxContainerExecutor.java:290) > at > org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:299) > at > org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:81) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Shell output: main : command provided 1 > main : user is bdcbas1234 > main : requested yarn user is bdcbas1234 > Container exited with a non-zero exit code 1 > .Failing this attempt.. Failing the application. > 3.在BULID CUBE时，在第2步失败： > #1 Step Name: Create Intermediate Flat Hive Table > 执行成功，mr任务使用的queue为配置后的cbasQueue > #2 Step Name: Redistribute Flat Hive Table > 执行失败，mr任务select count(*) from > ...6d_9935_49f0c9600e38(Stage-1)使用的queue为配置前的default > 4.将kylin.properties文件里的参数 > kylin.source.kylin.client修改为cli > 执行load hive table错误与beeline相同 > 5.在BULID CUBE时,在第3步失败 > #1 Step Name: Create
[jira] [Updated] (KYLIN-2853) Upgrade Curator dependency
[ https://issues.apache.org/jira/browse/KYLIN-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KYLIN-2853: -- Description: Currently we depend on Curator 2.7.1 There have been some bug fixes in Curator. e.g. CURATOR-264 that address potential leader election bugs. We should upgrade to Curator 2.12.0 was: Currently we depend on Curator 2.7.1 There have been some bug fixes in Curator. e.g. CURATOR-264 that address potential leader election bugs. We should upgrade to Curator 2.12.0 > Upgrade Curator dependency > -- > > Key: KYLIN-2853 > URL: https://issues.apache.org/jira/browse/KYLIN-2853 > Project: Kylin > Issue Type: Task >Reporter: Ted Yu > > Currently we depend on Curator 2.7.1 > There have been some bug fixes in Curator. e.g. > CURATOR-264 > that address potential leader election bugs. > We should upgrade to Curator 2.12.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2952) dynamic cube build for time(statTime and endTime)
[
https://issues.apache.org/jira/browse/KYLIN-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wenxue lin updated KYLIN-2952:
--
Description:
ex => curl -X PUT -u "ADMIN:KYLIN" -H
"Content-Type:application/json;charset=utf-8" -d
'{"startTime":150860160,"endTime":150868800,"buildType":"BUILD"}'
http://host:port/kylin/api/cubes/bi_dispatch_waiting_service_cube/rebuild
desc :
rest api param is startTime:150860160(2017-10-22) and
endTime:150868800(2017-10-23)， but the actual time of building the cube is
1 day ahead of schedule (actually 8 hours ahead of schedule)
=》【2017-10-21~2017-10-22】，But using kylinUI build without question, the actual
view kylin code, found that is because the kylin on the server side source code
for configuration of GMT rather than use the timezone of fixed GMT + 8, and
front-end UI will according to the configuration of the timezone is transformed
to the time of the page to add GMT + 8 time, then the back-end to GMT + 8 time
in into GMT time, so the kylinUI cube build time without error, and using
restAPI build cube time not making timezone 8 hours is not accurate time
difference problem。
*for code:*
kylinProperties.js
this.getTimeZone = function () {
if (!this.timezone) {
this.timezone = this.getProperty("kylin.rest.timezone").trim();
}
return this.timezone;
}
org.apache.kylin.cube.CubeSegment
public static String makeSegmentName(long startDate, long endDate, long
startOffset, long endOffset) {
if (startOffset != 0 || endOffset != 0) {
if (startOffset == 0 && (endOffset == 0 || endOffset ==
Long.MAX_VALUE)) {
return "FULL_BUILD";
}
return startOffset + "_" + endOffset;
}
// using time
SimpleDateFormat dateFormat = new SimpleDateFormat("MMddHHmmss");
dateFormat.setTimeZone(TimeZone.getTimeZone("GMT"));
return dateFormat.format(startDate) + "_" + dateFormat.format(endDate);
}
org.apache.kylin.common.util.DateFormat:
public static FastDateFormat getDateFormat(String datePattern) {
FastDateFormat r = formatMap.get(datePattern);
if (r == null) {
r = FastDateFormat.getInstance(datePattern,
TimeZone.getTimeZone("GMT")); // NOTE: this must be GMT to calculate epoch date
correctly
formatMap.put(datePattern, r);
}
return r;
}
was:
ex => curl -X PUT -u "ADMIN:KYLIN" -H
"Content-Type:application/json;charset=utf-8" -d
'{"startTime":150860160,"endTime":150868800,"buildType":"BUILD"}'
http://host:port/kylin/api/cubes/bi_dispatch_waiting_service_cube/rebuild
desc :
rest api param is startTime:150860160(2017-10-22) and
endTime:150868800(2017-10-23)， but the actual time of building the cube is
1 day ahead of schedule (actually 8 hours ahead of schedule)
=》【2017-10-21~2017-10-22】，But using kylinUI build without question, the actual
view kylin source, found that is because the kylin on the server side source
code for configuration of GMT rather than use the timezone of fixed GMT + 8,
and front-end UI will according to the configuration of the timezone is
transformed to the time of the page to add GMT + 8 time, then the back-end to
GMT + 8 time in into GMT time, so the kylinUI cube build time without error,
and using restAPI build cube time not making timezone 8 hours is not accurate
time difference problem。
*for code:*
kylinProperties.js
this.getTimeZone = function () {
if (!this.timezone) {
this.timezone = this.getProperty("kylin.rest.timezone").trim();
}
return this.timezone;
}
org.apache.kylin.cube.CubeSegment
public static String makeSegmentName(long startDate, long endDate, long
startOffset, long endOffset) {
if (startOffset != 0 || endOffset != 0) {
if (startOffset == 0 && (endOffset == 0 || endOffset ==
Long.MAX_VALUE)) {
return "FULL_BUILD";
}
return startOffset + "_" + endOffset;
}
// using time
SimpleDateFormat dateFormat = new SimpleDateFormat("MMddHHmmss");
dateFormat.setTimeZone(TimeZone.getTimeZone("GMT"));
return dateFormat.format(startDate) + "_" + dateFormat.format(endDate);
}
org.apache.kylin.common.util.DateFormat:
public static FastDateFormat getDateFormat(String datePattern) {
FastDateFormat r = formatMap.get(datePattern);
if (r == null) {
r = FastDateFormat.getInstance(datePattern,
TimeZone.getTimeZone("GMT")); // NOTE: this must be GMT to calculate epoch date
correctly
formatMap.put(datePattern, r);
}
return r;
}
> dynamic cube build for time(statTime and endTime)
> -
>
> Key: KYLIN-2952
> URL: https://issues.apache.org/jira/browse/KYLIN-2952
> Project: Kylin
> Issue Type: Improvement
> Components: REST Service
>Affects Versions: v1.6.0
> Environment: linux
>Reporter:
[jira] [Created] (KYLIN-2952) dynamic cube build for time(statTime and endTime)
wenxue lin created KYLIN-2952:
-
Summary: dynamic cube build for time(statTime and endTime)
Key: KYLIN-2952
URL: https://issues.apache.org/jira/browse/KYLIN-2952
Project: Kylin
Issue Type: Improvement
Components: REST Service
Affects Versions: v1.6.0
Environment: linux
Reporter: wenxue lin
Assignee: Zhong,Jason
Priority: Minor
ex => curl -X PUT -u "ADMIN:KYLIN" -H
"Content-Type:application/json;charset=utf-8" -d
'{"startTime":150860160,"endTime":150868800,"buildType":"BUILD"}'
http://host:port/kylin/api/cubes/bi_dispatch_waiting_service_cube/rebuild
desc :
rest api param is startTime:150860160(2017-10-22) and
endTime:150868800(2017-10-23)， but the actual time of building the cube is
1 day ahead of schedule (actually 8 hours ahead of schedule)
=》【2017-10-21~2017-10-22】，But using kylinUI build without question, the actual
view kylin source, found that is because the kylin on the server side source
code for configuration of GMT rather than use the timezone of fixed GMT + 8,
and front-end UI will according to the configuration of the timezone is
transformed to the time of the page to add GMT + 8 time, then the back-end to
GMT + 8 time in into GMT time, so the kylinUI cube build time without error,
and using restAPI build cube time not making timezone 8 hours is not accurate
time difference problem。
*for code:*
kylinProperties.js
this.getTimeZone = function () {
if (!this.timezone) {
this.timezone = this.getProperty("kylin.rest.timezone").trim();
}
return this.timezone;
}
org.apache.kylin.cube.CubeSegment
public static String makeSegmentName(long startDate, long endDate, long
startOffset, long endOffset) {
if (startOffset != 0 || endOffset != 0) {
if (startOffset == 0 && (endOffset == 0 || endOffset ==
Long.MAX_VALUE)) {
return "FULL_BUILD";
}
return startOffset + "_" + endOffset;
}
// using time
SimpleDateFormat dateFormat = new SimpleDateFormat("MMddHHmmss");
dateFormat.setTimeZone(TimeZone.getTimeZone("GMT"));
return dateFormat.format(startDate) + "_" + dateFormat.format(endDate);
}
org.apache.kylin.common.util.DateFormat:
public static FastDateFormat getDateFormat(String datePattern) {
FastDateFormat r = formatMap.get(datePattern);
if (r == null) {
r = FastDateFormat.getInstance(datePattern,
TimeZone.getTimeZone("GMT")); // NOTE: this must be GMT to calculate epoch date
correctly
formatMap.put(datePattern, r);
}
return r;
}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KYLIN-2951) Fix couple of NullPointerException in Kylin code base
Wang Ken created KYLIN-2951: --- Summary: Fix couple of NullPointerException in Kylin code base Key: KYLIN-2951 URL: https://issues.apache.org/jira/browse/KYLIN-2951 Project: Kylin Issue Type: Bug Reporter: Wang Ken Priority: Minor I create this ticket as the umbrella to cover some NPE bugs in Kylin 2.1 & 2.2 code base. We see some NPE errors from our server log, some of them are tiny, it is trivial to create individual ticket to cover them one by one. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KYLIN-2951) Fix couple of NullPointerException in Kylin code base
[ https://issues.apache.org/jira/browse/KYLIN-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wang Ken reassigned KYLIN-2951: --- Assignee: Wang Ken > Fix couple of NullPointerException in Kylin code base > - > > Key: KYLIN-2951 > URL: https://issues.apache.org/jira/browse/KYLIN-2951 > Project: Kylin > Issue Type: Bug >Reporter: Wang Ken >Assignee: Wang Ken >Priority: Minor > > I create this ticket as the umbrella to cover some NPE bugs in Kylin 2.1 & > 2.2 code base. > We see some NPE errors from our server log, some of them are tiny, it is > trivial to create individual ticket to cover them one by one. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2950) Change build engine smoothly
[ https://issues.apache.org/jira/browse/KYLIN-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fengYu updated KYLIN-2950: -- Attachment: 0001-KYLIN-2950-Change-build-engine-smoothly.patch > Change build engine smoothly > > > Key: KYLIN-2950 > URL: https://issues.apache.org/jira/browse/KYLIN-2950 > Project: Kylin > Issue Type: Bug >Affects Versions: v2.0.0 >Reporter: fengYu >Assignee: fengYu > Attachments: 0001-KYLIN-2950-Change-build-engine-smoothly.patch > > > Currently, we can not change build engine without disable cube and purging > all existing segments. But it is expensive。 > After my test building cube with MR engine and Spark engine, there generate > the same result, and Merge job always use mr engine. Hence, I think take > engineType as a part of cube's Signature is improper。 > I change the code and modify cube json. it work will with MR and spark engine > Alternately。 > TO BE DONE：modify web UI. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2756) Let "LIMIT" be optional in "Inspect" page
[ https://issues.apache.org/jira/browse/KYLIN-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2756: - Fix Version/s: v2.3.0 > Let "LIMIT" be optional in "Inspect" page > - > > Key: KYLIN-2756 > URL: https://issues.apache.org/jira/browse/KYLIN-2756 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-2756-Let-LIMIT-be-optional-in-inspect-page.patch > > > Kylin's "Inspect" page will append a LIMIT clause for queries if the query > doesn't have "LIMIT"; > While this will make some query be invalid because "LIMIT" not always appear > in the last position. For example: > select * from KYLIN_SALES OFFSET 100 ROWS FETCH FIRST 10 ROWS ONLY > According to Calcite's SQL reference, LIMIT should be before OFFSET clause. > So, Kylin should give user the option of not append the "LIMIT". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2948) Count a column returns the same result as count(*) even if this column has NULL
[ https://issues.apache.org/jira/browse/KYLIN-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16212067#comment-16212067 ] DeXin commented on KYLIN-2948: -- Yes, KYLIN-2049 is the similar issue.If “count” measure would allow us to select a column and calculate without NULLs, that will solve the problem. > Count a column returns the same result as count(*) even if this column has > NULL > --- > > Key: KYLIN-2948 > URL: https://issues.apache.org/jira/browse/KYLIN-2948 > Project: Kylin > Issue Type: Bug >Affects Versions: v2.1.0 > Environment: CentOS 7 >Reporter: DeXin >Priority: Critical > > When we want to count a column(with same NULL value), there is different > result from kylin and hive SQL. Is there a way to exclude NULL value in count > measure calculation for a particular column? > Here is the example: > 1. Here is source data: > Date ID > 2017-10-10 dfe343ddfe3f5 > 2017-10-11 fer234d656dff > 2017-10-11 NULL > 2017-10-12 jui6jnc3ncce3 > 2. run SQL in Hive: > select Date, count(*), count(ID) from table group by Date; > 2017-10-10 1 1 > 2017-10-11 2 1 > 2017-10-12 1 1 > 3. run same SQL in Kylin: > select Date, count(*), count(ID) from table group by Date; > 2017-10-10 1 1 > 2017-10-11 2 2 > 2017-10-12 1 1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2950) Change build engine smoothly
fengYu created KYLIN-2950: - Summary: Change build engine smoothly Key: KYLIN-2950 URL: https://issues.apache.org/jira/browse/KYLIN-2950 Project: Kylin Issue Type: Bug Affects Versions: v2.0.0 Reporter: fengYu Assignee: fengYu Currently, we can not change build engine without disable cube and purging all existing segments. But it is expensive。 After my test building cube with MR engine and Spark engine, there generate the same result, and Merge job always use mr engine. Hence, I think take engineType as a part of cube's Signature is improper。 I change the code and modify cube json. it work will with MR and spark engine Alternately。 TO BE DONE：modify web UI. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2949) The kylin does not get right authorities when the LDAP authentication service was used in RedHat OS.
[ https://issues.apache.org/jira/browse/KYLIN-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-2949: Issue Type: Bug (was: New Feature) > The kylin does not get right authorities when the LDAP authentication service > was used in RedHat OS. > > > Key: KYLIN-2949 > URL: https://issues.apache.org/jira/browse/KYLIN-2949 > Project: Kylin > Issue Type: Bug > Components: General >Affects Versions: v2.1.0 >Reporter: peng.jianhua >Assignee: peng.jianhua > Fix For: v2.2.0 > > Attachments: > 0001-KYLIN-2949-The-kylin-does-not-get-right-authorities-.patch > > > Scene: > 1. LDAP server(s) deployed in RedHat OS; > 2. Enable LDAP authentication in kylin; > 3. Add kylin_admin user and admin group in kylin. The kylin_admin user > belongs to the admin group. And admin group is the "admin" role. > 3. Login kylin using kylin_admin user. > The result is that kylin_admin user lost the authority of "ROLE_ADMIN", with > only default authorities returned. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2949) The kylin does not get right authorities when the LDAP authentication service was used in RedHat OS.
[ https://issues.apache.org/jira/browse/KYLIN-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-2949: Issue Type: New Feature (was: Bug) > The kylin does not get right authorities when the LDAP authentication service > was used in RedHat OS. > > > Key: KYLIN-2949 > URL: https://issues.apache.org/jira/browse/KYLIN-2949 > Project: Kylin > Issue Type: New Feature > Components: General >Affects Versions: v2.1.0 >Reporter: peng.jianhua >Assignee: peng.jianhua > Fix For: v2.2.0 > > Attachments: > 0001-KYLIN-2949-The-kylin-does-not-get-right-authorities-.patch > > > Scene: > 1. LDAP server(s) deployed in RedHat OS; > 2. Enable LDAP authentication in kylin; > 3. Add kylin_admin user and admin group in kylin. The kylin_admin user > belongs to the admin group. And admin group is the "admin" role. > 3. Login kylin using kylin_admin user. > The result is that kylin_admin user lost the authority of "ROLE_ADMIN", with > only default authorities returned. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2948) Count a column returns the same result as count(*) even if this column has NULL
[ https://issues.apache.org/jira/browse/KYLIN-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16211558#comment-16211558 ] albertoramon commented on KYLIN-2948: - Coulu you check:[ KYLIN-2049 ]https://issues.apache.org/jira/browse/KYLIN-2049 > Count a column returns the same result as count(*) even if this column has > NULL > --- > > Key: KYLIN-2948 > URL: https://issues.apache.org/jira/browse/KYLIN-2948 > Project: Kylin > Issue Type: Bug >Affects Versions: v2.1.0 > Environment: CentOS 7 >Reporter: DeXin >Priority: Critical > > When we want to count a column(with same NULL value), there is different > result from kylin and hive SQL. Is there a way to exclude NULL value in count > measure calculation for a particular column? > Here is the example: > 1. Here is source data: > Date ID > 2017-10-10 dfe343ddfe3f5 > 2017-10-11 fer234d656dff > 2017-10-11 NULL > 2017-10-12 jui6jnc3ncce3 > 2. run SQL in Hive: > select Date, count(*), count(ID) from table group by Date; > 2017-10-10 1 1 > 2017-10-11 2 1 > 2017-10-12 1 1 > 3. run same SQL in Kylin: > select Date, count(*), count(ID) from table group by Date; > 2017-10-10 1 1 > 2017-10-11 2 2 > 2017-10-12 1 1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2756) Let "LIMIT" be optional in "Inspect" page
[ https://issues.apache.org/jira/browse/KYLIN-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16211196#comment-16211196 ] Dong Li commented on KYLIN-2756: [~bob123] Please set "Fix version" when you resolve this JIRA. If patch merged to master branch, set to v2.3.0 If patch merged to 2.2.x branch, set to v2.2.0 > Let "LIMIT" be optional in "Inspect" page > - > > Key: KYLIN-2756 > URL: https://issues.apache.org/jira/browse/KYLIN-2756 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Attachments: > 0001-KYLIN-2756-Let-LIMIT-be-optional-in-inspect-page.patch > > > Kylin's "Inspect" page will append a LIMIT clause for queries if the query > doesn't have "LIMIT"; > While this will make some query be invalid because "LIMIT" not always appear > in the last position. For example: > select * from KYLIN_SALES OFFSET 100 ROWS FETCH FIRST 10 ROWS ONLY > According to Calcite's SQL reference, LIMIT should be before OFFSET clause. > So, Kylin should give user the option of not append the "LIMIT". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2949) The kylin does not get right authorities when the LDAP authentication service was used in RedHat OS.
[ https://issues.apache.org/jira/browse/KYLIN-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Li resolved KYLIN-2949. Resolution: Fixed Fix Version/s: v2.2.0 thanks jianhua. merged to master and 2.2.x branches > The kylin does not get right authorities when the LDAP authentication service > was used in RedHat OS. > > > Key: KYLIN-2949 > URL: https://issues.apache.org/jira/browse/KYLIN-2949 > Project: Kylin > Issue Type: Bug > Components: General >Affects Versions: v2.1.0 >Reporter: peng.jianhua >Assignee: peng.jianhua > Fix For: v2.2.0 > > Attachments: > 0001-KYLIN-2949-The-kylin-does-not-get-right-authorities-.patch > > > Scene: > 1. LDAP server(s) deployed in RedHat OS; > 2. Enable LDAP authentication in kylin; > 3. Add kylin_admin user and admin group in kylin. The kylin_admin user > belongs to the admin group. And admin group is the "admin" role. > 3. Login kylin using kylin_admin user. > The result is that kylin_admin user lost the authority of "ROLE_ADMIN", with > only default authorities returned. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2949) The kylin does not get right authorities when the LDAP authentication service was used in RedHat OS.
[ https://issues.apache.org/jira/browse/KYLIN-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-2949: Attachment: 0001-KYLIN-2949-The-kylin-does-not-get-right-authorities-.patch > The kylin does not get right authorities when the LDAP authentication service > was used in RedHat OS. > > > Key: KYLIN-2949 > URL: https://issues.apache.org/jira/browse/KYLIN-2949 > Project: Kylin > Issue Type: Bug > Components: General >Affects Versions: v2.1.0 >Reporter: peng.jianhua >Assignee: peng.jianhua > Attachments: > 0001-KYLIN-2949-The-kylin-does-not-get-right-authorities-.patch > > > Scene: > 1. LDAP server(s) deployed in RedHat OS; > 2. Enable LDAP authentication in kylin; > 3. Add kylin_admin user and admin group in kylin. The kylin_admin user > belongs to the admin group. And admin group is the "admin" role. > 3. Login kylin using kylin_admin user. > The result is that kylin_admin user lost the authority of "ROLE_ADMIN", with > only default authorities returned. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2756) Let "LIMIT" be optional in "Inspect" page
[ https://issues.apache.org/jira/browse/KYLIN-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luguosheng resolved KYLIN-2756. --- Resolution: Fixed > Let "LIMIT" be optional in "Inspect" page > - > > Key: KYLIN-2756 > URL: https://issues.apache.org/jira/browse/KYLIN-2756 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Attachments: > 0001-KYLIN-2756-Let-LIMIT-be-optional-in-inspect-page.patch > > > Kylin's "Inspect" page will append a LIMIT clause for queries if the query > doesn't have "LIMIT"; > While this will make some query be invalid because "LIMIT" not always appear > in the last position. For example: > select * from KYLIN_SALES OFFSET 100 ROWS FETCH FIRST 10 ROWS ONLY > According to Calcite's SQL reference, LIMIT should be before OFFSET clause. > So, Kylin should give user the option of not append the "LIMIT". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2949) The kylin does not get right authorities when the LDAP authentication service was used in RedHat OS.
peng.jianhua created KYLIN-2949: --- Summary: The kylin does not get right authorities when the LDAP authentication service was used in RedHat OS. Key: KYLIN-2949 URL: https://issues.apache.org/jira/browse/KYLIN-2949 Project: Kylin Issue Type: Bug Components: General Affects Versions: v2.1.0 Reporter: peng.jianhua Assignee: peng.jianhua Scene: 1. LDAP server(s) deployed in RedHat OS; 2. Enable LDAP authentication in kylin; 3. Add kylin_admin user and admin group in kylin. The kylin_admin user belongs to the admin group. And admin group is the "admin" role. 3. Login kylin using kylin_admin user. The result is that kylin_admin user lost the authority of "ROLE_ADMIN", with only default authorities returned. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2948) Count a column returns the same result as count(*) even if this column has NULL
DeXin created KYLIN-2948: Summary: Count a column returns the same result as count(*) even if this column has NULL Key: KYLIN-2948 URL: https://issues.apache.org/jira/browse/KYLIN-2948 Project: Kylin Issue Type: Bug Affects Versions: v2.1.0 Environment: CentOS 7 Reporter: DeXin Priority: Critical When we want to count a column(with same NULL value), there is different result from kylin and hive SQL. Is there a way to exclude NULL value in count measure calculation for a particular column? Here is the example: 1. Here is source data: Date ID 2017-10-10 dfe343ddfe3f5 2017-10-11 fer234d656dff 2017-10-11 NULL 2017-10-12 jui6jnc3ncce3 2. run SQL in Hive: select Date, count(*), count(ID) from table group by Date; 2017-10-10 1 1 2017-10-11 2 1 2017-10-12 1 1 3. run same SQL in Kylin: select Date, count(*), count(ID) from table group by Date; 2017-10-10 1 1 2017-10-11 2 2 2017-10-12 1 1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2794) MultipleDictionaryValueEnumerator should output values in sorted order
[
https://issues.apache.org/jira/browse/KYLIN-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210817#comment-16210817
]
songxiangjun commented on KYLIN-2794:
-
Hi,
We have tried to compile version 2.2 Kylin, but the problem remains. How do
you solve this problem? Can you Can you elaborate on that?
> MultipleDictionaryValueEnumerator should output values in sorted order
> --
>
> Key: KYLIN-2794
> URL: https://issues.apache.org/jira/browse/KYLIN-2794
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
>Affects Versions: v2.0.0
> Environment: hadoop hadoop-2.6.0-cdh5.8.2 hive 2.1 hbase 0.98
>Reporter: 翟玉勇
>Assignee: Yifei Wu
>Priority: Critical
> Labels: scope
> Fix For: v2.2.0
>
>
> Dictionary exception during merge of segments.
> {code}
> 2017-08-18 14:17:48,828 ERROR [pool-11-thread-1]
> threadpool.DistributedScheduler:188 : ExecuteException
> job:8d031b5f-2d3f-445f-a62b-7bc560d919ea in server: **
> org.apache.kylin.job.exception.ExecuteException:
> org.apache.kylin.job.exception.ExecuteException:
> java.lang.IllegalStateException: Invalid input data. Unordered data cannot be
> split into multi trees
> at
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:134)
> at
> org.apache.kylin.job.impl.threadpool.DistributedScheduler$JobRunner.run(DistributedScheduler.java:185)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.kylin.job.exception.ExecuteException:
> java.lang.IllegalStateException: Invalid input data. Unordered data cannot be
> split into multi trees
> at
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:134)
> at
> org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:64)
> at
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:124)
> ... 4 more
> Caused by: java.lang.IllegalStateException: Invalid input data. Unordered
> data cannot be split into multi trees
> at
> org.apache.kylin.dict.TrieDictionaryForestBuilder.addValue(TrieDictionaryForestBuilder.java:92)
> at
> org.apache.kylin.dict.TrieDictionaryForestBuilder.addValue(TrieDictionaryForestBuilder.java:78)
> at
> org.apache.kylin.dict.DictionaryGenerator$StringTrieDictForestBuilder.addValue(DictionaryGenerator.java:212)
> at
> org.apache.kylin.dict.DictionaryGenerator.buildDictionary(DictionaryGenerator.java:79)
> at
> org.apache.kylin.dict.DictionaryGenerator.buildDictionary(DictionaryGenerator.java:64)
> at
> org.apache.kylin.dict.DictionaryGenerator.mergeDictionaries(DictionaryGenerator.java:104)
> at
> org.apache.kylin.dict.DictionaryManager.mergeDictionary(DictionaryManager.java:267)
> at
> org.apache.kylin.engine.mr.steps.MergeDictionaryStep.mergeDictionaries(MergeDictionaryStep.java:146)
> at
> org.apache.kylin.engine.mr.steps.MergeDictionaryStep.makeDictForNewSegment(MergeDictionaryStep.java:136)
> at
> org.apache.kylin.engine.mr.steps.MergeDictionaryStep.doWork(MergeDictionaryStep.java:68)
> at
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:124)
> ... 6 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-2947) Changed the Pop-up box when no project selected
[ https://issues.apache.org/jira/browse/KYLIN-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210773#comment-16210773 ] luguosheng commented on KYLIN-2947: --- Thanks for your patch, I will merge it soon! > Changed the Pop-up box when no project selected > --- > > Key: KYLIN-2947 > URL: https://issues.apache.org/jira/browse/KYLIN-2947 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua > Attachments: > 0001-KYLIN-2947-Changed-the-Pop-up-box-when-no-project-se.patch, 01.PNG, > 02.PNG, 03.PNG > > > I noticed that the Pop-up box was like 01.png when there is no project > selected after you click the 'Calculate Cardinality',it reminds us we should > choose project first after we input the tablename and click the 'Calculate > Cardinality'. > And it keeps 'please wait' status on my environment after input and click > like 02.png. > It's unproperly.We should ingore this step,point out that there is no project > selected directly after we click the 'Calculate Cardinality',just like 03.png. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2947) Changed the Pop-up box when no project selected
[ https://issues.apache.org/jira/browse/KYLIN-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-2947: Description: I noticed that the Pop-up box was like 01.png when there is no project selected after you click the 'Calculate Cardinality',it reminds us we should choose project first after we input the tablename and click the 'Calculate Cardinality'. And it keeps 'please wait' status on my environment after input and click like 02.png. It's unproperly.We should ingore this step,point out that there is no project selected directly after we click the 'Calculate Cardinality',just like 03.png. was: I noticed that the Pop-up box was like 01.png when there is no project selected after you click the 'Calculate Cardinality',it reminds us we should choose project first after we input the tablename and click the 'Calculate Cardinality'. And it keeps 'please wait' status on my environment after click like 02.png. We should ingore this step,point out that there is no project selected directly after we click the 'Calculate Cardinality',just like 03.png. > Changed the Pop-up box when no project selected > --- > > Key: KYLIN-2947 > URL: https://issues.apache.org/jira/browse/KYLIN-2947 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua > Attachments: > 0001-KYLIN-2947-Changed-the-Pop-up-box-when-no-project-se.patch, 01.PNG, > 02.PNG, 03.PNG > > > I noticed that the Pop-up box was like 01.png when there is no project > selected after you click the 'Calculate Cardinality',it reminds us we should > choose project first after we input the tablename and click the 'Calculate > Cardinality'. > And it keeps 'please wait' status on my environment after input and click > like 02.png. > It's unproperly.We should ingore this step,point out that there is no project > selected directly after we click the 'Calculate Cardinality',just like 03.png. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2947) Changed the Pop-up box when no project selected
[ https://issues.apache.org/jira/browse/KYLIN-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-2947: Description: I noticed that the Pop-up box was like 01.png when there is no project selected after you click the 'Calculate Cardinality',it reminds us we should choose project first after we input the tablename and click the 'Calculate Cardinality'. And it keeps 'please wait' status on my environment after click like 02.png. We should ingore this step,point out that there is no project selected directly after we click the 'Calculate Cardinality',just like 03.png. was: I noticed that the Pop-up box was like 01.png when there is no project selected after you click the 'Calculate Cardinality',it reminds us we should choose project first after we input the tablename after we click the 'Calculate Cardinality'. And it keeps 'please wait' status on my environment after click like 02.png. We should ingore this step,point out that there is no project selected directly after we click the 'Calculate Cardinality',just like 03.png. > Changed the Pop-up box when no project selected > --- > > Key: KYLIN-2947 > URL: https://issues.apache.org/jira/browse/KYLIN-2947 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua > Attachments: > 0001-KYLIN-2947-Changed-the-Pop-up-box-when-no-project-se.patch, 01.PNG, > 02.PNG, 03.PNG > > > I noticed that the Pop-up box was like 01.png when there is no project > selected after you click the 'Calculate Cardinality',it reminds us we should > choose project first after we input the tablename and click the 'Calculate > Cardinality'. > And it keeps 'please wait' status on my environment after click like 02.png. > We should ingore this step,point out that there is no project selected > directly after we click the 'Calculate Cardinality',just like 03.png. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2947) Changed the Pop-up box when no project selected
[ https://issues.apache.org/jira/browse/KYLIN-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-2947: Description: I noticed that the Pop-up box was like 01.png when there is no project selected after you click the 'Calculate Cardinality',it reminds us we should choose project first after we input the tablename after we click the 'Calculate Cardinality'. And it keeps 'please wait' status on my environment after click like 02.png. We should ingore this step,point out that there is no project selected directly after we click the 'Calculate Cardinality',just like 03.png. was: I noticed that the Pop-up box was like 01.png when there is no project selected after you click the 'Calculate Cardinality',it reminds us we should choose project first after we input the tablename. And it keeps 'please wait' status on my environment after click like 02.png. We should ingore this step,point out that there is no project selected directly after we click the 'Calculate Cardinality',just like 03.png. > Changed the Pop-up box when no project selected > --- > > Key: KYLIN-2947 > URL: https://issues.apache.org/jira/browse/KYLIN-2947 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua > Attachments: > 0001-KYLIN-2947-Changed-the-Pop-up-box-when-no-project-se.patch, 01.PNG, > 02.PNG, 03.PNG > > > I noticed that the Pop-up box was like 01.png when there is no project > selected after you click the 'Calculate Cardinality',it reminds us we should > choose project first after we input the tablename after we click the > 'Calculate Cardinality'. > And it keeps 'please wait' status on my environment after click like 02.png. > We should ingore this step,point out that there is no project selected > directly after we click the 'Calculate Cardinality',just like 03.png. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2947) Changed the Pop-up box when no project selected
[ https://issues.apache.org/jira/browse/KYLIN-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-2947: Attachment: 01.PNG 02.PNG 03.PNG 0001-KYLIN-2947-Changed-the-Pop-up-box-when-no-project-se.patch > Changed the Pop-up box when no project selected > --- > > Key: KYLIN-2947 > URL: https://issues.apache.org/jira/browse/KYLIN-2947 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua > Attachments: > 0001-KYLIN-2947-Changed-the-Pop-up-box-when-no-project-se.patch, 01.PNG, > 02.PNG, 03.PNG > > > I noticed that the Pop-up box was like 01.png when there is no project > selected after you click the 'Calculate Cardinality',it reminds us we should > choose project first after we input the tablename. > And it keeps 'please wait' status on my environment after click like 02.png. > We should ingore this step,point out that there is no project selected > directly after we click the 'Calculate Cardinality',just like 03.png. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2947) Changed the Pop-up box when no project selected
[ https://issues.apache.org/jira/browse/KYLIN-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated KYLIN-2947: Description: I noticed that the Pop-up box was like 01.png when there is no project selected after you click the 'Calculate Cardinality',it reminds us we should choose project first after we input the tablename. And it keeps 'please wait' status on my environment after click like 02.png. We should ingore this step,point out that there is no project selected directly after we click the 'Calculate Cardinality',just like 03.png. > Changed the Pop-up box when no project selected > --- > > Key: KYLIN-2947 > URL: https://issues.apache.org/jira/browse/KYLIN-2947 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua > > I noticed that the Pop-up box was like 01.png when there is no project > selected after you click the 'Calculate Cardinality',it reminds us we should > choose project first after we input the tablename. > And it keeps 'please wait' status on my environment after click like 02.png. > We should ingore this step,point out that there is no project selected > directly after we click the 'Calculate Cardinality',just like 03.png. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2947) Changed the Pop-up box when no project selected
peng.jianhua created KYLIN-2947: --- Summary: Changed the Pop-up box when no project selected Key: KYLIN-2947 URL: https://issues.apache.org/jira/browse/KYLIN-2947 Project: Kylin Issue Type: Improvement Affects Versions: v2.3.0 Reporter: peng.jianhua Assignee: peng.jianhua -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2756) Let "LIMIT" be optional in "Inspect" page
[ https://issues.apache.org/jira/browse/KYLIN-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2756: - Attachment: 0001-KYLIN-2756-Let-LIMIT-be-optional-in-inspect-page.patch I have completed this issue.Please review it.Thanks! > Let "LIMIT" be optional in "Inspect" page > - > > Key: KYLIN-2756 > URL: https://issues.apache.org/jira/browse/KYLIN-2756 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Attachments: > 0001-KYLIN-2756-Let-LIMIT-be-optional-in-inspect-page.patch > > > Kylin's "Inspect" page will append a LIMIT clause for queries if the query > doesn't have "LIMIT"; > While this will make some query be invalid because "LIMIT" not always appear > in the last position. For example: > select * from KYLIN_SALES OFFSET 100 ROWS FETCH FIRST 10 ROWS ONLY > According to Calcite's SQL reference, LIMIT should be before OFFSET clause. > So, Kylin should give user the option of not append the "LIMIT". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
