[jira] [Commented] (KYLIN-5820) added pagination and add count distinct function in batch measure dialog
[ https://issues.apache.org/jira/browse/KYLIN-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835098#comment-17835098 ] ASF subversion and git services commented on KYLIN-5820: Commit f6cc0ce32c82e3102a2fe27db9c3b9a99f43bd47 in kylin's branch refs/heads/kylin5 from huangchunyan [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=f6cc0ce32c ] KYLIN-5820,added pagination and add count distinct function in batch measure dialog > added pagination and add count distinct function in batch measure dialog > - > > Key: KYLIN-5820 > URL: https://issues.apache.org/jira/browse/KYLIN-5820 > Project: Kylin > Issue Type: Improvement >Reporter: chunyan.huang >Assignee: chunyan.huang >Priority: Critical > Fix For: 5.0.0 > > Attachments: image-2024-04-09-09-54-05-858.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5813) improve query history page filter item and model list page button text
[ https://issues.apache.org/jira/browse/KYLIN-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835095#comment-17835095 ] ASF GitHub Bot commented on KYLIN-5813: --- liyang-kylin merged PR #2169: URL: https://github.com/apache/kylin/pull/2169 > improve query history page filter item and model list page button text > -- > > Key: KYLIN-5813 > URL: https://issues.apache.org/jira/browse/KYLIN-5813 > Project: Kylin > Issue Type: Improvement >Reporter: chunyan.huang >Assignee: chunyan.huang >Priority: Major > Fix For: 5.0.0 > > Attachments: image-2024-04-09-09-38-42-450.png, > image-2024-04-09-09-39-13-571.png, image-2024-04-09-09-39-40-593.png, > image-2024-04-09-09-44-16-515.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] KYLIN-5820,added pagination and add count distinct function in batch measure dialog [kylin]
liyang-kylin merged PR #2171: URL: https://github.com/apache/kylin/pull/2171 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@kylin.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] KYLIN-5813,history filter issue [kylin]
liyang-kylin merged PR #2169: URL: https://github.com/apache/kylin/pull/2169 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@kylin.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (KYLIN-5820) added pagination and add count distinct function in batch measure dialog
[ https://issues.apache.org/jira/browse/KYLIN-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835097#comment-17835097 ] ASF GitHub Bot commented on KYLIN-5820: --- liyang-kylin merged PR #2171: URL: https://github.com/apache/kylin/pull/2171 > added pagination and add count distinct function in batch measure dialog > - > > Key: KYLIN-5820 > URL: https://issues.apache.org/jira/browse/KYLIN-5820 > Project: Kylin > Issue Type: Improvement >Reporter: chunyan.huang >Assignee: chunyan.huang >Priority: Critical > Fix For: 5.0.0 > > Attachments: image-2024-04-09-09-54-05-858.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5813) improve query history page filter item and model list page button text
[ https://issues.apache.org/jira/browse/KYLIN-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835096#comment-17835096 ] ASF subversion and git services commented on KYLIN-5813: Commit 8c91a1a4eddbf0ed29f0e81487ea1e088cbf736b in kylin's branch refs/heads/kylin5 from huangchunyan [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=8c91a1a4ed ] KYLIN-5813,improve query history page filter item and model list page button text > improve query history page filter item and model list page button text > -- > > Key: KYLIN-5813 > URL: https://issues.apache.org/jira/browse/KYLIN-5813 > Project: Kylin > Issue Type: Improvement >Reporter: chunyan.huang >Assignee: chunyan.huang >Priority: Major > Fix For: 5.0.0 > > Attachments: image-2024-04-09-09-38-42-450.png, > image-2024-04-09-09-39-13-571.png, image-2024-04-09-09-39-40-593.png, > image-2024-04-09-09-44-16-515.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5820) added pagination and add count distinct function in batch measure dialog
[ https://issues.apache.org/jira/browse/KYLIN-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chunyan.huang updated KYLIN-5820: - Attachment: image-2024-04-09-09-54-05-858.png > added pagination and add count distinct function in batch measure dialog > - > > Key: KYLIN-5820 > URL: https://issues.apache.org/jira/browse/KYLIN-5820 > Project: Kylin > Issue Type: Improvement >Reporter: chunyan.huang >Assignee: chunyan.huang >Priority: Critical > Fix For: 5.0.0 > > Attachments: image-2024-04-09-09-54-05-858.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5820) added pagination and add count distinct function in batch measure dialog
[ https://issues.apache.org/jira/browse/KYLIN-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835094#comment-17835094 ] chunyan.huang commented on KYLIN-5820: -- h1. test evidence !image-2024-04-09-09-54-05-858.png! > added pagination and add count distinct function in batch measure dialog > - > > Key: KYLIN-5820 > URL: https://issues.apache.org/jira/browse/KYLIN-5820 > Project: Kylin > Issue Type: Improvement >Reporter: chunyan.huang >Assignee: chunyan.huang >Priority: Critical > Fix For: 5.0.0 > > Attachments: image-2024-04-09-09-54-05-858.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (KYLIN-5813) improve query history page filter item and model list page button text
[ https://issues.apache.org/jira/browse/KYLIN-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835091#comment-17835091 ] chunyan.huang edited comment on KYLIN-5813 at 4/9/24 1:45 AM: -- h1. test evidence h2. query history page change: filter ui !image-2024-04-09-09-38-42-450.png! !image-2024-04-09-09-39-13-571.png! celar all !image-2024-04-09-09-39-40-593.png! h2. model list page !image-2024-04-09-09-44-16-515.png! was (Author: chunyan.huang): test evidence 1. query history page change: filter ui !image-2024-04-09-09-38-42-450.png! !image-2024-04-09-09-39-13-571.png! celar all !image-2024-04-09-09-39-40-593.png! 2. model list page !image-2024-04-09-09-44-16-515.png! > improve query history page filter item and model list page button text > -- > > Key: KYLIN-5813 > URL: https://issues.apache.org/jira/browse/KYLIN-5813 > Project: Kylin > Issue Type: Improvement >Reporter: chunyan.huang >Assignee: chunyan.huang >Priority: Major > Fix For: 5.0.0 > > Attachments: image-2024-04-09-09-38-42-450.png, > image-2024-04-09-09-39-13-571.png, image-2024-04-09-09-39-40-593.png, > image-2024-04-09-09-44-16-515.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5813) improve query history page filter item and model list page button text
[ https://issues.apache.org/jira/browse/KYLIN-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chunyan.huang updated KYLIN-5813: - Attachment: image-2024-04-09-09-44-16-515.png > improve query history page filter item and model list page button text > -- > > Key: KYLIN-5813 > URL: https://issues.apache.org/jira/browse/KYLIN-5813 > Project: Kylin > Issue Type: Improvement >Reporter: chunyan.huang >Assignee: chunyan.huang >Priority: Major > Fix For: 5.0.0 > > Attachments: image-2024-04-09-09-38-42-450.png, > image-2024-04-09-09-39-13-571.png, image-2024-04-09-09-39-40-593.png, > image-2024-04-09-09-44-16-515.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5813) improve query history page filter item and model list page button text
[ https://issues.apache.org/jira/browse/KYLIN-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835091#comment-17835091 ] chunyan.huang commented on KYLIN-5813: -- test evidence 1. query history page change: filter ui !image-2024-04-09-09-38-42-450.png! !image-2024-04-09-09-39-13-571.png! celar all !image-2024-04-09-09-39-40-593.png! 2. model list page !image-2024-04-09-09-44-16-515.png! > improve query history page filter item and model list page button text > -- > > Key: KYLIN-5813 > URL: https://issues.apache.org/jira/browse/KYLIN-5813 > Project: Kylin > Issue Type: Improvement >Reporter: chunyan.huang >Assignee: chunyan.huang >Priority: Major > Fix For: 5.0.0 > > Attachments: image-2024-04-09-09-38-42-450.png, > image-2024-04-09-09-39-13-571.png, image-2024-04-09-09-39-40-593.png, > image-2024-04-09-09-44-16-515.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5813) improve query history page filter item and model list page button text
[ https://issues.apache.org/jira/browse/KYLIN-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chunyan.huang updated KYLIN-5813: - Attachment: image-2024-04-09-09-39-13-571.png > improve query history page filter item and model list page button text > -- > > Key: KYLIN-5813 > URL: https://issues.apache.org/jira/browse/KYLIN-5813 > Project: Kylin > Issue Type: Improvement >Reporter: chunyan.huang >Assignee: chunyan.huang >Priority: Major > Fix For: 5.0.0 > > Attachments: image-2024-04-09-09-38-42-450.png, > image-2024-04-09-09-39-13-571.png, image-2024-04-09-09-39-40-593.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5813) improve query history page filter item and model list page button text
[ https://issues.apache.org/jira/browse/KYLIN-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chunyan.huang updated KYLIN-5813: - Attachment: image-2024-04-09-09-39-40-593.png > improve query history page filter item and model list page button text > -- > > Key: KYLIN-5813 > URL: https://issues.apache.org/jira/browse/KYLIN-5813 > Project: Kylin > Issue Type: Improvement >Reporter: chunyan.huang >Assignee: chunyan.huang >Priority: Major > Fix For: 5.0.0 > > Attachments: image-2024-04-09-09-38-42-450.png, > image-2024-04-09-09-39-13-571.png, image-2024-04-09-09-39-40-593.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5813) improve query history page filter item and model list page button text
[ https://issues.apache.org/jira/browse/KYLIN-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chunyan.huang updated KYLIN-5813: - Attachment: image-2024-04-09-09-38-42-450.png > improve query history page filter item and model list page button text > -- > > Key: KYLIN-5813 > URL: https://issues.apache.org/jira/browse/KYLIN-5813 > Project: Kylin > Issue Type: Improvement >Reporter: chunyan.huang >Assignee: chunyan.huang >Priority: Major > Fix For: 5.0.0 > > Attachments: image-2024-04-09-09-38-42-450.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5783) Round query result of decimal zero by config
[ https://issues.apache.org/jira/browse/KYLIN-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834935#comment-17834935 ] pengfei.zhan commented on KYLIN-5783: - h1. Design Add a new configuration item kylin.query.round-decimal-zero, true means ignore the precision of Decimal 0, convert any 0.0, 0.00, 0., etc. to 0, false means don't convert, keep the original logic. The default is false, which supports project-level configuration. Project level configuration practice is dirty, do not support project level configuration. Model response is handled by sparder, so new type conversion logic is added in SparderTypeUtil, only the columns with data type decimal, return value BigDecimal and value 0 are converted; downward pressure hive is converted to the columns with return value BigDecimal and value 0. The above conversion only takes effect when the configuration item is turned on. > Round query result of decimal zero by config > > > Key: KYLIN-5783 > URL: https://issues.apache.org/jira/browse/KYLIN-5783 > Project: Kylin > Issue Type: Improvement > Components: Query Engine >Affects Versions: 5.0-beta >Reporter: pengfei.zhan >Assignee: pengfei.zhan >Priority: Minor > Fix For: 5.0-beta > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5782) Duplicated join keys result empty query result
[ https://issues.apache.org/jira/browse/KYLIN-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834934#comment-17834934 ] pengfei.zhan commented on KYLIN-5782: - h1. Design As in the previous analysis, replacing the original Map with Map>. > Duplicated join keys result empty query result > -- > > Key: KYLIN-5782 > URL: https://issues.apache.org/jira/browse/KYLIN-5782 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: 5.0-beta >Reporter: pengfei.zhan >Assignee: pengfei.zhan >Priority: Major > Fix For: 5.0-beta > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5782) Duplicated join keys result empty query result
[ https://issues.apache.org/jira/browse/KYLIN-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834933#comment-17834933 ] pengfei.zhan commented on KYLIN-5782: - h1. Root Cause After the context is sliced, the columns on the join condition will be pressed down to the sub context, the customer's join condition is like a = b and c = d and a = e, the code is using map to collect the information of the join keys, and use the column on the left of the equals sign as the key, and the column on the right as the value, when a=e is put into the map, the column b is overwritten due to the duplication of the key and a=b, and only the column c, d, a, and e are collected, and the column b is omitted. When a=e is put into the map, b is overwritten because the key is duplicated with a=b, and the only columns collected are c, d, a, and e, leaving out b. This results in b being used as the dummy column, but this column will eventually be used as the join key, which results in the data being empty. > Duplicated join keys result empty query result > -- > > Key: KYLIN-5782 > URL: https://issues.apache.org/jira/browse/KYLIN-5782 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: 5.0-beta >Reporter: pengfei.zhan >Assignee: pengfei.zhan >Priority: Major > Fix For: 5.0-beta > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5782) Duplicated join keys result empty query result
[
https://issues.apache.org/jira/browse/KYLIN-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834932#comment-17834932
]
pengfei.zhan commented on KYLIN-5782:
-
The sql to reproduce problem
{code:sql}
select count(*) from
KYLIN_SALES t1 inner join KYLIN_CAL_DT t2
on t1.part_dt = t2.cal_dt and t1.part_dt = t2.month_beg_dt
group by t1.part_dt
limit 10{code}
> Duplicated join keys result empty query result
> --
>
> Key: KYLIN-5782
> URL: https://issues.apache.org/jira/browse/KYLIN-5782
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Affects Versions: 5.0-beta
>Reporter: pengfei.zhan
>Assignee: pengfei.zhan
>Priority: Major
> Fix For: 5.0-beta
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KYLIN-5781) Adjust the query result order of sql with union
[ https://issues.apache.org/jira/browse/KYLIN-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834931#comment-17834931 ] pengfei.zhan commented on KYLIN-5781: - h1. Design In the case of union, after getting the child nodes, just do the inverse order sorting. Add the configuration kylin.query.collect-union-in-order to be true by default to keep the order in the sql by default. > Adjust the query result order of sql with union > --- > > Key: KYLIN-5781 > URL: https://issues.apache.org/jira/browse/KYLIN-5781 > Project: Kylin > Issue Type: Improvement > Components: Query Engine >Affects Versions: 5.0-beta >Reporter: pengfei.zhan >Assignee: pengfei.zhan >Priority: Major > Fix For: 5.0-beta > > Attachments: KYLIN_5781.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5781) Adjust the query result order of sql with union
[ https://issues.apache.org/jira/browse/KYLIN-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834930#comment-17834930 ] pengfei.zhan commented on KYLIN-5781: - h1. Description When traversing the RelNode tree, subsequent traversal is used, and the stack is used to record some child nodes. The design is reasonable. !KYLIN_5781.png! For the RelNode tree shown above, the traversal process is: Process a first and put it on the stack, then b and put it on the stack, then c and put it on the stack; Process union 2, pop two nodes from the stack, namely c, b The order of c, b does not match the original order. > Adjust the query result order of sql with union > --- > > Key: KYLIN-5781 > URL: https://issues.apache.org/jira/browse/KYLIN-5781 > Project: Kylin > Issue Type: Improvement > Components: Query Engine >Affects Versions: 5.0-beta >Reporter: pengfei.zhan >Assignee: pengfei.zhan >Priority: Major > Fix For: 5.0-beta > > Attachments: KYLIN_5781.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5781) Adjust the query result order of sql with union
[ https://issues.apache.org/jira/browse/KYLIN-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pengfei.zhan updated KYLIN-5781: Attachment: KYLIN_5781.png > Adjust the query result order of sql with union > --- > > Key: KYLIN-5781 > URL: https://issues.apache.org/jira/browse/KYLIN-5781 > Project: Kylin > Issue Type: Improvement > Components: Query Engine >Affects Versions: 5.0-beta >Reporter: pengfei.zhan >Assignee: pengfei.zhan >Priority: Major > Fix For: 5.0-beta > > Attachments: KYLIN_5781.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5780) Dimension capacity does not work
[ https://issues.apache.org/jira/browse/KYLIN-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834926#comment-17834926 ] pengfei.zhan commented on KYLIN-5780: - h1. Design GET /kylin/api/index_plans/rule Normally display the "Maximum number of dimension combinations" at the bottom of the "Aggregation Group" setting The global maximum number of dimension combinations is effective for all aggregation groups, and is subject to the last setting. Modify logic: When assigning a value to "Maximum number of dimension combinations", both the batch model and the flow model exist. You need to determine the size of the timestamp. > Dimension capacity does not work > > > Key: KYLIN-5780 > URL: https://issues.apache.org/jira/browse/KYLIN-5780 > Project: Kylin > Issue Type: Bug > Components: Modeling >Affects Versions: 5.0-beta >Reporter: pengfei.zhan >Assignee: pengfei.zhan >Priority: Major > Fix For: 5.0-beta > > > The setting of the maximum number of dimension combinations at the bottom of > the aggregation group does not take effect. > When editing an aggregation group, set the maximum number of dimension > combinations at the bottom (applicable to aggregation groups that do not have > a maximum number of dimension combinations set) to 1. After saving, when > editing again, it becomes unlimited. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5780) Dimension capacity does not work
[ https://issues.apache.org/jira/browse/KYLIN-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834925#comment-17834925 ] pengfei.zhan commented on KYLIN-5780: - h1. Acceptance # Set the "Maximum number of dimension combinations" at the bottom of the "aggregation group". After saving and building, when you edit "the aggregation group" again, the "maximum number of dimension combinations" at the bottom will be the value set when the last time you saved the build. # If the maximum number of dimension combinations is not set for a single aggregation group, the maximum number of dimension combinations of this aggregation group will be overwritten by the maximum number of dimension combinations at all aggregation group levels. If a maximum number of dimension combinations is set for a single aggregation group, the number of index dimensions of this aggregation group is only limited by the maximum number of dimension combinations of this single aggregation group. If the maximum number of dimension combinations at all aggregation group levels is left blank, it means that the user has turned off the setting of the maximum number of dimension combinations at all aggregation group levels. At this time, the number of dimensions in the index generated by an aggregation group that has not been set separately for the maximum number of dimension combinations is unlimited. Aggregation groups that have been set to the maximum number of dimension combinations at a single aggregation group level are not affected. > Dimension capacity does not work > > > Key: KYLIN-5780 > URL: https://issues.apache.org/jira/browse/KYLIN-5780 > Project: Kylin > Issue Type: Bug > Components: Modeling >Affects Versions: 5.0-beta >Reporter: pengfei.zhan >Assignee: pengfei.zhan >Priority: Major > Fix For: 5.0-beta > > > The setting of the maximum number of dimension combinations at the bottom of > the aggregation group does not take effect. > When editing an aggregation group, set the maximum number of dimension > combinations at the bottom (applicable to aggregation groups that do not have > a maximum number of dimension combinations set) to 1. After saving, when > editing again, it becomes unlimited. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5780) Dimension capacity does not work
[ https://issues.apache.org/jira/browse/KYLIN-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pengfei.zhan updated KYLIN-5780: Description: The setting of the maximum number of dimension combinations at the bottom of the aggregation group does not take effect. When editing an aggregation group, set the maximum number of dimension combinations at the bottom (applicable to aggregation groups that do not have a maximum number of dimension combinations set) to 1. After saving, when editing again, it becomes unlimited. > Dimension capacity does not work > > > Key: KYLIN-5780 > URL: https://issues.apache.org/jira/browse/KYLIN-5780 > Project: Kylin > Issue Type: Bug > Components: Modeling >Affects Versions: 5.0-beta >Reporter: pengfei.zhan >Assignee: pengfei.zhan >Priority: Major > Fix For: 5.0-beta > > > The setting of the maximum number of dimension combinations at the bottom of > the aggregation group does not take effect. > When editing an aggregation group, set the maximum number of dimension > combinations at the bottom (applicable to aggregation groups that do not have > a maximum number of dimension combinations set) to 1. After saving, when > editing again, it becomes unlimited. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5779) Without project permission，calling "kylin/api/access/acls" api occurs NPE
[
https://issues.apache.org/jira/browse/KYLIN-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834923#comment-17834923
]
pengfei.zhan commented on KYLIN-5779:
-
h1. Fix Design
change the following code snappy
{code:java}
int mask = projectPermissions.get(getSid(groupName, false));{code}
to
{code:java}
int mask = projectPermissions.getOrDefault(getSid(groupName, false), 0){code}
After getting the response, do some filter to solve this problem.
org.apache.kylin.rest.controller.open.OpenAccessController#getUserOrGroupAclPermissions
{{response.stream().filter(e ->
!AclConstants.EMPTY.equals(e.getProjectPermission())).collect(Collectors.toList())}}
> Without project permission，calling "kylin/api/access/acls" api occurs NPE
> -
>
> Key: KYLIN-5779
> URL: https://issues.apache.org/jira/browse/KYLIN-5779
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Affects Versions: 5.0-beta
>Reporter: pengfei.zhan
>Assignee: pengfei.zhan
>Priority: Major
> Fix For: 5.0-beta
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KYLIN-5777) Change spark.yarn.submit.file.replication from 1 to 3
[ https://issues.apache.org/jira/browse/KYLIN-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834920#comment-17834920 ] pengfei.zhan commented on KYLIN-5777: - The design is as described in the issue > Change spark.yarn.submit.file.replication from 1 to 3 > - > > Key: KYLIN-5777 > URL: https://issues.apache.org/jira/browse/KYLIN-5777 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: 5.0-beta >Reporter: pengfei.zhan >Assignee: pengfei.zhan >Priority: Major > Fix For: 5.0-beta > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5776) Support parameter type is string for timestampadd
[ https://issues.apache.org/jira/browse/KYLIN-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834918#comment-17834918 ] pengfei.zhan commented on KYLIN-5776: - h1. Design For the function timestampadd, calcite for kylin will transfer to datetime_plus to fold the constant, however, the calculation does not support string. If the first parameter is year/day/month/quarter, the constant folding works but gives wrong result. In order to support this, add some functions to support string. > Support parameter type is string for timestampadd > - > > Key: KYLIN-5776 > URL: https://issues.apache.org/jira/browse/KYLIN-5776 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: 5.0-beta >Reporter: pengfei.zhan >Assignee: pengfei.zhan >Priority: Major > Fix For: 5.0-beta > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5776) Support parameter type is string for timestampadd
[
https://issues.apache.org/jira/browse/KYLIN-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834917#comment-17834917
]
pengfei.zhan commented on KYLIN-5776:
-
At present, the following sql
{code:sql}
select trunc(TIMESTAMPADD(year, -1, date '2023-07-01'), 'MM') from ssb.lineorder
{code}
is supported by Kylin5. However, if the date was expressed with string, it is
not supported yet.
{code:sql}
select trunc(TIMESTAMPADD(year, -1, '2023-07-01'), 'MM') from ssb.lineorder
{code}
> Support parameter type is string for timestampadd
> -
>
> Key: KYLIN-5776
> URL: https://issues.apache.org/jira/browse/KYLIN-5776
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Affects Versions: 5.0-beta
>Reporter: pengfei.zhan
>Assignee: pengfei.zhan
>Priority: Major
> Fix For: 5.0-beta
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KYLIN-5775) Upgrade testcontainers to version 1.16.2
[ https://issues.apache.org/jira/browse/KYLIN-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834914#comment-17834914 ] pengfei.zhan commented on KYLIN-5775: - Refer to [https://github.com/testcontainers/testcontainers-java/pull/4597] Upgrade the version to 1.16.2 > Upgrade testcontainers to version 1.16.2 > > > Key: KYLIN-5775 > URL: https://issues.apache.org/jira/browse/KYLIN-5775 > Project: Kylin > Issue Type: Bug > Components: Others >Affects Versions: 5.0-beta >Reporter: pengfei.zhan >Assignee: pengfei.zhan >Priority: Major > Fix For: 5.0-beta > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] fix frontend build sh [kylin]
liyang-kylin merged PR #2179: URL: https://github.com/apache/kylin/pull/2179 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@kylin.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
