[jira] [Updated] (KYLIN-5263) replace log4j with logback
[ https://issues.apache.org/jira/browse/KYLIN-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhaoliu updated KYLIN-5263: --- Description: 在查询并发高的时候，发现线程会阻塞在日志打印处，可以使用更高效的logback替换当前的log4j. !screenshot-1.png! was: 在查询并发高的时候，发现线程会阻塞在日志打印处，可以使用更高效的logback替换当前的log4j. locked org.apache.log4j.spi.RootLogger > replace log4j with logback > -- > > Key: KYLIN-5263 > URL: https://issues.apache.org/jira/browse/KYLIN-5263 > Project: Kylin > Issue Type: Improvement > Components: Query Engine >Affects Versions: v4.0.1 >Reporter: zhaoliu >Priority: Minor > Attachments: screenshot-1.png > > > 在查询并发高的时候，发现线程会阻塞在日志打印处，可以使用更高效的logback替换当前的log4j. > !screenshot-1.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5263) replace log4j with logback
[ https://issues.apache.org/jira/browse/KYLIN-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhaoliu updated KYLIN-5263: --- Attachment: screenshot-1.png > replace log4j with logback > -- > > Key: KYLIN-5263 > URL: https://issues.apache.org/jira/browse/KYLIN-5263 > Project: Kylin > Issue Type: Improvement > Components: Query Engine >Affects Versions: v4.0.1 >Reporter: zhaoliu >Priority: Minor > Attachments: screenshot-1.png > > > 在查询并发高的时候，发现线程会阻塞在日志打印处，可以使用更高效的logback替换当前的log4j. > locked org.apache.log4j.spi.RootLogger -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KYLIN-5263) replace log4j with logback
zhaoliu created KYLIN-5263: -- Summary: replace log4j with logback Key: KYLIN-5263 URL: https://issues.apache.org/jira/browse/KYLIN-5263 Project: Kylin Issue Type: Improvement Components: Query Engine Affects Versions: v4.0.1 Reporter: zhaoliu 在查询并发高的时候，发现线程会阻塞在日志打印处，可以使用更高效的logback替换当前的log4j. locked org.apache.log4j.spi.RootLogger -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5259) Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL
[ https://issues.apache.org/jira/browse/KYLIN-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee updated KYLIN-5259: Component/s: Documentation > Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL > -- > > Key: KYLIN-5259 > URL: https://issues.apache.org/jira/browse/KYLIN-5259 > Project: Kylin > Issue Type: Wish > Components: Documentation >Affects Versions: v3.1.3 >Reporter: yoonsung.lee >Priority: Major > > Hi. I have been using Kylin 3.1.3. > Kylin's SQL seems to do not support DAY*, WEEK*, MONTH*, YEAR* functions. * > means series of functions such as day, day_of_week, day_of_month, > day_of_year. > Are there existing features to support these? > If not, is there any plan to support these? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5259) Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL
[ https://issues.apache.org/jira/browse/KYLIN-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1760#comment-1760 ] yoonsung.lee commented on KYLIN-5259: - I tried them and they work fine. Thanks to respond :) > Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL > -- > > Key: KYLIN-5259 > URL: https://issues.apache.org/jira/browse/KYLIN-5259 > Project: Kylin > Issue Type: Wish >Affects Versions: v3.1.3 >Reporter: yoonsung.lee >Priority: Major > > Hi. I have been using Kylin 3.1.3. > Kylin's SQL seems to do not support DAY*, WEEK*, MONTH*, YEAR* functions. * > means series of functions such as day, day_of_week, day_of_month, > day_of_year. > Are there existing features to support these? > If not, is there any plan to support these? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [kylin] hit-lacus merged pull request #1977: Update how_to_write_doc.md
hit-lacus merged PR #1977: URL: https://github.com/apache/kylin/pull/1977 -- 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
[GitHub] [kylin] hit-lacus commented on pull request #1977: Update how_to_write_doc.md
hit-lacus commented on PR #1977: URL: https://github.com/apache/kylin/pull/1977#issuecomment-1244770002 Thanks for contribute some new tips and reference links! -- 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
[GitHub] [kylin] liyang-kylin opened a new pull request, #1977: Update how_to_write_doc.md
liyang-kylin opened a new pull request, #1977: URL: https://github.com/apache/kylin/pull/1977 ## Proposed changes Improve the how-to-contribute-doc page - Smoother English - Added some troubleshooting info - Added some reference links ## Branch to commit - [ ] Branch **kylin3** for v2.x to v3.x - [ ] Branch **kylin4** for v4.x - [ ] Branch **kylin5** for v5.x ## Types of changes What types of changes does your code introduce to Kylin? _Put an `x` in the boxes that apply_ - [ ] Bugfix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Documentation Update (if none of the other choices apply) ## Checklist _Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code._ - [ ] I have created an issue on [Kylin's jira](https://issues.apache.org/jira/browse/KYLIN), and have described the bug/feature there in detail - [ ] Commit messages in my PR start with the related jira ID, like "KYLIN- Make Kylin project open-source" - [ ] Compiling and unit tests pass locally with my changes - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I have added necessary documentation (if appropriate) - [ ] Any dependent changes have been merged ## Further comments If this is a relatively large or complex change, kick off the discussion at u...@kylin.apache.org or d...@kylin.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc... -- 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-5253) Is there any plan to add field processing method
[ https://issues.apache.org/jira/browse/KYLIN-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602996#comment-17602996 ] liyang commented on KYLIN-5253: --- any of these work? * SUBSTRING(string FROM integer1 FOR integer2) * concat(str1, str2) * left(str,n) if yes, then the doc needs improvement > Is there any plan to add field processing method > > > Key: KYLIN-5253 > URL: https://issues.apache.org/jira/browse/KYLIN-5253 > Project: Kylin > Issue Type: Wish > Components: Flink Engine >Reporter: zys >Priority: Major > > Hi! Is there any plan to add field processing method, such as concat, substr? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5255) UTF-8 column name support
[
https://issues.apache.org/jira/browse/KYLIN-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602992#comment-17602992
]
liyang commented on KYLIN-5255:
---
Nice improvement suggestion.
> UTF-8 column name support
> -
>
> Key: KYLIN-5255
> URL: https://issues.apache.org/jira/browse/KYLIN-5255
> Project: Kylin
> Issue Type: Wish
>Affects Versions: v4.0.1
>Reporter: Lilo
>Priority: Major
>
> Perhaps it's an appropriate time to support UTF-8 column names? (Kylin4 using
> Spark to build Cube)
> Although the Hive documentation still says that UTF-8 characters are not
> supported for table or column names, but after some simple sql tweaks to hive
> metadata, we had no problems using UTF-8 column names in production (e.g. in
> Hive / Spark2 / Spark3 / Impala / Presto / Flink).
>
> (Tweaks like
> {code:sql}
> alter table COLUMNS_V2 modify column COLUMN_NAME varchar(255) character set
> utf8;{code}
> )
>
> also:
> https://issues.apache.org/jira/browse/KYLIN-2816
> https://issues.apache.org/jira/browse/KYLIN-3668
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KYLIN-5259) Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL
[ https://issues.apache.org/jira/browse/KYLIN-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602983#comment-17602983 ] liyang commented on KYLIN-5259: --- try * DAYOFYEAR(date) * DAYOFMONTH(date) * DAYOFWEEK(date) * MONTH(date) * WEEK(date) * YEAR(date) if these work, em, the doc needs improvements > Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL > -- > > Key: KYLIN-5259 > URL: https://issues.apache.org/jira/browse/KYLIN-5259 > Project: Kylin > Issue Type: Wish >Affects Versions: v3.1.3 >Reporter: yoonsung.lee >Priority: Major > > Hi. I have been using Kylin 3.1.3. > Kylin's SQL seems to do not support DAY*, WEEK*, MONTH*, YEAR* functions. * > means series of functions such as day, day_of_week, day_of_month, > day_of_year. > Are there existing features to support these? > If not, is there any plan to support these? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5258) kylin5 HiveMetaStore
[ https://issues.apache.org/jira/browse/KYLIN-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602978#comment-17602978 ] liyang commented on KYLIN-5258: --- There must be deeper cause (likely caused by) not mentioned in the log. Please share the cause and solution together for other's reference. > kylin5 HiveMetaStore > > > Key: KYLIN-5258 > URL: https://issues.apache.org/jira/browse/KYLIN-5258 > Project: Kylin > Issue Type: Bug > Components: Metadata >Affects Versions: 5.0-alpha >Reporter: zys >Priority: Blocker > > Hi! i compile kylin5 and found that there are more settings in > kylin.properties, such as > spark.sql.hive.metastore. After start cmd, found errors in logs/check-env.out > like that: > > 22/09/07 22:10:08 WARN metadata.Hive: Failed to register all functions. > java.lang.RuntimeException: Unable to instantiate > org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient > at > org.apache.hadoop.hive.metastore.MetaStoreUtils.newInstance(MetaStoreUtils.java:1662) > at > org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.(RetryingMetaStoreClient.java:67) > at > org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.getProxy(RetryingMetaStoreClient.java:82) > at > org.apache.hadoop.hive.ql.metadata.Hive.createMetaStoreClient(Hive.java:3411) > at org.apache.hadoop.hive.ql.metadata.Hive.getMSC(Hive.java:3430) > at > org.apache.hadoop.hive.ql.metadata.Hive.getAllFunctions(Hive.java:3655) > at > org.apache.hadoop.hive.ql.metadata.Hive.reloadFunctions(Hive.java:231) > at > org.apache.hadoop.hive.ql.metadata.Hive.registerAllFunctionsOnce(Hive.java:215) > > hive.metastore.version is 1.1.0. i have tried spark2.*, 3.*, and put > hive.site-xml in $SPARK_HOME/conf, the result is same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5261) Suggest to add group owner to identify the usergoup's owner
[ https://issues.apache.org/jira/browse/KYLIN-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602977#comment-17602977 ] liyang commented on KYLIN-5261: --- Good idea. Code commit is welcome. :) > Suggest to add group owner to identify the usergoup's owner > --- > > Key: KYLIN-5261 > URL: https://issues.apache.org/jira/browse/KYLIN-5261 > Project: Kylin > Issue Type: Improvement > Components: Others >Affects Versions: Future >Reporter: Li Can >Priority: Major > Attachments: image-2022-09-09-16-45-37-415.png > > > !image-2022-09-09-16-45-37-415.png|width=390,height=200! > above this UserGroup authorization part, suggest to add group owner to > identify the group's owner, thus when someone need other group permission, > he/she can contact the owner quickly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
