[jira] [Assigned] (KYLIN-3679) Fetch Kafka topic with Spark streaming
[ https://issues.apache.org/jira/browse/KYLIN-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI reassigned KYLIN-3679: --- Assignee: weibin0516 Awesome! [~codingforfun] please go ahead, pull request to Kylin github is welcomed > Fetch Kafka topic with Spark streaming > -- > > Key: KYLIN-3679 > URL: https://issues.apache.org/jira/browse/KYLIN-3679 > Project: Kylin > Issue Type: New Feature > Components: Spark Engine >Reporter: Shaofeng SHI >Assignee: weibin0516 >Priority: Major > > Now Kylin uses a MR job to fetch Kafka messages in parallel and then persist > to HDFS for subsequent processing. If user selects to use Spark engine, we > can use Spark streaming API to do this. Spark streaming can read the Kafka > message in a given offset range as a RDD, then it would be easy to process; > https://spark.apache.org/docs/latest/streaming-kafka-0-10-integration.html > With Spark streaming, Kylin can also easily connect with other data source > like Kinesis, Flume, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-4061) Swap inner join's left side, right side table will get different result when query
[
https://issues.apache.org/jira/browse/KYLIN-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
weibin0516 updated KYLIN-4061:
--
Description:
When the left side table of inner join is a fact table and the right side table
is a lookup table, will query cube and get correct result. Sql is as follows.
{code:java}
SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE),
COUNT(KYLIN_ACCOUNT.ACCOUNT_ID)
FROM KYLIN_SALES
INNER JOIN KYLIN_ACCOUNT ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID
WHERE KYLIN_SALES.LSTG_SITE_ID != 1000
GROUP BY KYLIN_SALES.TRANS_ID
ORDER BY TRANS_ID
LIMIT 10;{code}
However，when swap the left and right side tables of the inner join will failed
due to no realization found. Sql is as follows.
{code:java}
SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE),
COUNT(KYLIN_ACCOUNT.ACCOUNT_ID)
FROM KYLIN_ACCOUNT
INNER JOIN KYLIN_SALES ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID
WHERE KYLIN_SALES.LSTG_SITE_ID != 1000
GROUP BY KYLIN_SALES.TRANS_ID
ORDER BY TRANS_ID
LIMIT 10;{code}
We know that the above two sql semantics are consistent and should return the
same result.
I looked at the source code, kylin will use context.firstTableScan(assigned in
OLAPTableScan.implementOLAP) as the fact table, whether it is or not. The fact
table will be the key evidence for choosing realization later. So, in the
second sql Regard a lookup table as a fact table can not find corresponding
realization.
Is this a bug, do we need to fix it?
was:
When the left side table of inner join is a fact table and the right side table
is a lookup table, will query cube and get correct result. Sql is as follows.
{code:java}
SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE),
COUNT(KYLIN_ACCOUNT.ACCOUNT_ID)
FROM KYLIN_SALES
INNER JOIN KYLIN_ACCOUNT ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID
WHERE KYLIN_SALES.LSTG_SITE_ID != 1000
GROUP BY KYLIN_SALES.TRANS_ID
ORDER BY TRANS_ID
LIMIT 10;{code}
However，when swap the left and right side tables of the inner join will failed
due to no realization found. Sql is as follows.
{code:java}
SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE),
COUNT(KYLIN_ACCOUNT.ACCOUNT_ID)
FROM KYLIN_ACCOUNT
INNER JOIN KYLIN_SALES ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID
WHERE KYLIN_SALES.LSTG_SITE_ID != 1000
GROUP BY KYLIN_SALES.TRANS_ID
ORDER BY TRANS_ID
LIMIT 10;{code}
We know that the above two sql semantics are consistent and should return the
same result.
I looked at the source code, kylin will use context.firstTableScan(assigned in
OLAPTableScan.implementOLAP) as the fact table, whether it is or not.
Is this a bug, do we need to fix it?
> Swap inner join's left side, right side table will get different result when
> query
> --
>
> Key: KYLIN-4061
> URL: https://issues.apache.org/jira/browse/KYLIN-4061
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Affects Versions: v2.5.2
>Reporter: weibin0516
>Priority: Major
> Attachments: failed.png, succeed.png
>
>
> When the left side table of inner join is a fact table and the right side
> table is a lookup table, will query cube and get correct result. Sql is as
> follows.
> {code:java}
> SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE),
> COUNT(KYLIN_ACCOUNT.ACCOUNT_ID)
> FROM KYLIN_SALES
> INNER JOIN KYLIN_ACCOUNT ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID
> WHERE KYLIN_SALES.LSTG_SITE_ID != 1000
> GROUP BY KYLIN_SALES.TRANS_ID
> ORDER BY TRANS_ID
> LIMIT 10;{code}
>
> However，when swap the left and right side tables of the inner join will
> failed due to no realization found. Sql is as follows.
> {code:java}
> SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE),
> COUNT(KYLIN_ACCOUNT.ACCOUNT_ID)
> FROM KYLIN_ACCOUNT
> INNER JOIN KYLIN_SALES ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID
> WHERE KYLIN_SALES.LSTG_SITE_ID != 1000
> GROUP BY KYLIN_SALES.TRANS_ID
> ORDER BY TRANS_ID
> LIMIT 10;{code}
> We know that the above two sql semantics are consistent and should return the
> same result.
> I looked at the source code, kylin will use context.firstTableScan(assigned
> in OLAPTableScan.implementOLAP) as the fact table, whether it is or not. The
> fact table will be the key evidence for choosing realization later. So, in
> the second sql Regard a lookup table as a fact table can not find
> corresponding realization.
> Is this a bug, do we need to fix it?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KYLIN-4061) Swap inner join's left side, right side table will get different result when query
[
https://issues.apache.org/jira/browse/KYLIN-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
weibin0516 updated KYLIN-4061:
--
Description:
When the left side table of inner join is a fact table and the right side table
is a lookup table, will query cube and get correct result. Sql is as follows.
{code:java}
SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE),
COUNT(KYLIN_ACCOUNT.ACCOUNT_ID)
FROM KYLIN_SALES
INNER JOIN KYLIN_ACCOUNT ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID
WHERE KYLIN_SALES.LSTG_SITE_ID != 1000
GROUP BY KYLIN_SALES.TRANS_ID
ORDER BY TRANS_ID
LIMIT 10;{code}
However，when swap the left and right side tables of the inner join will failed
due to no realization found. Sql is as follows.
{code:java}
SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE),
COUNT(KYLIN_ACCOUNT.ACCOUNT_ID)
FROM KYLIN_ACCOUNT
INNER JOIN KYLIN_SALES ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID
WHERE KYLIN_SALES.LSTG_SITE_ID != 1000
GROUP BY KYLIN_SALES.TRANS_ID
ORDER BY TRANS_ID
LIMIT 10;{code}
We know that the above two sql semantics are consistent and should return the
same result.
I looked at the source code, kylin will use context.firstTableScan(assigned in
OLAPTableScan.implementOLAP) as the fact table, whether it is or not.
Is this a bug, do we need to fix it?
was:
When the left side table of inner join is a fact table and the right side table
is a lookup table, will query cube and get correct result. Sql is as follows.
```
SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE),
COUNT(KYLIN_ACCOUNT.ACCOUNT_ID)
FROM KYLIN_SALES
INNER JOIN KYLIN_ACCOUNT ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID
WHERE KYLIN_SALES.LSTG_SITE_ID != 1000
GROUP BY KYLIN_SALES.TRANS_ID
ORDER BY TRANS_ID
LIMIT 10;
```
However，when swap the left and right side tables of the inner join will failed
due to no realization found. Sql is as follows.
```
SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE),
COUNT(KYLIN_ACCOUNT.ACCOUNT_ID)
FROM KYLIN_ACCOUNT
INNER JOIN KYLIN_SALES ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID
WHERE KYLIN_SALES.LSTG_SITE_ID != 1000
GROUP BY KYLIN_SALES.TRANS_ID
ORDER BY TRANS_ID
LIMIT 10;
```
We know that the above two sql semantics are consistent and should return the
same result.
I looked at the source code, kylin will use context.firstTableScan(assigned in
OLAPTableScan.implementOLAP) as the fact table, whether it is or not.
Is this a bug, do we need to fix it?
> Swap inner join's left side, right side table will get different result when
> query
> --
>
> Key: KYLIN-4061
> URL: https://issues.apache.org/jira/browse/KYLIN-4061
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Affects Versions: v2.5.2
>Reporter: weibin0516
>Priority: Major
> Attachments: failed.png, succeed.png
>
>
> When the left side table of inner join is a fact table and the right side
> table is a lookup table, will query cube and get correct result. Sql is as
> follows.
> {code:java}
> SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE),
> COUNT(KYLIN_ACCOUNT.ACCOUNT_ID)
> FROM KYLIN_SALES
> INNER JOIN KYLIN_ACCOUNT ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID
> WHERE KYLIN_SALES.LSTG_SITE_ID != 1000
> GROUP BY KYLIN_SALES.TRANS_ID
> ORDER BY TRANS_ID
> LIMIT 10;{code}
>
> However，when swap the left and right side tables of the inner join will
> failed due to no realization found. Sql is as follows.
> {code:java}
> SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE),
> COUNT(KYLIN_ACCOUNT.ACCOUNT_ID)
> FROM KYLIN_ACCOUNT
> INNER JOIN KYLIN_SALES ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID
> WHERE KYLIN_SALES.LSTG_SITE_ID != 1000
> GROUP BY KYLIN_SALES.TRANS_ID
> ORDER BY TRANS_ID
> LIMIT 10;{code}
> We know that the above two sql semantics are consistent and should return the
> same result.
> I looked at the source code, kylin will use context.firstTableScan(assigned
> in OLAPTableScan.implementOLAP) as the fact table, whether it is or not.
> Is this a bug, do we need to fix it?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KYLIN-4061) Swap inner join's left side, right side table will get different result when query
[ https://issues.apache.org/jira/browse/KYLIN-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] weibin0516 updated KYLIN-4061: -- Attachment: succeed.png failed.png > Swap inner join's left side, right side table will get different result when > query > -- > > Key: KYLIN-4061 > URL: https://issues.apache.org/jira/browse/KYLIN-4061 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.5.2 >Reporter: weibin0516 >Priority: Major > Attachments: failed.png, succeed.png > > > When the left side table of inner join is a fact table and the right side > table is a lookup table, will query cube and get correct result. Sql is as > follows. > ``` > SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE), > COUNT(KYLIN_ACCOUNT.ACCOUNT_ID) > FROM KYLIN_SALES > INNER JOIN KYLIN_ACCOUNT ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID > WHERE KYLIN_SALES.LSTG_SITE_ID != 1000 > GROUP BY KYLIN_SALES.TRANS_ID > ORDER BY TRANS_ID > LIMIT 10; > ``` > > However，when swap the left and right side tables of the inner join will > failed due to no realization found. Sql is as follows. > ``` > SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE), > COUNT(KYLIN_ACCOUNT.ACCOUNT_ID) > FROM KYLIN_ACCOUNT > INNER JOIN KYLIN_SALES ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID > WHERE KYLIN_SALES.LSTG_SITE_ID != 1000 > GROUP BY KYLIN_SALES.TRANS_ID > ORDER BY TRANS_ID > LIMIT 10; > ``` > We know that the above two sql semantics are consistent and should return the > same result. > I looked at the source code, kylin will use context.firstTableScan(assigned > in OLAPTableScan.implementOLAP) as the fact table, whether it is or not. > Is this a bug, do we need to fix it? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-4061) Swap inner join's left side, right side table will get different result when query
weibin0516 created KYLIN-4061: - Summary: Swap inner join's left side, right side table will get different result when query Key: KYLIN-4061 URL: https://issues.apache.org/jira/browse/KYLIN-4061 Project: Kylin Issue Type: Bug Components: Query Engine Affects Versions: v2.5.2 Reporter: weibin0516 When the left side table of inner join is a fact table and the right side table is a lookup table, will query cube and get correct result. Sql is as follows. ``` SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE), COUNT(KYLIN_ACCOUNT.ACCOUNT_ID) FROM KYLIN_SALES INNER JOIN KYLIN_ACCOUNT ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID WHERE KYLIN_SALES.LSTG_SITE_ID != 1000 GROUP BY KYLIN_SALES.TRANS_ID ORDER BY TRANS_ID LIMIT 10; ``` However，when swap the left and right side tables of the inner join will failed due to no realization found. Sql is as follows. ``` SELECT KYLIN_SALES.TRANS_ID, SUM(KYLIN_SALES.PRICE), COUNT(KYLIN_ACCOUNT.ACCOUNT_ID) FROM KYLIN_ACCOUNT INNER JOIN KYLIN_SALES ON KYLIN_SALES.BUYER_ID = KYLIN_ACCOUNT.ACCOUNT_ID WHERE KYLIN_SALES.LSTG_SITE_ID != 1000 GROUP BY KYLIN_SALES.TRANS_ID ORDER BY TRANS_ID LIMIT 10; ``` We know that the above two sql semantics are consistent and should return the same result. I looked at the source code, kylin will use context.firstTableScan(assigned in OLAPTableScan.implementOLAP) as the fact table, whether it is or not. Is this a bug, do we need to fix it? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [kylin] coveralls commented on issue #721: [KYLIN-2517] Upgrade Apache Hbase version to 1.4.7
coveralls commented on issue #721: [KYLIN-2517] Upgrade Apache Hbase version to 1.4.7 URL: https://github.com/apache/kylin/pull/721#issuecomment-506954726 ## Pull Request Test Coverage Report for [Build 4681](https://coveralls.io/builds/24280148) * **0** of **0** changed or added relevant lines in **0** files are covered. * **2** unchanged lines in **2** files lost coverage. * Overall coverage decreased (**-0.002%**) to **28.183%** --- | Files with Coverage Reduction | New Missed Lines | % | | :-|--|--: | | [core-cube/src/main/java/org/apache/kylin/cube/inmemcubing/MemDiskStore.java](https://coveralls.io/builds/24280148/source?filename=core-cube%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Fcube%2Finmemcubing%2FMemDiskStore.java#L553) | 1 | 78.12% | | [core-dictionary/src/main/java/org/apache/kylin/dict/lookup/cache/RocksDBLookupTable.java](https://coveralls.io/builds/24280148/source?filename=core-dictionary%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Fdict%2Flookup%2Fcache%2FRocksDBLookupTable.java#L62) | 1 | 81.08% | | Totals | [](https://coveralls.io/builds/24280148) | | :-- | --: | | Change from base [Build 4677](https://coveralls.io/builds/24277319): | -0.002% | | Covered Lines: | 23255 | | Relevant Lines: | 82513 | --- # - [Coveralls](https://coveralls.io) 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 With regards, Apache Git Services
[jira] [Commented] (KYLIN-3679) Fetch Kafka topic with Spark streaming
[ https://issues.apache.org/jira/browse/KYLIN-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875486#comment-16875486 ] weibin0516 commented on KYLIN-3679: --- Hi, [~Shaofengshi], i hope to implement this feature, please assign it to me. Thanks~ > Fetch Kafka topic with Spark streaming > -- > > Key: KYLIN-3679 > URL: https://issues.apache.org/jira/browse/KYLIN-3679 > Project: Kylin > Issue Type: New Feature > Components: Spark Engine >Reporter: Shaofeng SHI >Priority: Major > > Now Kylin uses a MR job to fetch Kafka messages in parallel and then persist > to HDFS for subsequent processing. If user selects to use Spark engine, we > can use Spark streaming API to do this. Spark streaming can read the Kafka > message in a given offset range as a RDD, then it would be easy to process; > https://spark.apache.org/docs/latest/streaming-kafka-0-10-integration.html > With Spark streaming, Kylin can also easily connect with other data source > like Kinesis, Flume, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (KYLIN-3832) Kylin Pushdown query not support postgresql
[ https://issues.apache.org/jira/browse/KYLIN-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] weibin0516 updated KYLIN-3832: -- Comment: was deleted (was: I'd like to implement the postgresql data source adapter. Please assign to me.) > Kylin Pushdown query not support postgresql > --- > > Key: KYLIN-3832 > URL: https://issues.apache.org/jira/browse/KYLIN-3832 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.5.2 >Reporter: hailin.huang >Priority: Major > Fix For: Future > > > when I run pushdown to postgresql in my env, I encount the below exception. > it seems that kylin need support more JDBC Driver, > PushDownRunnerJdbcImpl.class should be more general. > 2019-02-26 16:12:53,168 ERROR [Query 207dcf77-7c14-8078-ea8b-79644a0c576d-48] > service.QueryService:989 : pushdown engine failed current query too > java.sql.SQLException: Unrecognized column type: int8 > at > org.apache.kylin.query.adhoc.PushDownRunnerJdbcImpl.toSqlType(PushDownRunnerJdbcImpl.java:260) > at > org.apache.kylin.query.adhoc.PushDownRunnerJdbcImpl.extractColumnMeta(PushDownRunnerJdbcImpl.java:192) > at > org.apache.kylin.query.adhoc.PushDownRunnerJdbcImpl.executeQuery(PushDownRunnerJdbcImpl.java:68) > at > org.apache.kylin.query.util.PushDownUtil.tryPushDownQuery(PushDownUtil.java:122) > at > org.apache.kylin.query.util.PushDownUtil.tryPushDownSelectQuery(PushDownUtil.java:69) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [kylin] coveralls commented on issue #718: [KYLIN-3519] Upgrade Jacoco version to 0.8.2
coveralls commented on issue #718: [KYLIN-3519] Upgrade Jacoco version to 0.8.2 URL: https://github.com/apache/kylin/pull/718#issuecomment-506950822 ## Pull Request Test Coverage Report for [Build 4678](https://coveralls.io/builds/24280040) * **0** of **0** changed or added relevant lines in **0** files are covered. * **4** unchanged lines in **2** files lost coverage. * Overall coverage decreased (**-0.004%**) to **28.182%** --- | Files with Coverage Reduction | New Missed Lines | % | | :-|--|--: | | [core-cube/src/main/java/org/apache/kylin/cube/cuboid/TreeCuboidScheduler.java](https://coveralls.io/builds/24280040/source?filename=core-cube%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Fcube%2Fcuboid%2FTreeCuboidScheduler.java#L124) | 2 | 68.46% | | [core-job/src/main/java/org/apache/kylin/job/impl/threadpool/DefaultScheduler.java](https://coveralls.io/builds/24280040/source?filename=core-job%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Fjob%2Fimpl%2Fthreadpool%2FDefaultScheduler.java#L194) | 2 | 80.23% | | Totals | [](https://coveralls.io/builds/24280040) | | :-- | --: | | Change from base [Build 4677](https://coveralls.io/builds/24277319): | -0.004% | | Covered Lines: | 23254 | | Relevant Lines: | 82513 | --- # - [Coveralls](https://coveralls.io) 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 With regards, Apache Git Services
[GitHub] [kylin] codecov-io commented on issue #718: [KYLIN-3519] Upgrade Jacoco version to 0.8.2
codecov-io commented on issue #718: [KYLIN-3519] Upgrade Jacoco version to 0.8.2 URL: https://github.com/apache/kylin/pull/718#issuecomment-506950704 # [Codecov](https://codecov.io/gh/apache/kylin/pull/718?src=pr=h1) Report > Merging [#718](https://codecov.io/gh/apache/kylin/pull/718?src=pr=desc) into [master](https://codecov.io/gh/apache/kylin/commit/916e51d3a932c02d66df0de0fa88d3c4774e8319?src=pr=desc) will **decrease** coverage by `<.01%`. > The diff coverage is `n/a`. [](https://codecov.io/gh/apache/kylin/pull/718?src=pr=tree) ```diff @@ Coverage Diff @@ ## master#718 +/- ## === - Coverage 25.7% 25.7% -0.01% + Complexity 60116009 -2 === Files 13861386 Lines 82513 82513 Branches 11568 11568 === - Hits 21210 21207 -3 - Misses59259 59262 +3 Partials 20442044 ``` | [Impacted Files](https://codecov.io/gh/apache/kylin/pull/718?src=pr=tree) | Coverage Δ | Complexity Δ | | |---|---|---|---| | [...he/kylin/job/impl/threadpool/DefaultScheduler.java](https://codecov.io/gh/apache/kylin/pull/718/diff?src=pr=tree#diff-Y29yZS1qb2Ivc3JjL21haW4vamF2YS9vcmcvYXBhY2hlL2t5bGluL2pvYi9pbXBsL3RocmVhZHBvb2wvRGVmYXVsdFNjaGVkdWxlci5qYXZh) | `74.41% <0%> (-2.33%)` | `12% <0%> (ø)` | | | [.../apache/kylin/cube/cuboid/TreeCuboidScheduler.java](https://codecov.io/gh/apache/kylin/pull/718/diff?src=pr=tree#diff-Y29yZS1jdWJlL3NyYy9tYWluL2phdmEvb3JnL2FwYWNoZS9reWxpbi9jdWJlL2N1Ym9pZC9UcmVlQ3Vib2lkU2NoZWR1bGVyLmphdmE=) | `63.84% <0%> (-2.31%)` | `0% <0%> (ø)` | | | [...pache/kylin/job/impl/curator/CuratorScheduler.java](https://codecov.io/gh/apache/kylin/pull/718/diff?src=pr=tree#diff-Y29yZS1qb2Ivc3JjL21haW4vamF2YS9vcmcvYXBhY2hlL2t5bGluL2pvYi9pbXBsL2N1cmF0b3IvQ3VyYXRvclNjaGVkdWxlci5qYXZh) | `65.25% <0%> (+0.84%)` | `7% <0%> (ø)` | :arrow_down: | | [...ylin/source/jdbc/metadata/JdbcMetadataFactory.java](https://codecov.io/gh/apache/kylin/pull/718/diff?src=pr=tree#diff-c291cmNlLWpkYmMvc3JjL21haW4vamF2YS9vcmcvYXBhY2hlL2t5bGluL3NvdXJjZS9qZGJjL21ldGFkYXRhL0pkYmNNZXRhZGF0YUZhY3RvcnkuamF2YQ==) | `66.66% <0%> (+16.66%)` | `3% <0%> (-2%)` | :arrow_down: | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/kylin/pull/718?src=pr=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/kylin/pull/718?src=pr=footer). Last update [916e51d...152269a](https://codecov.io/gh/apache/kylin/pull/718?src=pr=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). 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 With regards, Apache Git Services
[GitHub] [kylin] asfgit commented on issue #721: [KYLIN-2517] Upgrade Apache Hbase version to 1.4.7
asfgit commented on issue #721: [KYLIN-2517] Upgrade Apache Hbase version to 1.4.7 URL: https://github.com/apache/kylin/pull/721#issuecomment-506950101 Can one of the admins verify this patch? 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 With regards, Apache Git Services
[GitHub] [kylin] weibin0516 opened a new pull request #721: [KYLIN-2517] Upgrade Apache Hbase version to 1.4.7
weibin0516 opened a new pull request #721: [KYLIN-2517] Upgrade Apache Hbase version to 1.4.7 URL: https://github.com/apache/kylin/pull/721 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 With regards, Apache Git Services
[jira] [Commented] (KYLIN-2517) Upgrade hbase dependency to 1.4.7
[ https://issues.apache.org/jira/browse/KYLIN-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875469#comment-16875469 ] ASF GitHub Bot commented on KYLIN-2517: --- weibin0516 commented on pull request #721: [KYLIN-2517] Upgrade Apache Hbase version to 1.4.7 URL: https://github.com/apache/kylin/pull/721 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 > Upgrade hbase dependency to 1.4.7 > - > > Key: KYLIN-2517 > URL: https://issues.apache.org/jira/browse/KYLIN-2517 > Project: Kylin > Issue Type: Improvement >Reporter: Ted Yu >Priority: Major > > There have been major enhancements / bug fixes since the hbase 1.1.1 release. > This issue is to upgrade to 1.4.7 release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [kylin] weibin0516 opened a new pull request #720: [KYLIN-2650] Upgrade Apache Calcite Avatica to version 1.17.0
weibin0516 opened a new pull request #720: [KYLIN-2650] Upgrade Apache Calcite Avatica to version 1.17.0 URL: https://github.com/apache/kylin/pull/720 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 With regards, Apache Git Services
[jira] [Commented] (KYLIN-2650) Update to Apache Calcite Avatica 1.17.0
[ https://issues.apache.org/jira/browse/KYLIN-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875466#comment-16875466 ] ASF GitHub Bot commented on KYLIN-2650: --- weibin0516 commented on pull request #720: [KYLIN-2650] Upgrade Apache Calcite Avatica to version 1.17.0 URL: https://github.com/apache/kylin/pull/720 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 > Update to Apache Calcite Avatica 1.17.0 > --- > > Key: KYLIN-2650 > URL: https://issues.apache.org/jira/browse/KYLIN-2650 > Project: Kylin > Issue Type: Improvement >Reporter: Ted Yu >Priority: Minor > > Apache Calcite Avatica 1.17.0 was released mid-July > https://sematext.com/opensee/m/Calcite/FR3K9IxYty1a4ECo1?subj=+ANNOUNCE+Apache+Calcite+Avatica+1+12+0+released > This issue upgrades Avatica dependency. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [kylin] asfgit commented on issue #720: [KYLIN-2650] Upgrade Apache Calcite Avatica to version 1.17.0
asfgit commented on issue #720: [KYLIN-2650] Upgrade Apache Calcite Avatica to version 1.17.0 URL: https://github.com/apache/kylin/pull/720#issuecomment-506949921 Can one of the admins verify this patch? 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 With regards, Apache Git Services
[jira] [Commented] (KYLIN-3519) Upgrade Jacoco version to 0.8.2
[ https://issues.apache.org/jira/browse/KYLIN-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875465#comment-16875465 ] ASF GitHub Bot commented on KYLIN-3519: --- weibin0516 commented on pull request #719: [KYLIN-3519] Upgrade Hadoop version to 2.7.7 URL: https://github.com/apache/kylin/pull/719 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 > Upgrade Jacoco version to 0.8.2 > --- > > Key: KYLIN-3519 > URL: https://issues.apache.org/jira/browse/KYLIN-3519 > Project: Kylin > Issue Type: Improvement >Reporter: Ted Yu >Priority: Minor > > Jacoco 0.8.2 adds Java 11 support: >https://github.com/jacoco/jacoco/releases/tag/v0.8.2 > Java 11 RC1 is out. > We should consider upgrading Jacoco. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [kylin] asfgit commented on issue #719: [KYLIN-3519] Upgrade Hadoop version to 2.7.7
asfgit commented on issue #719: [KYLIN-3519] Upgrade Hadoop version to 2.7.7 URL: https://github.com/apache/kylin/pull/719#issuecomment-506949590 Can one of the admins verify this patch? 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 With regards, Apache Git Services
[GitHub] [kylin] weibin0516 opened a new pull request #719: [KYLIN-3519] Upgrade Hadoop version to 2.7.7
weibin0516 opened a new pull request #719: [KYLIN-3519] Upgrade Hadoop version to 2.7.7 URL: https://github.com/apache/kylin/pull/719 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 With regards, Apache Git Services
[GitHub] [kylin] asfgit commented on issue #718: [KYLIN-3519] Upgrade Jacoco version to 0.8.2
asfgit commented on issue #718: [KYLIN-3519] Upgrade Jacoco version to 0.8.2 URL: https://github.com/apache/kylin/pull/718#issuecomment-506948908 Can one of the admins verify this patch? 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 With regards, Apache Git Services
[jira] [Commented] (KYLIN-3519) Upgrade Jacoco version to 0.8.2
[ https://issues.apache.org/jira/browse/KYLIN-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875462#comment-16875462 ] ASF GitHub Bot commented on KYLIN-3519: --- keepsimplefocus commented on pull request #718: [KYLIN-3519] Upgrade Jacoco version to 0.8.2 URL: https://github.com/apache/kylin/pull/718 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 > Upgrade Jacoco version to 0.8.2 > --- > > Key: KYLIN-3519 > URL: https://issues.apache.org/jira/browse/KYLIN-3519 > Project: Kylin > Issue Type: Improvement >Reporter: Ted Yu >Priority: Minor > > Jacoco 0.8.2 adds Java 11 support: >https://github.com/jacoco/jacoco/releases/tag/v0.8.2 > Java 11 RC1 is out. > We should consider upgrading Jacoco. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [kylin] keepsimplefocus opened a new pull request #718: [KYLIN-3519] Upgrade Jacoco version to 0.8.2
keepsimplefocus opened a new pull request #718: [KYLIN-3519] Upgrade Jacoco version to 0.8.2 URL: https://github.com/apache/kylin/pull/718 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 With regards, Apache Git Services
[jira] [Commented] (KYLIN-3832) Kylin Pushdown query not support postgresql
[ https://issues.apache.org/jira/browse/KYLIN-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875401#comment-16875401 ] weibin1991 commented on KYLIN-3832: --- I'd like to implement the postgresql data source adapter. Please assign to me. > Kylin Pushdown query not support postgresql > --- > > Key: KYLIN-3832 > URL: https://issues.apache.org/jira/browse/KYLIN-3832 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v2.5.2 >Reporter: hailin.huang >Priority: Major > Fix For: Future > > > when I run pushdown to postgresql in my env, I encount the below exception. > it seems that kylin need support more JDBC Driver, > PushDownRunnerJdbcImpl.class should be more general. > 2019-02-26 16:12:53,168 ERROR [Query 207dcf77-7c14-8078-ea8b-79644a0c576d-48] > service.QueryService:989 : pushdown engine failed current query too > java.sql.SQLException: Unrecognized column type: int8 > at > org.apache.kylin.query.adhoc.PushDownRunnerJdbcImpl.toSqlType(PushDownRunnerJdbcImpl.java:260) > at > org.apache.kylin.query.adhoc.PushDownRunnerJdbcImpl.extractColumnMeta(PushDownRunnerJdbcImpl.java:192) > at > org.apache.kylin.query.adhoc.PushDownRunnerJdbcImpl.executeQuery(PushDownRunnerJdbcImpl.java:68) > at > org.apache.kylin.query.util.PushDownUtil.tryPushDownQuery(PushDownUtil.java:122) > at > org.apache.kylin.query.util.PushDownUtil.tryPushDownSelectQuery(PushDownUtil.java:69) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
