[GitHub] [kylin] hit-lacus merged pull request #1373: KYLIN-4716 Optimize the project page
hit-lacus merged pull request #1373: URL: https://github.com/apache/kylin/pull/1373 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (KYLIN-4716) Optimize the project page
[ https://issues.apache.org/jira/browse/KYLIN-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192578#comment-17192578 ] ASF subversion and git services commented on KYLIN-4716: Commit f6278faa24bedc4c6df0050bd518f417baa055ab in kylin's branch refs/heads/master from Guangxu Cheng [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=f6278fa ] KYLIN-4716 Optimize the project page > Optimize the project page > - > > Key: KYLIN-4716 > URL: https://issues.apache.org/jira/browse/KYLIN-4716 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v3.1.0 >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Attachments: image-2020-08-25-11-26-34-031.png > > > # Now only click the project name field to display the details, which is very > inconvenient. After this patch, click any field in this row to display > details. > # Remove the # from #cubes field > !image-2020-08-25-11-26-34-031.png|width=1236,height=76! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-4716) Optimize the project page
[ https://issues.apache.org/jira/browse/KYLIN-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192575#comment-17192575 ] ASF GitHub Bot commented on KYLIN-4716: --- hit-lacus commented on pull request #1373: URL: https://github.com/apache/kylin/pull/1373#issuecomment-689260518 This LGTM, thank you @guangxuCheng . 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Optimize the project page > - > > Key: KYLIN-4716 > URL: https://issues.apache.org/jira/browse/KYLIN-4716 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v3.1.0 >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Attachments: image-2020-08-25-11-26-34-031.png > > > # Now only click the project name field to display the details, which is very > inconvenient. After this patch, click any field in this row to display > details. > # Remove the # from #cubes field > !image-2020-08-25-11-26-34-031.png|width=1236,height=76! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [kylin] hit-lacus commented on pull request #1373: KYLIN-4716 Optimize the project page
hit-lacus commented on pull request #1373: URL: https://github.com/apache/kylin/pull/1373#issuecomment-689260518 This LGTM, thank you @guangxuCheng . 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (KYLIN-4716) Optimize the project page
[ https://issues.apache.org/jira/browse/KYLIN-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192576#comment-17192576 ] ASF GitHub Bot commented on KYLIN-4716: --- hit-lacus merged pull request #1373: URL: https://github.com/apache/kylin/pull/1373 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Optimize the project page > - > > Key: KYLIN-4716 > URL: https://issues.apache.org/jira/browse/KYLIN-4716 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v3.1.0 >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Attachments: image-2020-08-25-11-26-34-031.png > > > # Now only click the project name field to display the details, which is very > inconvenient. After this patch, click any field in this row to display > details. > # Remove the # from #cubes field > !image-2020-08-25-11-26-34-031.png|width=1236,height=76! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KYLIN-4751) Throws NPE when run test case TestTopNUDAF
Zhichao Zhang created KYLIN-4751: - Summary: Throws NPE when run test case TestTopNUDAF Key: KYLIN-4751 URL: https://issues.apache.org/jira/browse/KYLIN-4751 Project: Kylin Issue Type: Bug Components: Spark Engine Affects Versions: v4.0.0-alpha Reporter: Zhichao Zhang Assignee: Zhichao Zhang Fix For: v4.0.0-beta When run test case 'TestTopNUDAF' it will throw NPE. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-3359) Support sum(expression) if possible
[
https://issues.apache.org/jira/browse/KYLIN-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192550#comment-17192550
]
mzz commented on KYLIN-3359:
[~yaho]
The problem is solved. Thank you.
> Support sum(expression) if possible
> ---
>
> Key: KYLIN-3359
> URL: https://issues.apache.org/jira/browse/KYLIN-3359
> Project: Kylin
> Issue Type: Sub-task
> Components: Query Engine
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
> Fix For: v2.4.0
>
> Attachments: KYLIN-3359-Hive-query.png, KYLIN-3359-Kylin-query.png
>
>
> The expression can be as follows:
> # a ~1~*col ~1~ + a ~2~*col ~2~ + ... + a ~n~*col ~n~ + b, if sum(col
> ~1~),sum(col ~2~),...sum(col ~n~) are defined
> # case when {{filter}} ~1~ then expr ~1~
> when {{filter}} ~2~ then expr ~2~
> ...
> else expr ~N~
> end, if {{filter}} ~1~,{{filter}} ~2~, ... {{filter}} ~N-1~, and expr
> ~1~,expr ~2~,...expr ~N~ are supported
> There's a constraint for the filter. That is it's able to push down the
> related filters in case when.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KYLIN-3359) Support sum(expression) if possible
[
https://issues.apache.org/jira/browse/KYLIN-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192525#comment-17192525
]
Zhong Yanghong commented on KYLIN-3359:
---
Hi [~mzz_q], did you set *kylin.query.enable-dynamic-column* to be true at
project level.
> Support sum(expression) if possible
> ---
>
> Key: KYLIN-3359
> URL: https://issues.apache.org/jira/browse/KYLIN-3359
> Project: Kylin
> Issue Type: Sub-task
> Components: Query Engine
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
> Fix For: v2.4.0
>
> Attachments: KYLIN-3359-Hive-query.png, KYLIN-3359-Kylin-query.png
>
>
> The expression can be as follows:
> # a ~1~*col ~1~ + a ~2~*col ~2~ + ... + a ~n~*col ~n~ + b, if sum(col
> ~1~),sum(col ~2~),...sum(col ~n~) are defined
> # case when {{filter}} ~1~ then expr ~1~
> when {{filter}} ~2~ then expr ~2~
> ...
> else expr ~N~
> end, if {{filter}} ~1~,{{filter}} ~2~, ... {{filter}} ~N-1~, and expr
> ~1~,expr ~2~,...expr ~N~ are supported
> There's a constraint for the filter. That is it's able to push down the
> related filters in case when.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KYLIN-3359) Support sum(expression) if possible
[
https://issues.apache.org/jira/browse/KYLIN-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192170#comment-17192170
]
mzz commented on KYLIN-3359:
Hi [~yaho],
thx for your reply, i set *kylin.query.is-null-as-zero-in-expression *to be
true at project level and system level , and restart kylin, but it always
report this error.
> Support sum(expression) if possible
> ---
>
> Key: KYLIN-3359
> URL: https://issues.apache.org/jira/browse/KYLIN-3359
> Project: Kylin
> Issue Type: Sub-task
> Components: Query Engine
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
> Fix For: v2.4.0
>
> Attachments: KYLIN-3359-Hive-query.png, KYLIN-3359-Kylin-query.png
>
>
> The expression can be as follows:
> # a ~1~*col ~1~ + a ~2~*col ~2~ + ... + a ~n~*col ~n~ + b, if sum(col
> ~1~),sum(col ~2~),...sum(col ~n~) are defined
> # case when {{filter}} ~1~ then expr ~1~
> when {{filter}} ~2~ then expr ~2~
> ...
> else expr ~N~
> end, if {{filter}} ~1~,{{filter}} ~2~, ... {{filter}} ~N-1~, and expr
> ~1~,expr ~2~,...expr ~N~ are supported
> There's a constraint for the filter. That is it's able to push down the
> related filters in case when.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KYLIN-4620) sum(expression) support should be limited since it's not conform the associative law of addition in standard sql
[
https://issues.apache.org/jira/browse/KYLIN-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhong Yanghong updated KYLIN-4620:
--
Description:
In standard sql, there's an edge case for the calculation of expression for a
single row. For example,
{code:java}
${col1} + ${col2}
{code}
if ${col1} or ${col2} is null, the result of this expression should be null.
Therefore, the sum aggregation function does not conform the associative law of
addition. That is
{code:java}
sum(col1) + sum(col2) != sum(col1 + col2)
{code}
To support sum(col1 + col2), we have to predefine the it if null values may
exist for the related columns.
If you want to enable sum(expression) with regarding null as 0, you need to set
*kylin.query.is-null-as-zero-in-expression* to be true at project level
was:
In standard sql, there's an edge case for the calculation of expression for a
single row. For example,
{code:java}
${col1} + ${col2}
{code}
if ${col1} or ${col2} is null, the result of this expression should be null.
Therefore, the sum aggregation function does not conform the associative law of
addition. That is
{code:java}
sum(col1) + sum(col2) != sum(col1 + col2)
{code}
To support sum(col1 + col2), we have to predefine the it if null values may
exist for the related columns.
If you want to enable sum(expression) with regarding null as 0, you need to set
kylin.query.is-null-as-zero-in-expression to be true at project level
> sum(expression) support should be limited since it's not conform the
> associative law of addition in standard sql
>
>
> Key: KYLIN-4620
> URL: https://issues.apache.org/jira/browse/KYLIN-4620
> Project: Kylin
> Issue Type: Improvement
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
>
> In standard sql, there's an edge case for the calculation of expression for a
> single row. For example,
> {code:java}
> ${col1} + ${col2}
> {code}
> if ${col1} or ${col2} is null, the result of this expression should be null.
> Therefore, the sum aggregation function does not conform the associative law
> of addition. That is
> {code:java}
> sum(col1) + sum(col2) != sum(col1 + col2)
> {code}
>
> To support sum(col1 + col2), we have to predefine the it if null values may
> exist for the related columns.
> If you want to enable sum(expression) with regarding null as 0, you need to
> set *kylin.query.is-null-as-zero-in-expression* to be true at project level
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KYLIN-4620) sum(expression) support should be limited since it's not conform the associative law of addition in standard sql
[
https://issues.apache.org/jira/browse/KYLIN-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhong Yanghong updated KYLIN-4620:
--
Description:
In standard sql, there's an edge case for the calculation of expression for a
single row. For example,
{code:java}
${col1} + ${col2}
{code}
if ${col1} or ${col2} is null, the result of this expression should be null.
Therefore, the sum aggregation function does not conform the associative law of
addition. That is
{code:java}
sum(col1) + sum(col2) != sum(col1 + col2)
{code}
To support sum(col1 + col2), we have to predefine the it if null values may
exist for the related columns.
If you want to enable sum(expression) with regarding null as 0, you need to set
kylin.query.is-null-as-zero-in-expression to be true at project level
was:
In standard sql, there's an edge case for the calculation of expression for a
single row. For example,
{code:java}
${col1} + ${col2}
{code}
if ${col1} or ${col2} is null, the result of this expression should be null.
Therefore, the sum aggregation function does not conform the associative law of
addition. That is
{code:java}
sum(col1) + sum(col2) != sum(col1 + col2)
{code}
To support sum(col1 + col2), we have to predefine the it if null values may
exist for the related columns.
> sum(expression) support should be limited since it's not conform the
> associative law of addition in standard sql
>
>
> Key: KYLIN-4620
> URL: https://issues.apache.org/jira/browse/KYLIN-4620
> Project: Kylin
> Issue Type: Improvement
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
>
> In standard sql, there's an edge case for the calculation of expression for a
> single row. For example,
> {code:java}
> ${col1} + ${col2}
> {code}
> if ${col1} or ${col2} is null, the result of this expression should be null.
> Therefore, the sum aggregation function does not conform the associative law
> of addition. That is
> {code:java}
> sum(col1) + sum(col2) != sum(col1 + col2)
> {code}
>
> To support sum(col1 + col2), we have to predefine the it if null values may
> exist for the related columns.
> If you want to enable sum(expression) with regarding null as 0, you need to
> set kylin.query.is-null-as-zero-in-expression to be true at project level
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KYLIN-4654) new metadata read/write and reload mechanism
[ https://issues.apache.org/jira/browse/KYLIN-4654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192166#comment-17192166 ] chuxiao commented on KYLIN-4654: 更新方案，重新设计更新实体操作。 针对一般实体的更新，先更新存储再让缓存可读。 单个服务进程，先更新存储，成功了再更新缓存。潜在的风险，是后更新缓存的被前置更新的覆盖。对表，model，cube来说，更新存储和更新缓存的操作必须加锁。 多个服务进程，收到实体更新通知，为避免潜在的多个并发“读存储-写map”的顺序和服务自身的“写存储-写map”的不一致，必须加锁，加锁的最小单位是资源本身。 instance对象当reload会new新的，所以更新存储和缓存时，应该跳出实例，对资源的唯一路径加锁。 对于new实体操作，并发只允许一个保存成功。 udpate实体操作，单一操作要么全部成功要么全部失败。如果直接在旧instace上更新，可能会保存另一个更新操作的一半变更。要么更新实例属性时就加资源路径锁，要么clone实例更新，更新成功后再更新map映射。 前者的风险是更新属性后可能还有一堆其他逻辑，当后续逻辑要更新其他实体时有死锁风险。后者在同一个服务内更容易更新失败，如果要提高操作成功率需要reload重新更新cas更多次，并且对于实体整体的更新无法reload。并发操作是少见的，个人倾向cas。 再加上通过haproxy请求多个服务进程的场景，有2点需要注意。1.可能并发有冲突cas失败，进程内的锁不管用。全局锁，或者cas失败操作失败，或者cas失败了reload重试cas。2.连续操作时前置操作返回成功了，新操作请求的服务进程还没更新对应的缓存，可能找不到元数据。 考虑实际场景，单个表，model，cube自身的并发创建/更新，一般只出现于同一个请求连续发了多次，并发创建/更新只成功一个影响并不大。所以实现可以clone/reload/new的基础上修改，再cas，失败就直接操作失败。 对于prj更新table/model/cube/其他属性，如果要允许并发，需要拆project元数据为多个。如果保持现在的prj整体为最小粒度，在并发时必然有冲突。对更新其他属性，直接失败没问题。但更新prj的子元素列表失败，因为已经保存子元素了，直接操作失败会留有子元素的脏数据。这本质是同时更新子元素和prj的操作原子性问题。没有事务的存储引擎是无法保证多个更新的原子性的，取舍为reload prj并更新子元素cas，重试几次后还是失败则操作失败。如果真的由于存储引擎问题或并发太高问题产生子元素的脏数据，概率很低，用清理工具删除元数据即可。 再就是更新segment，这个可以采用prj更新子元素相同逻辑来处理，目前应该就是这么做的。 对于连续操作在多个服务进程上的串行，如果发现依赖实体还无缓存，可以尝试主动reload一次依赖实体，依然不存在再报错。如果更新依赖实体再来新建实体，由于缓存还未刷新导致新建实体检查正确性失败，非常规操作，直接失败让客户端重试即可。 对lru2cache，资源缓存换了对象实例，可能会影响lru2cache映射。但考虑还没被引用的才可以直接修改信息，所以收口lru2cache的变化，只有在会影响查询路由的cube变化时再统一更新，其他时候直接读即可。 对于其他读缓存还未更新的场景，直接按读缓存处理，潜在风险目前只想到当依赖实体被删除时基于依赖并发创建实体(例如删除model的同时基于该model并发创建cube)可能出现问题。考虑这是非常规操作，依赖都要删除了还要基于依赖去创建本身也是有问题的，后果是新创建的实体不可用，不影响已有查询和其他实体创建，影响可控，用清理工具删除元数据即可。 > new metadata read/write and reload mechanism > > > Key: KYLIN-4654 > URL: https://issues.apache.org/jira/browse/KYLIN-4654 > Project: Kylin > Issue Type: Improvement >Reporter: chuxiao >Priority: Major > Attachments: 优化方案.docx, 现有代码梳理.docx > > > support when there are 10，000 cube in one cluster one project, and 1000 cubes > continue update，still can create cube and query -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-3359) Support sum(expression) if possible
[
https://issues.apache.org/jira/browse/KYLIN-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192167#comment-17192167
]
Zhong Yanghong commented on KYLIN-3359:
---
Hi [~mzz_q], please see [KYLIN-4620]. If you want to enable sum(expression),
you need to set *kylin.query.is-null-as-zero-in-expression* to be true at
project level
> Support sum(expression) if possible
> ---
>
> Key: KYLIN-3359
> URL: https://issues.apache.org/jira/browse/KYLIN-3359
> Project: Kylin
> Issue Type: Sub-task
> Components: Query Engine
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
> Fix For: v2.4.0
>
> Attachments: KYLIN-3359-Hive-query.png, KYLIN-3359-Kylin-query.png
>
>
> The expression can be as follows:
> # a ~1~*col ~1~ + a ~2~*col ~2~ + ... + a ~n~*col ~n~ + b, if sum(col
> ~1~),sum(col ~2~),...sum(col ~n~) are defined
> # case when {{filter}} ~1~ then expr ~1~
> when {{filter}} ~2~ then expr ~2~
> ...
> else expr ~N~
> end, if {{filter}} ~1~,{{filter}} ~2~, ... {{filter}} ~N-1~, and expr
> ~1~,expr ~2~,...expr ~N~ are supported
> There's a constraint for the filter. That is it's able to push down the
> related filters in case when.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KYLIN-4654) new metadata read/write and reload mechanism
[ https://issues.apache.org/jira/browse/KYLIN-4654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chuxiao updated KYLIN-4654: --- Attachment: 优化方案.docx > new metadata read/write and reload mechanism > > > Key: KYLIN-4654 > URL: https://issues.apache.org/jira/browse/KYLIN-4654 > Project: Kylin > Issue Type: Improvement >Reporter: chuxiao >Priority: Major > Attachments: 优化方案.docx, 现有代码梳理.docx > > > support when there are 10，000 cube in one cluster one project, and 1000 cubes > continue update，still can create cube and query -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KYLIN-4654) new metadata read/write and reload mechanism
[ https://issues.apache.org/jira/browse/KYLIN-4654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chuxiao updated KYLIN-4654: --- Attachment: (was: 优化方案.docx) > new metadata read/write and reload mechanism > > > Key: KYLIN-4654 > URL: https://issues.apache.org/jira/browse/KYLIN-4654 > Project: Kylin > Issue Type: Improvement >Reporter: chuxiao >Priority: Major > Attachments: 优化方案.docx, 现有代码梳理.docx > > > support when there are 10，000 cube in one cluster one project, and 1000 cubes > continue update，still can create cube and query -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-3359) Support sum(expression) if possible
[
https://issues.apache.org/jira/browse/KYLIN-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192148#comment-17192148
]
mzz commented on KYLIN-3359:
Hi [~shaofengshi] [~yaho],
my version is 2.6.6, I create a model and use 'counts' col as a measure,
when I run a query 'SELECT
DT,SUM(COUNTS) FROM VIW.VIW_QM_AGGS_LOG GROUP BY DT', The correct result is
returned.
but ,when run a sum(expression) query...
*sql:*
{code:java}
SELECT
DT,
SUM(COUNTS),
SUM(case
when dt='20200901' then counts
else 0
end) AS S
FROM VIW.VIW_QM_AGGS_LOG
GROUP BY DT
HAVING DT='20200901'
{code}
*it report a error:
*
{code:java}
No realization found for OLAPContext, CUBE_NOT_READY,
CUBE_UNMATCHED_AGGREGATION[FunctionDesc [expression=SUM, parameter=CASE(=($0,
'20200901'), 1, 0), returnType=null]],
rel#3453:OLAPTableScan.OLAP.[](table=[VIW, VIW_QM_AGGS_LOG],ctx=,fields=[0, 1,
2, 3, 4]) while executing SQL: "SELECT DT, SUM(COUNTS), SUM(case when
dt='20200901' then 1 else 0 end) AS S FROM VIW.VIW_QM_AGGS_LOG GROUP BY DT
HAVING DT='20200901' LIMIT 5"
{code}
> Support sum(expression) if possible
> ---
>
> Key: KYLIN-3359
> URL: https://issues.apache.org/jira/browse/KYLIN-3359
> Project: Kylin
> Issue Type: Sub-task
> Components: Query Engine
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
> Fix For: v2.4.0
>
> Attachments: KYLIN-3359-Hive-query.png, KYLIN-3359-Kylin-query.png
>
>
> The expression can be as follows:
> # a ~1~*col ~1~ + a ~2~*col ~2~ + ... + a ~n~*col ~n~ + b, if sum(col
> ~1~),sum(col ~2~),...sum(col ~n~) are defined
> # case when {{filter}} ~1~ then expr ~1~
> when {{filter}} ~2~ then expr ~2~
> ...
> else expr ~N~
> end, if {{filter}} ~1~,{{filter}} ~2~, ... {{filter}} ~N-1~, and expr
> ~1~,expr ~2~,...expr ~N~ are supported
> There's a constraint for the filter. That is it's able to push down the
> related filters in case when.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (KYLIN-4717) Failed to build webapp
[ https://issues.apache.org/jira/browse/KYLIN-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192132#comment-17192132 ] yongjie zhao edited comment on KYLIN-4717 at 9/8/20, 10:49 AM: --- Using updated packages.json file, it still fails to compile in my environment. I guess the front-end part is ["legacy|https://cn.eudic.net/dict/searchword?word=legacy];, so we should use the "[legacy|https://cn.eudic.net/dict/searchword?word=legacy]; version of node and npm to compile the frontend. !image-2020-09-08-18-48-28-298.png|width=476,height=296! was (Author: zog): Using updated packages.json file, it still fails to compile in my environment. I guess the front-end part is ["legacy|https://cn.eudic.net/dict/searchword?word=legacy];, so we should use the "[legacy|https://cn.eudic.net/dict/searchword?word=legacy]; version of node and npm to compile the frontend. !image-2020-09-08-18-48-28-298.png|width=773,height=481! > Failed to build webapp > -- > > Key: KYLIN-4717 > URL: https://issues.apache.org/jira/browse/KYLIN-4717 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v3.1.0 >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Attachments: image-2020-08-25-11-40-49-948.png, > image-2020-09-08-18-48-28-298.png > > > !image-2020-08-25-11-40-49-948.png|width=803,height=301! > OS Platform: macos 10.15.5 (19F101) > node version: 14.8.0 > npm version: 6.14.7 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (KYLIN-4717) Failed to build webapp
[ https://issues.apache.org/jira/browse/KYLIN-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192132#comment-17192132 ] yongjie zhao edited comment on KYLIN-4717 at 9/8/20, 10:48 AM: --- Using updated packages.json file, it still fails to compile in my environment. I guess the front-end part is ["legacy|https://cn.eudic.net/dict/searchword?word=legacy];, so we should use the "[legacy|https://cn.eudic.net/dict/searchword?word=legacy]; version of node and npm to compile the frontend. !image-2020-09-08-18-48-28-298.png! was (Author: zog): Using updated packages.json file, it still fails to compile in my environment. I guess the front-end part is ["legacy|https://cn.eudic.net/dict/searchword?word=legacy];, so we should use the "[legacy|https://cn.eudic.net/dict/searchword?word=legacy]; version of node and npm to compile the frontend. !image-2020-09-08-18-47-12-939.png! > Failed to build webapp > -- > > Key: KYLIN-4717 > URL: https://issues.apache.org/jira/browse/KYLIN-4717 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v3.1.0 >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Attachments: image-2020-08-25-11-40-49-948.png, > image-2020-09-08-18-48-28-298.png > > > !image-2020-08-25-11-40-49-948.png|width=803,height=301! > OS Platform: macos 10.15.5 (19F101) > node version: 14.8.0 > npm version: 6.14.7 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (KYLIN-4717) Failed to build webapp
[ https://issues.apache.org/jira/browse/KYLIN-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192132#comment-17192132 ] yongjie zhao edited comment on KYLIN-4717 at 9/8/20, 10:48 AM: --- Using updated packages.json file, it still fails to compile in my environment. I guess the front-end part is ["legacy|https://cn.eudic.net/dict/searchword?word=legacy];, so we should use the "[legacy|https://cn.eudic.net/dict/searchword?word=legacy]; version of node and npm to compile the frontend. !image-2020-09-08-18-48-28-298.png|width=773,height=481! was (Author: zog): Using updated packages.json file, it still fails to compile in my environment. I guess the front-end part is ["legacy|https://cn.eudic.net/dict/searchword?word=legacy];, so we should use the "[legacy|https://cn.eudic.net/dict/searchword?word=legacy]; version of node and npm to compile the frontend. !image-2020-09-08-18-48-28-298.png! > Failed to build webapp > -- > > Key: KYLIN-4717 > URL: https://issues.apache.org/jira/browse/KYLIN-4717 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v3.1.0 >Reporter: Guangxu Cheng >Assignee: Guangxu Cheng >Priority: Major > Attachments: image-2020-08-25-11-40-49-948.png, > image-2020-09-08-18-48-28-298.png > > > !image-2020-08-25-11-40-49-948.png|width=803,height=301! > OS Platform: macos 10.15.5 (19F101) > node version: 14.8.0 > npm version: 6.14.7 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-4660) Remove duplicated/misleading code or comment
[ https://issues.apache.org/jira/browse/KYLIN-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192119#comment-17192119 ] ASF subversion and git services commented on KYLIN-4660: Commit bc94f4978bc3009a5ad7853c2c6f86c8f2f1c39d in kylin's branch refs/heads/kylin-on-parquet-v2 from Xiaoxiang Yu [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=bc94f49 ] KYLIN-4660 Refine kylin-default.properties > Remove duplicated/misleading code or comment > > > Key: KYLIN-4660 > URL: https://issues.apache.org/jira/browse/KYLIN-4660 > Project: Kylin > Issue Type: Sub-task > Components: Storage - Parquet >Reporter: Xiaoxiang Yu >Assignee: Xiaoxiang Yu >Priority: Major > Fix For: v4.0.0-alpha > > Original Estimate: 672h > Remaining Estimate: 672h > > Source code is located at > [https://github.com/apache/kylin/tree/kylin-on-parquet-v2] , we are still > test and verify it. > > > https://cwiki.apache.org/confluence/display/KYLIN/Kylin+4.X+Feature+List -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-4043) build cube on step 3,ORA-00904: "B0"."CATALOG_NAME": 标识符⽆无效
[
https://issues.apache.org/jira/browse/KYLIN-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192085#comment-17192085
]
han commented on KYLIN-4043:
谢谢张大哥
> build cube on step 3,ORA-00904: "B0"."CATALOG_NAME": 标识符⽆无效
> ---
>
> Key: KYLIN-4043
> URL: https://issues.apache.org/jira/browse/KYLIN-4043
> Project: Kylin
> Issue Type: Bug
> Components: Environment , Metadata
>Affects Versions: v2.6.2
> Environment: operating system:Centos7(four real computer machines)
> Hadoop : 3.1.1(four nodes)
> Hive : 3.1.0
> HBase : 2.0.5(four nodes)
> Kylin : apache-kylin-2.6.2-bin-hadoop3(one node)
>Reporter: fap...@163.com
>Priority: Major
> Attachments: errlog.PNG, step_errors.PNG
>
>
> h2. My hive's metastore on oracle 11g,hive jdbc config is :
> {panel:title=hive jdbc config}
>
> hive.metastore.db.type
> ORACLE
>
> Expects one of [derby, oracle, mysql, mssql, postgres].
> Type of database used by the metastore. Information schema
> JDBCStorageHandler depend on it.
>
>
>
> javax.jdo.option.ConnectionURL
> jdbc:oracle:thin:@192.168.0.2:1521/xxx
> JDBC connect string for a JDBC
> metastore
>
>
> javax.jdo.option.ConnectionDriverName
> oracle.jdbc.OracleDriver
> Driver class name for a JDBC
> metastore
>
>
> javax.jdo.option.ConnectionUserName
> bus_info
> username to use against metastore
> database
>
>
> javax.jdo.option.ConnectionPassword
> here is my passowrd
> password to use against metastore
> database
>
>
> hive.metastore.warehouse.dir
> /user/hive/warehouse
> location of default database for the warehouse
>
> {panel}
> h2. *when building cube on setp 3 , throws a exception is below:*
> {panel:title=exception}
> java.lang.RuntimeException: java.io.IOException:
> MetaException(message:Exception thrown when executing query : SELECT DISTINCT
> 'org.apache.hadoop.hive.metastore.model.MTable' AS
> NUCLEUS_TYPE,A0.CREATE_TIME,A0.LAST_ACCESS_TIME,A0.OWNER,A0.OWNER_TYPE,A0.RETENTION,A0.REWRITE_ENABLED,A0.TBL_NAME,A0.TBL_TYPE,A0.TBL_ID
> FROM TBLS A0 LEFT OUTER JOIN DBS B0 ON A0.DB_ID = B0.DB_ID WHERE A0.TBL_NAME
> = ? AND B0."NAME" = ? AND B0."CATALOG_NAME" = ?)
> at
> org.apache.kylin.source.hive.HiveMRInput$HiveTableInputFormat.configureJob(HiveMRInput.java:83)
> at
> org.apache.kylin.engine.mr.steps.FactDistinctColumnsJob.setupMapper(FactDistinctColumnsJob.java:126)
> at
> org.apache.kylin.engine.mr.steps.FactDistinctColumnsJob.run(FactDistinctColumnsJob.java:104)
> at
> org.apache.kylin.engine.mr.common.MapReduceExecutable.doWork(MapReduceExecutable.java:131)
> at
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:167)
> at
> org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:71)
> at
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:167)
> at
> org.apache.kylin.job.impl.threadpool.DistributedScheduler$JobRunner.run(DistributedScheduler.java:110)
> 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.io.IOException: MetaException(message:Exception thrown when
> executing query : SELECT DISTINCT
> 'org.apache.hadoop.hive.metastore.model.MTable' AS
> NUCLEUS_TYPE,A0.CREATE_TIME,A0.LAST_ACCESS_TIME,A0.OWNER,A0.OWNER_TYPE,A0.RETENTION,A0.REWRITE_ENABLED,A0.TBL_NAME,A0.TBL_TYPE,A0.TBL_ID
> FROM TBLS A0 LEFT OUTER JOIN DBS B0 ON A0.DB_ID = B0.DB_ID WHERE A0.TBL_NAME
> = ? AND B0."NAME" = ? AND B0."CATALOG_NAME" = ?)
> at
> org.apache.hive.hcatalog.mapreduce.HCatInputFormat.setInput(HCatInputFormat.java:97)
> at
> org.apache.hive.hcatalog.mapreduce.HCatInputFormat.setInput(HCatInputFormat.java:51)
> at
> org.apache.kylin.source.hive.HiveMRInput$HiveTableInputFormat.configureJob(HiveMRInput.java:80)
> ... 10 more
> Caused by: MetaException(message:Exception thrown when executing query :
> SELECT DISTINCT 'org.apache.hadoop.hive.metastore.model.MTable' AS
> NUCLEUS_TYPE,A0.CREATE_TIME,A0.LAST_ACCESS_TIME,A0.OWNER,A0.OWNER_TYPE,A0.RETENTION,A0.REWRITE_ENABLED,A0.TBL_NAME,A0.TBL_TYPE,A0.TBL_ID
> FROM TBLS A0 LEFT OUTER JOIN DBS B0 ON A0.DB_ID = B0.DB_ID WHERE A0.TBL_NAME
> = ? AND B0."NAME" = ? AND B0."CATALOG_NAME" = ?)
> at
>
[jira] [Commented] (KYLIN-4545) unable to load HiveMetaStore
[ https://issues.apache.org/jira/browse/KYLIN-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192084#comment-17192084 ] han commented on KYLIN-4545: 于大哥, 我也遇到了一模一样的问题, 也是外部表. 请问上面大哥的问题怎么解决的? 谢谢了. > unable to load HiveMetaStore > > > Key: KYLIN-4545 > URL: https://issues.apache.org/jira/browse/KYLIN-4545 > Project: Kylin > Issue Type: Test > Components: Environment >Affects Versions: v3.0.2 > Environment: hadoop-3.2.0 > hbase-2.2.0 > hive-3.1.0 > kylin-3.0.2-bin-hadoop3 >Reporter: praveenece >Priority: Critical > > We are using the below software to setup kylin environment. > hadoop-3.2.0 > hbase-2.2.0 > hive-3.1.0 > kylin-3.0.2-bin-hadoop3 > After configuring everything getting *message: Caused by: > javax.jdo.JDOException: Exception thrown when executing query : SELECT > `A0`.`NAME` FROM `DBS` `A0` WHERE `A0`.`CATALOG_NAME` = ?* this error message. > i have executed below query against hive Metastore to fix the issues. > USE metastore; >ALTER TABLE TBLS ADD REWRITE_ENABLED BIT(1) NOT NULL; >UPDATE TBLS SET REWRITE_ENABLED=IS_REWRITE_ENABLED; >ALTER TABLE DBS ADD CATALOG_NAME varchar(256) not Null; >UPDATE DBS SET CATALOG_NAME=CTLG_NAME; > After that i am able to see the hive tables in kylin model, but i am not able > to Sync the tables. Getting the "can not get Hive TableMeta" error message. > Please help us to fix the issues ASAP. -- This message was sent by Atlassian Jira (v8.3.4#803005)
