[jira] [Updated] (KYLIN-1799) Add a document to setup kylin on spark engine?
[ https://issues.apache.org/jira/browse/KYLIN-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1799: Request participants: (was: ) Fix Version/s: v2.0.0 > Add a document to setup kylin on spark engine? > -- > > Key: KYLIN-1799 > URL: https://issues.apache.org/jira/browse/KYLIN-1799 > Project: Kylin > Issue Type: Wish > Components: Spark Engine >Reporter: zhengyaohong >Assignee: Shaofeng SHI > Fix For: v2.0.0 > > > Add a document to setup kylin on spark engine? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (KYLIN-1799) Add a document to setup kylin on spark engine?
[ https://issues.apache.org/jira/browse/KYLIN-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI reassigned KYLIN-1799: --- Assignee: Shaofeng SHI > Add a document to setup kylin on spark engine? > -- > > Key: KYLIN-1799 > URL: https://issues.apache.org/jira/browse/KYLIN-1799 > Project: Kylin > Issue Type: Wish > Components: Spark Engine >Reporter: zhengyaohong >Assignee: Shaofeng SHI > Fix For: v2.0.0 > > > Add a document to setup kylin on spark engine? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (KYLIN-2445) UI: select cube engine in "Advanced setting" page
[ https://issues.apache.org/jira/browse/KYLIN-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI reassigned KYLIN-2445: --- Assignee: Zhixiong Chen (was: Zhong,Jason) Request participants: (was: ) > UI: select cube engine in "Advanced setting" page > - > > Key: KYLIN-2445 > URL: https://issues.apache.org/jira/browse/KYLIN-2445 > Project: Kylin > Issue Type: Sub-task > Components: Web >Affects Versions: v2.0.0 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.0.0 > > > Allow user to select a cube engine when define the cube; there are two > options: MapReduce, Spark; The selection determines the "engine_type" value > of a cube descriptor: MR=2, Spark=4; -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KYLIN-2445) UI: select cube engine in "Advanced setting" page
Shaofeng SHI created KYLIN-2445: --- Summary: UI: select cube engine in "Advanced setting" page Key: KYLIN-2445 URL: https://issues.apache.org/jira/browse/KYLIN-2445 Project: Kylin Issue Type: Sub-task Components: Web Affects Versions: v2.0.0 Reporter: Shaofeng SHI Assignee: Zhong,Jason Fix For: v2.0.0 Allow user to select a cube engine when define the cube; there are two options: MapReduce, Spark; The selection determines the "engine_type" value of a cube descriptor: MR=2, Spark=4; -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2243) TopN memory estimation is inaccurate in some cases
[ https://issues.apache.org/jira/browse/KYLIN-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-2243: Description: TopNCounterSerializer.maxLength() and TopNCounterSerializer.getStorageBytesEstimate() might be inaccurate, especially when there are multiple "group by" columns in one TopN measure and some uses long bytes encoding like "fixed_length:16" The inaccurate estimation may cause memory issue when using in-mem cubing, and will cause the estimation on final cube size inaccurate. The root cause is the data type like "top(100)" doesn't have the info of how long a key can be. So far it uses a default value 4 which is too small when the encoding is something like "fixed_length:16". The solution is extending the expression of data type to "top(100, 16)" to indicate that one key can be 16 bytes long. If the "scale" is absent, use 8 bytes as default. was: TopNCounterSerializer.maxLength() and TopNCounterSerializer.getStorageBytesEstimate() might be inaccurate, especially when there are multiple "group by" columns in one TopN measure and some uses long bytes encoding like "fixed_length:16" The inaccurate estimation may cause memory issue when using in-mem cubing, and will cause the estimation on final cube size inaccurate. > TopN memory estimation is inaccurate in some cases > -- > > Key: KYLIN-2243 > URL: https://issues.apache.org/jira/browse/KYLIN-2243 > Project: Kylin > Issue Type: Bug >Reporter: Shaofeng SHI > Fix For: Backlog > > > TopNCounterSerializer.maxLength() and > TopNCounterSerializer.getStorageBytesEstimate() might be inaccurate, > especially when there are multiple "group by" columns in one TopN measure and > some uses long bytes encoding like "fixed_length:16" > The inaccurate estimation may cause memory issue when using in-mem cubing, > and will cause the estimation on final cube size inaccurate. > The root cause is the data type like "top(100)" doesn't have the info of how > long a key can be. So far it uses a default value 4 which is too small when > the encoding is something like "fixed_length:16". The solution is extending > the expression of data type to "top(100, 16)" to indicate that one key can be > 16 bytes long. If the "scale" is absent, use 8 bytes as default. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2428) Cleanup unnecessary shaded libraries for job/coprocessor/jdbc/server
[ https://issues.apache.org/jira/browse/KYLIN-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15865163#comment-15865163 ] Billy Liu commented on KYLIN-2428: -- Hi [~Shaofengshi], the patch has rebased with the latest master with support on Spark IT. It passed IT test. Could you help review this patch? or check the code on the dev branch https://github.com/apache/kylin/commit/f10d9d9ba95878a97f70975547763083c000bcfe > Cleanup unnecessary shaded libraries for job/coprocessor/jdbc/server > > > Key: KYLIN-2428 > URL: https://issues.apache.org/jira/browse/KYLIN-2428 > Project: Kylin > Issue Type: Improvement > Components: General >Affects Versions: v1.6.0 >Reporter: Billy Liu >Assignee: Billy Liu > Attachments: KYLIN-2428.patch > > > Kylin releases three libraries: kylin-coprocessor, kylin-jdbc, kylin-job and > one web application: server. > Currently, all libraries have shaded some used third party libraries into the > package. For example, guava, curator, commons, kyro in kylin-job. The > duplicate libraries in runtime classpath may have potential class loading > conflicts and waste computing resource. We should leverage the hadoop > provided libraries at runtime instead of the shaded one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Issue Comment Deleted] (KYLIN-2428) Cleanup unnecessary shaded libraries for job/coprocessor/jdbc/server
[ https://issues.apache.org/jira/browse/KYLIN-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Liu updated KYLIN-2428: - Comment: was deleted (was: [INFO] Apache Kylin ... SUCCESS [ 3.045 s] [INFO] Apache Kylin - Calcite Overrides ... SUCCESS [ 2.161 s] [INFO] Apache Kylin - Core Common . SUCCESS [ 5.515 s] [INFO] Apache Kylin - Core Metadata ... SUCCESS [ 25.081 s] [INFO] Apache Kylin - Core Dictionary . SUCCESS [01:14 min] [INFO] Apache Kylin - Core Cube ... SUCCESS [01:44 min] [INFO] Apache Kylin - Core Job SUCCESS [01:58 min] [INFO] Apache Kylin - Core Storage SUCCESS [ 34.999 s] [INFO] Apache Kylin - MapReduce Engine SUCCESS [ 20.623 s] [INFO] Apache Kylin - HBase Storage ... SUCCESS [ 12.564 s] [INFO] Apache Kylin - Spark Engine SUCCESS [ 13.664 s] [INFO] Apache Kylin - Hive Source . SUCCESS [ 4.314 s] [INFO] Apache Kylin - Kafka Source SUCCESS [ 3.250 s] [INFO] Apache Kylin - Query ... SUCCESS [ 2.485 s] [INFO] Apache Kylin - Tool SUCCESS [ 4.199 s] [INFO] Apache Kylin - REST Server Base SUCCESS [ 6.802 s] [INFO] Apache Kylin - REST Server . SUCCESS [ 37.196 s] [INFO] Apache Kylin - JDBC Driver . SUCCESS [ 5.646 s] [INFO] Apache Kylin - Assembly SUCCESS [ 5.158 s] [INFO] Apache Kylin - Integration Test SUCCESS [ 01:08 h] [INFO] Apache Kylin - Tomcat Extension SUCCESS [ 2.810 s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 01:16 h [INFO] Finished at: 2017-02-07T15:27:23+00:00 [INFO] Final Memory: 75M/935M) > Cleanup unnecessary shaded libraries for job/coprocessor/jdbc/server > > > Key: KYLIN-2428 > URL: https://issues.apache.org/jira/browse/KYLIN-2428 > Project: Kylin > Issue Type: Improvement > Components: General >Affects Versions: v1.6.0 >Reporter: Billy Liu >Assignee: Billy Liu > Attachments: KYLIN-2428.patch > > > Kylin releases three libraries: kylin-coprocessor, kylin-jdbc, kylin-job and > one web application: server. > Currently, all libraries have shaded some used third party libraries into the > package. For example, guava, curator, commons, kyro in kylin-job. The > duplicate libraries in runtime classpath may have potential class loading > conflicts and waste computing resource. We should leverage the hadoop > provided libraries at runtime instead of the shaded one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2428) Cleanup unnecessary shaded libraries for job/coprocessor/jdbc/server
[ https://issues.apache.org/jira/browse/KYLIN-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15865161#comment-15865161 ] Billy Liu commented on KYLIN-2428: -- [INFO] Apache Kylin ... SUCCESS [ 3.483 s] [INFO] Apache Kylin - Calcite Overrides ... SUCCESS [ 2.295 s] [INFO] Apache Kylin - Core Common . SUCCESS [ 5.559 s] [INFO] Apache Kylin - Core Metadata ... SUCCESS [ 26.885 s] [INFO] Apache Kylin - Core Dictionary . SUCCESS [01:18 min] [INFO] Apache Kylin - Core Cube ... SUCCESS [01:49 min] [INFO] Apache Kylin - Core Job SUCCESS [01:58 min] [INFO] Apache Kylin - Core Storage SUCCESS [ 35.183 s] [INFO] Apache Kylin - MapReduce Engine SUCCESS [ 22.122 s] [INFO] Apache Kylin - HBase Storage ... SUCCESS [ 14.430 s] [INFO] Apache Kylin - Spark Engine SUCCESS [ 9.362 s] [INFO] Apache Kylin - Hive Source . SUCCESS [ 4.243 s] [INFO] Apache Kylin - Kafka Source SUCCESS [ 3.351 s] [INFO] Apache Kylin - Query ... SUCCESS [ 2.604 s] [INFO] Apache Kylin - Tool SUCCESS [ 4.809 s] [INFO] Apache Kylin - REST Server Base SUCCESS [ 7.992 s] [INFO] Apache Kylin - REST Server . SUCCESS [ 39.903 s] [INFO] Apache Kylin - JDBC Driver . SUCCESS [ 4.899 s] [INFO] Apache Kylin - Assembly SUCCESS [ 6.212 s] [INFO] Apache Kylin - Tool Assembly ... SUCCESS [ 2.187 s] [INFO] Apache Kylin - Integration Test SUCCESS [ 01:03 h] [INFO] Apache Kylin - Tomcat Extension SUCCESS [ 0.633 s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 01:12 h [INFO] Finished at: 2017-02-14T14:25:15+00:00 [INFO] Final Memory: 76M/856M > Cleanup unnecessary shaded libraries for job/coprocessor/jdbc/server > > > Key: KYLIN-2428 > URL: https://issues.apache.org/jira/browse/KYLIN-2428 > Project: Kylin > Issue Type: Improvement > Components: General >Affects Versions: v1.6.0 >Reporter: Billy Liu >Assignee: Billy Liu > Attachments: KYLIN-2428.patch > > > Kylin releases three libraries: kylin-coprocessor, kylin-jdbc, kylin-job and > one web application: server. > Currently, all libraries have shaded some used third party libraries into the > package. For example, guava, curator, commons, kyro in kylin-job. The > duplicate libraries in runtime classpath may have potential class loading > conflicts and waste computing resource. We should leverage the hadoop > provided libraries at runtime instead of the shaded one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2428) Cleanup unnecessary shaded libraries for job/coprocessor/jdbc/server
[ https://issues.apache.org/jira/browse/KYLIN-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Liu updated KYLIN-2428: - Attachment: KYLIN-2428.patch > Cleanup unnecessary shaded libraries for job/coprocessor/jdbc/server > > > Key: KYLIN-2428 > URL: https://issues.apache.org/jira/browse/KYLIN-2428 > Project: Kylin > Issue Type: Improvement > Components: General >Affects Versions: v1.6.0 >Reporter: Billy Liu >Assignee: Billy Liu > Attachments: KYLIN-2428.patch > > > Kylin releases three libraries: kylin-coprocessor, kylin-jdbc, kylin-job and > one web application: server. > Currently, all libraries have shaded some used third party libraries into the > package. For example, guava, curator, commons, kyro in kylin-job. The > duplicate libraries in runtime classpath may have potential class loading > conflicts and waste computing resource. We should leverage the hadoop > provided libraries at runtime instead of the shaded one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2428) Cleanup unnecessary shaded libraries for job/coprocessor/jdbc/server
[ https://issues.apache.org/jira/browse/KYLIN-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Liu updated KYLIN-2428: - Attachment: (was: KYLIN-2428.patch) > Cleanup unnecessary shaded libraries for job/coprocessor/jdbc/server > > > Key: KYLIN-2428 > URL: https://issues.apache.org/jira/browse/KYLIN-2428 > Project: Kylin > Issue Type: Improvement > Components: General >Affects Versions: v1.6.0 >Reporter: Billy Liu >Assignee: Billy Liu > Attachments: KYLIN-2428.patch > > > Kylin releases three libraries: kylin-coprocessor, kylin-jdbc, kylin-job and > one web application: server. > Currently, all libraries have shaded some used third party libraries into the > package. For example, guava, curator, commons, kyro in kylin-job. The > duplicate libraries in runtime classpath may have potential class loading > conflicts and waste computing resource. We should leverage the hadoop > provided libraries at runtime instead of the shaded one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KYLIN-2444) Kylin should release different hadoop versions to maven repository
Shaofeng SHI created KYLIN-2444: --- Summary: Kylin should release different hadoop versions to maven repository Key: KYLIN-2444 URL: https://issues.apache.org/jira/browse/KYLIN-2444 Project: Kylin Issue Type: Improvement Components: General Reporter: Shaofeng SHI Till 1.6.0, Kylin only release/install one compiled version to maven repository, they are all compiled with hbase 0.98; For example, kylin-storage-hbase:1.6.0, actually it is kylin-storage-hbase-0.98:1.6.0. Expectation: kylin release multiple versions: kylin-storage-hbase-0.98:, kylin-storage-hbase-1.1:, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2407) TPC-H query 20, why this query returns no result?
[
https://issues.apache.org/jira/browse/KYLIN-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15864864#comment-15864864
]
Kaige Liu commented on KYLIN-2407:
---
IN clause is parsed to an inner join here.So that we got a "LOOKUP T" join "SUB
QUERY" which should use *executeLookupTableQuery* to do the query, but was
routed to *executeOLAPQuery*.
{code}
OLAPToEnumerableConverter
EnumerableLimit(fetch=[5])
EnumerableSort(sort0=[$0], dir0=[ASC])
EnumerableCalc(expr#0..7=[{inputs}], S_NAME=[$t1], S_ADDRESS=[$t2])
EnumerableJoin(condition=[=($0, $7)], joinType=[inner])
<- IN clause here
OLAPTableScan(table=[[TPCH_FLAT_ORC_2, SUPPLIER]], fields=[[0, 1, 2,
3, 4, 5, 6]]) <--- This is a lookup table
EnumerableAggregate(group=[{0}])
EnumerableCalc(expr#0..10=[{inputs}], expr#11=[>($t2, $t9)],
PS_SUPPKEY=[$t1], $condition=[$t11])
EnumerableJoin(condition=[AND(=($0, $8), =($1, $10))],
joinType=[inner])
OLAPTableScan(table=[[TPCH_FLAT_ORC_2, V_PARTSUPP]],
fields=[[0, 1, 2, 3, 4, 5, 6, 7]])
EnumerableCalc(expr#0..2=[{inputs}], expr#3=[0.5],
expr#4=[*($t3, $t2)], L_PARTKEY=[$t0], SUM_QUANTITY=[$t4], L_SUPPKEY=[$t1])
EnumerableAggregate(group=[{0, 1}], agg#0=[SUM($2)])
EnumerableCalc(expr#0..36=[{inputs}],
expr#37=['1992-01-01'], expr#38=[>=($t8, $t37)], expr#39=['1995-01-01'],
expr#40=[<=($t8, $t39)], expr#41=['CANADA'], expr#42=[=($t28, $t41)],
expr#43=['forest%'], expr#44=[LIKE($t31, $t43)], expr#45=[AND($t38, $t40, $t42,
$t44)], L_PARTKEY=[$t1], L_SUPPKEY=[$t2], L_QUANTITY=[$t3], $condition=[$t45])
OLAPJoinRel(condition=[=($1, $30)], joinType=[inner])
OLAPJoinRel(condition=[=($23, $27)], joinType=[inner])
OLAPJoinRel(condition=[=($2, $20)], joinType=[inner])
OLAPTableScan(table=[[TPCH_FLAT_ORC_2,
V_LINEITEM]], fields=[[0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
16, 17, 18, 19]])
OLAPTableScan(table=[[TPCH_FLAT_ORC_2, SUPPLIER]],
fields=[[0, 1, 2, 3, 4, 5, 6]])
OLAPTableScan(table=[[TPCH_FLAT_ORC_2, NATION]],
fields=[[0, 1, 2]])
OLAPTableScan(table=[[TPCH_FLAT_ORC_2, PART]],
fields=[[0, 1, 2, 3, 4, 5, 6]])
{code}
The logic to route query method below is not correct:
{code}
private String genExecFunc() {
// if the table to scan is not the fact table of cube, then it's a
lookup table
if (context.hasJoin == false &&
context.realization.getModel().isLookupTable(tableName)) {
return "executeLookupTableQuery";
} else {
return "executeOLAPQuery";
}
}
{code}
> TPC-H query 20, why this query returns no result?
> -
>
> Key: KYLIN-2407
> URL: https://issues.apache.org/jira/browse/KYLIN-2407
> Project: Kylin
> Issue Type: Bug
>Reporter: liyang
>Assignee: Kaige Liu
>
> Below query returns no result.
> {code}
> with tmp3 as (
> select l_partkey, 0.5 * sum(l_quantity) as sum_quantity, l_suppkey
> from v_lineitem
> inner join supplier on l_suppkey = s_suppkey
> inner join nation on s_nationkey = n_nationkey
> inner join part on l_partkey = p_partkey
> where l_shipdate >= '1992-01-01' and l_shipdate <= '1995-01-01'
> and n_name = 'CANADA'
> and p_name like 'forest%'
> group by l_partkey, l_suppkey
> ),
> tmp5 as (
> select
> ps_suppkey
> from
> v_partsupp inner join tmp3 on ps_partkey = l_partkey and ps_suppkey =
> l_suppkey
> where
> ps_availqty > sum_quantity
> )
> select
> s_name,
> s_address
> from
> supplier
> where
> s_suppkey IN (select ps_suppkey from tmp5)
> order by s_name
> {code}
> While another similar query returns correct result.
> {code}
> with tmp3 as (
> select l_partkey, 0.5 * sum(l_quantity) as sum_quantity, l_suppkey
> from v_lineitem
> inner join supplier on l_suppkey = s_suppkey
> inner join nation on s_nationkey = n_nationkey
> inner join part on l_partkey = p_partkey
> where l_shipdate >= '1992-01-01' and l_shipdate <= '1995-01-01'
> and n_name = 'CANADA'
> and p_name like 'forest%'
> group by l_partkey, l_suppkey
> )
> select
> s_name,
> s_address
> from
> v_partsupp
> inner join supplier on ps_suppkey = s_suppkey
> inner join tmp3 on ps_partkey = l_partkey and ps_suppkey = l_suppkey
> where
> ps_availqty > sum_quantity
> group by
> s_name, s_address
> order by
> s_name
> {code}
> Maybe something wrong with the "where ... IN ..." clause?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KYLIN-2274) Dundas ODBC Error: SQLColAttribute unknown attr,
[
https://issues.apache.org/jira/browse/KYLIN-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863695#comment-15863695
]
albertoramon commented on KYLIN-2274:
-
I tested on SqurrieL, and Works OK, but this use JAR directly (OLEDB)
Also work with Kylin UI (Rest API)
for that reason, I think the problem is on ODBC Driver
> Dundas ODBC Error: SQLColAttribute unknown attr,
>
>
> Key: KYLIN-2274
> URL: https://issues.apache.org/jira/browse/KYLIN-2274
> Project: Kylin
> Issue Type: Bug
> Components: Driver - ODBC
>Affects Versions: v1.6.0
> Environment: Kylin 1.6.0
> ODBC 1.6 64 bits
> Dundas BI: 3.0.2 Windows7 64 bits
>Reporter: albertoramon
>Assignee: Dong Li
> Attachments: dundas.png, odbc-2016-12-06-19-01-51.log, Q1ON
> SQuirrel.png, Q2onLylinUI.png, Q2onSQuirrel.png, TheProblem.png
>
>
> I tested [Dundas Software|http://www.dundas.com/dundas-bi]
> (I used Kylin Sample Cube)
> (I try with SQuirreL because it uses JDBC directly, and perhaps this can
> helpful )
> You can read list of tables :)
> !dundas.png!
> But when you try to load data of these, there is two types of errors:
> *Error 1:* (from ODBC Log)
> {quote}
> [INFO ] [2016-12-06.19:05:30]SELECT * FROM "DEFAULT"."KYLIN_CAL_DT" WHERE 1 =
> 2
> [INFO ] [2016-12-06.19:05:30]Successfully done executing the query
> [FATAL] [2016-12-06.19:05:30]SQLColAttribute unknown attr, ColNum: 1, FldID:
> 1211
> {quote}
> This query works OK on Kylin UI and SQuirriel:
> !Q1ON SQuirrel.png!
> \\
> \\
> \\
> *Error 2:* (from ODBC Log)
> {quote}
> [ERROR][2016-12-06.19:30:27]The REST query request failed, the error message
> is: Error while executing SQL "SELECT T."USER_DEFINED_FIELD1" AS "TE0",
> T."SITE_ID" AS "TE1" FROM "DEFAULT"."KYLIN_CAL_DT" T GROUP BY
> T."USER_DEFINED_FIELD1", T."SITE_ID" ORDER BY T."USER_DEFINED_FIELD1",
> T."SITE_ID"": From line 1, column 106 to line 1, column 126: Column
> 'USER_DEFINED_FIELD1' not found in table 'T'
> {quote}
> This Query fails on Kylin UI:
> !Q2onLylinUI.png!
> _ERROR: Column 'USER_DEFINED_FIELD1' not found in table 'T'_
> This Query fails on SQuirrel:
> !Q2onSQuirrel.png!
> _ERROR: ava.sql.SQLException: java.io.IOException: POST failed, error code
> 500 and response:
> {"url":"http://172.17.0.2:7070/kylin/api/query","exception":"Error while
> executing SQL \"SELECT T.\"USER_DEFINED_FIELD1\" AS \"TE0\" , T.\"SITE_ID\"
> AS \"TE1\" FROM \"DEFAULT\".\"KYLIN_CAL_DT\" T GROUP BY
> T.\"USER_DEFINED_FIELD1\", T.\"SITE_ID\" ORDER BY
> T.\"USER_DEFINED_FIELD1\", T.\"SITE_ID\"\": From line 4, column 13 to line 4,
> column 33: Column 'USER_DEFINED_FIELD1' not found in table 'T'"}_
> *The problem on Q2 is:*
> ... was very simple, somebody / Dundas?? is crossing columns with their
> tables tables
> !TheProblem.png!
> these columns are of other table :) why? who?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KYLIN-2429) Variable initialized should be declared volatile in SparkCubingByLayer#execute()
[
https://issues.apache.org/jira/browse/KYLIN-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated KYLIN-2429:
--
Description:
{code}
final JavaPairRDD encodedBaseRDD =
intermediateTable.javaRDD().mapToPair(new PairFunction() {
transient boolean initialized = false;
...
public Tuple2 call(Row row) throws Exception {
if (initialized == false) {
synchronized (SparkCubingByLayer.class) {
if (initialized == false) {
{code}
For double checked locking to work, initialized needs to be volatile.
was:
{code}
final JavaPairRDD encodedBaseRDD =
intermediateTable.javaRDD().mapToPair(new PairFunction() {
transient boolean initialized = false;
...
public Tuple2 call(Row row) throws Exception {
if (initialized == false) {
synchronized (SparkCubingByLayer.class) {
if (initialized == false) {
{code}
For double checked locking to work, initialized needs to be volatile.
> Variable initialized should be declared volatile in
> SparkCubingByLayer#execute()
>
>
> Key: KYLIN-2429
> URL: https://issues.apache.org/jira/browse/KYLIN-2429
> Project: Kylin
> Issue Type: Bug
>Reporter: Ted Yu
>
> {code}
> final JavaPairRDD encodedBaseRDD =
> intermediateTable.javaRDD().mapToPair(new PairFunction Object[]>() {
> transient boolean initialized = false;
> ...
> public Tuple2 call(Row row) throws Exception
> {
> if (initialized == false) {
> synchronized (SparkCubingByLayer.class) {
> if (initialized == false) {
> {code}
> For double checked locking to work, initialized needs to be volatile.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KYLIN-2274) Dundas ODBC Error: SQLColAttribute unknown attr,
[
https://issues.apache.org/jira/browse/KYLIN-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863278#comment-15863278
]
Yifan Zhang commented on KYLIN-2274:
For Q1, have you tried with other BI tools. I'm thinking if it's Dundas spec
problem.
I did not see such problem with power BI (see following odbc log)
Log start: Mon Feb 13 11:07:36 2017
[INFO ][2017-02-13.11:07:36]SQLFreeStmt called, 75576512 with option 0
[INFO
][2017-02-13.11:07:36]
[INFO ][2017-02-13.11:07:36]start exec the query:
[INFO ][2017-02-13.11:07:36]SELECT * FROM "DEFAULT"."KYLIN_CAL_DT" WHERE 1 = 2
[INFO ][2017-02-13.11:07:37]Successfully done executing the query
[INFO ][2017-02-13.11:07:37]Last row of current query has been fetched
[INFO ][2017-02-13.11:07:37]SQLFreeHandle called, Handle Type: 3, Handle:
75576512
[INFO ][2017-02-13.11:07:37]SQLDisconnect called
[INFO ][2017-02-13.11:07:37]SQLFreeHandle called, Handle Type: 2, Handle:
75552128
[INFO ][2017-02-13.11:07:37]SQLFreeHandle called, Handle Type: 1, Handle:
5019184
> Dundas ODBC Error: SQLColAttribute unknown attr,
>
>
> Key: KYLIN-2274
> URL: https://issues.apache.org/jira/browse/KYLIN-2274
> Project: Kylin
> Issue Type: Bug
> Components: Driver - ODBC
>Affects Versions: v1.6.0
> Environment: Kylin 1.6.0
> ODBC 1.6 64 bits
> Dundas BI: 3.0.2 Windows7 64 bits
>Reporter: albertoramon
>Assignee: Dong Li
> Attachments: dundas.png, odbc-2016-12-06-19-01-51.log, Q1ON
> SQuirrel.png, Q2onLylinUI.png, Q2onSQuirrel.png, TheProblem.png
>
>
> I tested [Dundas Software|http://www.dundas.com/dundas-bi]
> (I used Kylin Sample Cube)
> (I try with SQuirreL because it uses JDBC directly, and perhaps this can
> helpful )
> You can read list of tables :)
> !dundas.png!
> But when you try to load data of these, there is two types of errors:
> *Error 1:* (from ODBC Log)
> {quote}
> [INFO ] [2016-12-06.19:05:30]SELECT * FROM "DEFAULT"."KYLIN_CAL_DT" WHERE 1 =
> 2
> [INFO ] [2016-12-06.19:05:30]Successfully done executing the query
> [FATAL] [2016-12-06.19:05:30]SQLColAttribute unknown attr, ColNum: 1, FldID:
> 1211
> {quote}
> This query works OK on Kylin UI and SQuirriel:
> !Q1ON SQuirrel.png!
> \\
> \\
> \\
> *Error 2:* (from ODBC Log)
> {quote}
> [ERROR][2016-12-06.19:30:27]The REST query request failed, the error message
> is: Error while executing SQL "SELECT T."USER_DEFINED_FIELD1" AS "TE0",
> T."SITE_ID" AS "TE1" FROM "DEFAULT"."KYLIN_CAL_DT" T GROUP BY
> T."USER_DEFINED_FIELD1", T."SITE_ID" ORDER BY T."USER_DEFINED_FIELD1",
> T."SITE_ID"": From line 1, column 106 to line 1, column 126: Column
> 'USER_DEFINED_FIELD1' not found in table 'T'
> {quote}
> This Query fails on Kylin UI:
> !Q2onLylinUI.png!
> _ERROR: Column 'USER_DEFINED_FIELD1' not found in table 'T'_
> This Query fails on SQuirrel:
> !Q2onSQuirrel.png!
> _ERROR: ava.sql.SQLException: java.io.IOException: POST failed, error code
> 500 and response:
> {"url":"http://172.17.0.2:7070/kylin/api/query","exception":"Error while
> executing SQL \"SELECT T.\"USER_DEFINED_FIELD1\" AS \"TE0\" , T.\"SITE_ID\"
> AS \"TE1\" FROM \"DEFAULT\".\"KYLIN_CAL_DT\" T GROUP BY
> T.\"USER_DEFINED_FIELD1\", T.\"SITE_ID\" ORDER BY
> T.\"USER_DEFINED_FIELD1\", T.\"SITE_ID\"\": From line 4, column 13 to line 4,
> column 33: Column 'USER_DEFINED_FIELD1' not found in table 'T'"}_
> *The problem on Q2 is:*
> ... was very simple, somebody / Dundas?? is crossing columns with their
> tables tables
> !TheProblem.png!
> these columns are of other table :) why? who?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
