[jira] [Commented] (KYLIN-4750) ldap do not working
[ https://issues.apache.org/jira/browse/KYLIN-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17212133#comment-17212133 ] chen wenqiang commented on KYLIN-4750: -- hi [~zhangyaqian] , version is 3.1.0, I downloaded source code and found the default value of searchSubtree is false, but my ldap users are stored in different tree levels, so kylin was not working well. Maybe your user info is in a same level, I guess. [~sonuSINGH], I also had problem like yours, because the length of password is longer than 15, and it goes well when I shortened my password. But I found some issues said this problem had been solved... So, maybe you can have a try... By the way, encryption key may not be same in different kylin versions, you'd better encrypt you password again if upgrade. > ldap do not working > --- > > Key: KYLIN-4750 > URL: https://issues.apache.org/jira/browse/KYLIN-4750 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v3.1.0 >Reporter: chen wenqiang >Priority: Major > > kylinSecurity.xml 文件中 LDAPAuthoritiesPopulator 的 searchSubtree > 没有配置true，使role无法查询到，无法登录，需要以下配置项。 > > > -- > In file kylinSecurity.xml, property in bean class > is not setting. Cause admin role in ldap cannot be > find. Suppose to add configuration as below in kylinSecurity.xml like old > versions. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-4750) ldap do not working
[ https://issues.apache.org/jira/browse/KYLIN-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17212123#comment-17212123 ] Sonu Singh commented on KYLIN-4750: --- Hi Yaqian Zhang, I am also facing LDAP issue with Kylin 3.1.0. Please find the error log and I am not able to start Kylin itself with below error: After enabling LDAP, kylin application is not able to start. 2020-09-16 09:54:35,511 DEBUG [localhost-startStop-1] security.PasswordPlaceholderConfigurer:174 : Loading properties file from InputStream resource [resource loaded through InputStream] 2020-09-16 09:54:35,551 WARN [localhost-startStop-1] support.XmlWebApplicationContext:551 : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'ldapSource' defined in class path resource [kylinSecurity.xml]: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.; nested exception is java.lang.RuntimeException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption. 2020-09-16 09:54:35,553 ERROR [localhost-startStop-1] context.ContextLoader:350 : Context initialization failed org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'ldapSource' defined in class path resource [kylinSecurity.xml]: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.; nested exception is java.lang.RuntimeException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption. at org.springframework.beans.factory.config.PlaceholderConfigurerSupport.doProcessProperties(PlaceholderConfigurerSupport.java:223) at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.processProperties(PropertyPlaceholderConfigurer.java:222) at org.springframework.beans.factory.config.PropertyResourceConfigurer.postProcessBeanFactory(PropertyResourceConfigurer.java:86) at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:283) at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:163) at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:687) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:525) at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:443) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:325) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:107) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4792) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5256) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:754) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:730) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:985) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.RuntimeException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption. at org.apache.kylin.common.util.EncryptUtil.decrypt(EncryptUtil.java:65) at org.apache.kylin.rest.security.PasswordPlaceholderConfigurer.resolvePlaceholder(PasswordPlaceholderConfigurer.java:70) at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.resolvePlaceholder(PropertyPlaceholderConfigurer.java:162) at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer$PropertyPlaceholderConfigurerResolver.resolvePlaceholder(PropertyPlaceholderConfigurer.java:277) at org.springframework.util.PropertyPlaceholderHelper.parseStringValue(PropertyPlaceholderHelper.java:147) at org.springframework.util.PropertyPlaceholderHelper.replacePlaceholders(PropertyPlaceholderHelper.java:126) at
[jira] [Comment Edited] (KYLIN-4776) Release Kylin v3.1.1
[ https://issues.apache.org/jira/browse/KYLIN-4776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17202758#comment-17202758 ] Yaqian Zhang edited comment on KYLIN-4776 at 10/12/20, 3:54 AM: ||Issue ID||Verified？||Documentation updated?||Others|| |KYLIN-4756|Yes|No need|No| |KYLIN-4755|Yes|No need|No| |KYLIN-4716|Yes|No need|No| |KYLIN-4714|Yes|No need|No| |KYLIN-4578|Yes|No need|No| |KYLIN-4561|Yes|No need|No| |KYLIN-4560|Yes|No need|No| |KYLIN-4559|Yes|No need|No| |KYLIN-4558|Yes|No need|No| |KYLIN-4557|No need|No need|Code Optimize| |KYLIN-4527|Yes|No need|No| |KYLIN-4551|Yes|No need|Bug have been fixed| |KYLIN-4526|Yes|No need|No| |KYLIN-4683|Yes|No need|No| |KYLIN-4672|Yes|Yes|Document update| |KYLIN-4689|No|No need|There is some bugs| was (Author: zhangyaqian): ||Issue ID||Verified？||Documentation updated?||Others|| |KYLIN-4756|Yes|No need|No| |KYLIN-4755|Yes|No need|No| |KYLIN-4716|Yes|No need|No| |KYLIN-4714|Yes|No need|No| |KYLIN-4578|Yes|No need|No| |KYLIN-4561|Yes|No need|No| |KYLIN-4560|Yes|No need|No| |KYLIN-4559|Yes|No need|No| |KYLIN-4558|Yes|No need|No| |KYLIN-4557|No need|No need|Code Optimize| |KYLIN-4527|Yes|No need|No| |KYLIN-4551|Yes|No need|Bug have been fixed| |KYLIN-4526|Yes|No need|No| |KYLIN-4683|Yes|No need|No| |KYLIN-4672|Yes|Yes|Document update| > Release Kylin v3.1.1 > > > Key: KYLIN-4776 > URL: https://issues.apache.org/jira/browse/KYLIN-4776 > Project: Kylin > Issue Type: Test > Components: Release >Affects Versions: v3.1.0 >Reporter: Xiaoxiang Yu >Assignee: Xiaoxiang Yu >Priority: Critical > Original Estimate: 336h > Remaining Estimate: 336h > > h2. Release Plan for Kylin v3.1.1 > > ||Key||Content|| > |Release Manager|Xiaoxiang Yu| > |Voting Date|2020/10/15| > > > h3. Issue List > [https://issues.apache.org/jira/projects/KYLIN/versions/12348354] > h3. Issue Verification Assignee > # Go to [https://issues.apache.org/jira/issues/?jql=] and input JQL, and you > will know the issue that you need to verify. > # After issue verified, please add a comment, in this comment, provided a > table to show result of each issue. Ask help from RM if faced any trouble. > ||Assignee ||Issue||Count|| > |Zhichao Zhang|project = 12316121 AND fixVersion = 12348354 and (assignee = > tianhui5 OR assignee = xxyu )|9| > |Yaqian Zhang|project = 12316121 AND fixVersion = 12348354 and (assignee = > gxcheng )|13| > |Rupeng Wang|project = 12316121 AND fixVersion = 12348354 and (assignee = > itzhangqiang or assignee = zhangyaqian or assignee = zhangzc and assignee = > julianpan )|10| > |Xiaoxiang Yu|project = 12316121 AND fixVersion = 12348354 and (assignee = > xiaoge )|14| > > h3. Hadoop3 patch PR > - Patch : [https://github.com/apache/kylin/pull/1434] > - Verifcation at CDH 6.3: > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-4720) support htable read quota
[ https://issues.apache.org/jira/browse/KYLIN-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17212088#comment-17212088 ] fengpod commented on KYLIN-4720: We use it in our production env， and it's value setted to 1。It works well。When QPS on table over this limit，will throw QuotaExceededException。But in the past two years，we have only meet this exception only once。 > support htable read quota > - > > Key: KYLIN-4720 > URL: https://issues.apache.org/jira/browse/KYLIN-4720 > Project: Kylin > Issue Type: Improvement > Components: Storage - HBase >Affects Versions: v3.1.0 >Reporter: fengpod >Assignee: fengpod >Priority: Minor > Fix For: v3.1.2 > > > In order to avoid the pressure of massive queries on hbase，htable read quota > is necessary。Through a new configuration “kylin.hbase.htable-quota”，we can > control the read quota when the htable created。The default value of this conf > is -1，means will not limit queries。You can set it to any intger greater than > 0 as needed。 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (KYLIN-4720) support htable read quota
[ https://issues.apache.org/jira/browse/KYLIN-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fengpod reassigned KYLIN-4720: -- Assignee: Xiaoxiang Yu (was: fengpod) > support htable read quota > - > > Key: KYLIN-4720 > URL: https://issues.apache.org/jira/browse/KYLIN-4720 > Project: Kylin > Issue Type: Improvement > Components: Storage - HBase >Affects Versions: v3.1.0 >Reporter: fengpod >Assignee: Xiaoxiang Yu >Priority: Minor > Fix For: v3.1.2 > > > In order to avoid the pressure of massive queries on hbase，htable read quota > is necessary。Through a new configuration “kylin.hbase.htable-quota”，we can > control the read quota when the htable created。The default value of this conf > is -1，means will not limit queries。You can set it to any intger greater than > 0 as needed。 -- This message was sent by Atlassian Jira (v8.3.4#803005)
