[jira] [Updated] (KYLIN-1623) Make the hll precision for data samping configurable
[ https://issues.apache.org/jira/browse/KYLIN-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Li updated KYLIN-1623: --- Issue Type: Improvement (was: New Feature) > Make the hll precision for data samping configurable > > > Key: KYLIN-1623 > URL: https://issues.apache.org/jira/browse/KYLIN-1623 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > Fix For: v1.5.2 > > > now kylin uses hll(14) for sampling; it should be configurable at cube level > for small or large cubes. Property name > "kylin.job.cubing.inmem.sampling.hll.precision", default be 14; allowed > values: 10, 12, 14, 16 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1695) Skip cardinality calculation job when loading hive table
[ https://issues.apache.org/jira/browse/KYLIN-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kangkaisen updated KYLIN-1695: -- Attachment: (was: KYLIN-1695.patch) > Skip cardinality calculation job when loading hive table > > > Key: KYLIN-1695 > URL: https://issues.apache.org/jira/browse/KYLIN-1695 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v1.5.1 >Reporter: kangkaisen >Assignee: Dong Li > > When user loads/reloads hive tables from web console, kylin will submit a mr > job asynchronously to calculate column cardinalities. This has four major > problems: > # the calculated cardinality is stored in table metadata, but never used in > cubing/querying > # table may change after loading, so the cardinality doesn't necessarily > reflect the actual value > # the current `HiveColumnCardinalityJob` has many limitations, e.g., it > doesn't support views > # the `HiveColumnCardinalityJob` may use lots of resources when computing > cardinality of partitioned table > Due to these problems, we should disable it by default and (maybe) remove it > in future releases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1695) Skip cardinality calculation job when loading hive table
[ https://issues.apache.org/jira/browse/KYLIN-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kangkaisen updated KYLIN-1695: -- Attachment: KYLIN-1695.patch This patch add a checkbox in the "add hive table" web page, asking user to select whether calculate the cardinality. the default value of checkbox is true. > Skip cardinality calculation job when loading hive table > > > Key: KYLIN-1695 > URL: https://issues.apache.org/jira/browse/KYLIN-1695 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v1.5.1 >Reporter: kangkaisen >Assignee: Dong Li > Attachments: KYLIN-1695.patch > > > When user loads/reloads hive tables from web console, kylin will submit a mr > job asynchronously to calculate column cardinalities. This has four major > problems: > # the calculated cardinality is stored in table metadata, but never used in > cubing/querying > # table may change after loading, so the cardinality doesn't necessarily > reflect the actual value > # the current `HiveColumnCardinalityJob` has many limitations, e.g., it > doesn't support views > # the `HiveColumnCardinalityJob` may use lots of resources when computing > cardinality of partitioned table > Due to these problems, we should disable it by default and (maybe) remove it > in future releases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-1721) KylinConfigExt lost base properties when store into file
Yerui Sun created KYLIN-1721:
Summary: KylinConfigExt lost base properties when store into file
Key: KYLIN-1721
URL: https://issues.apache.org/jira/browse/KYLIN-1721
Project: Kylin
Issue Type: Bug
Components: Metadata
Affects Versions: v1.5.2
Reporter: Yerui Sun
Assignee: Yerui Sun
Priority: Critical
Fix For: v1.5.2
KylinConfigExt overrides getAllProperties() to merge the base properties and
the override properties into one Properties, which used to get config or write
into file.
In the following code, super properties stored in Properties.*defaults*, which
will *NOT* written out by store() method, quoted from [java
document|https://docs.oracle.com/javase/7/docs/api/java/util/Properties.html#store(java.io.OutputStream,%20java.lang.String)].
That will lost super properties when store KylinConfigExt into file.
{code}
protected Properties getAllProperties() {
Properties result = new Properties(super.getAllProperties());
result.putAll(overrides);
return result;
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KYLIN-1720) Apache Kylin:- Measures is not seen anywhere
[ https://issues.apache.org/jira/browse/KYLIN-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295114#comment-15295114 ] Yerui Sun commented on KYLIN-1720: -- MAX_PRICE is the measure name used by kylin internally, you should use max(price) instead of MAX_PRICE in your sql, just like query in other system. BTW, jira is mainly used to manage progress of bug or feature, you'd better ask questions in mail list d...@kylin.apache.org or u...@kylin.apache.org. > Apache Kylin:- Measures is not seen anywhere > > > Key: KYLIN-1720 > URL: https://issues.apache.org/jira/browse/KYLIN-1720 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.5.1 >Reporter: Rahul Choubey >Priority: Blocker > Attachments: image.png > > > We have created measures in cube that we have created through Kylin. > But the question is where this measures will get stored and how can I use > them when I query the cubes. I want to use these measures in my select > statement while querying the cube for e.g.:- > SELECT KYLIN_CATEGORY_GROUPINGS.BSNS_VRTCL_NAME,KYLIN_CAL_DT.YEAR_BEG_DT, > MAX_PRICE FROM KYLIN_SALES > INNER JOIN KYLIN_CATEGORY_GROUPINGS > ON KYLIN_SALES.LEAF_CATEG_ID = KYLIN_CATEGORY_GROUPINGS.LEAF_CATEG_ID AND > KYLIN_SALES.LSTG_SITE_ID = KYLIN_CATEGORY_GROUPINGS.SITE_ID > INNER JOIN KYLIN_CAL_DT > ON KYLIN_SALES.PART_DT = KYLIN_CAL_DT.CAL_DT > GROUP BY KYLIN_CATEGORY_GROUPINGS.BSNS_VRTCL_NAME,KYLIN_CAL_DT.YEAR_BEG_DT > Currently if I am using above using query, it will give me error saying that > MAX_PRICE is not a column present in tables. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (KYLIN-1720) Apache Kylin:- Measures is not seen anywhere
[ https://issues.apache.org/jira/browse/KYLIN-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yerui Sun closed KYLIN-1720. Resolution: Information Provided > Apache Kylin:- Measures is not seen anywhere > > > Key: KYLIN-1720 > URL: https://issues.apache.org/jira/browse/KYLIN-1720 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.5.1 >Reporter: Rahul Choubey >Priority: Blocker > Attachments: image.png > > > We have created measures in cube that we have created through Kylin. > But the question is where this measures will get stored and how can I use > them when I query the cubes. I want to use these measures in my select > statement while querying the cube for e.g.:- > SELECT KYLIN_CATEGORY_GROUPINGS.BSNS_VRTCL_NAME,KYLIN_CAL_DT.YEAR_BEG_DT, > MAX_PRICE FROM KYLIN_SALES > INNER JOIN KYLIN_CATEGORY_GROUPINGS > ON KYLIN_SALES.LEAF_CATEG_ID = KYLIN_CATEGORY_GROUPINGS.LEAF_CATEG_ID AND > KYLIN_SALES.LSTG_SITE_ID = KYLIN_CATEGORY_GROUPINGS.SITE_ID > INNER JOIN KYLIN_CAL_DT > ON KYLIN_SALES.PART_DT = KYLIN_CAL_DT.CAL_DT > GROUP BY KYLIN_CATEGORY_GROUPINGS.BSNS_VRTCL_NAME,KYLIN_CAL_DT.YEAR_BEG_DT > Currently if I am using above using query, it will give me error saying that > MAX_PRICE is not a column present in tables. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1691) can not load project info from hbase when startup.
[ https://issues.apache.org/jira/browse/KYLIN-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang updated KYLIN-1691: -- Assignee: (was: hongbin ma) > can not load project info from hbase when startup. > -- > > Key: KYLIN-1691 > URL: https://issues.apache.org/jira/browse/KYLIN-1691 > Project: Kylin > Issue Type: Bug > Components: Environment >Affects Versions: v1.5.1 > Environment: Ubuntu 14 > JDK 1.7 > kylin 1.5.1 - Binary Package (for running on HBase 1.x) >Reporter: Hanhui LI > > can not load project info from hbase when startup if directory > kylin_metadata@hbase is created in $KYLIN_HOME -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1691) can not load project info from hbase when startup.
[ https://issues.apache.org/jira/browse/KYLIN-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295345#comment-15295345 ] liyang commented on KYLIN-1691: --- Please provide log and error details, or no one can help. > can not load project info from hbase when startup. > -- > > Key: KYLIN-1691 > URL: https://issues.apache.org/jira/browse/KYLIN-1691 > Project: Kylin > Issue Type: Bug > Components: Environment >Affects Versions: v1.5.1 > Environment: Ubuntu 14 > JDK 1.7 > kylin 1.5.1 - Binary Package (for running on HBase 1.x) >Reporter: Hanhui LI >Assignee: Dong Li > > can not load project info from hbase when startup if directory > kylin_metadata@hbase is created in $KYLIN_HOME -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1691) can not load project info from hbase when startup.
[ https://issues.apache.org/jira/browse/KYLIN-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang updated KYLIN-1691: -- Assignee: hongbin ma (was: Dong Li) > can not load project info from hbase when startup. > -- > > Key: KYLIN-1691 > URL: https://issues.apache.org/jira/browse/KYLIN-1691 > Project: Kylin > Issue Type: Bug > Components: Environment >Affects Versions: v1.5.1 > Environment: Ubuntu 14 > JDK 1.7 > kylin 1.5.1 - Binary Package (for running on HBase 1.x) >Reporter: Hanhui LI >Assignee: hongbin ma > > can not load project info from hbase when startup if directory > kylin_metadata@hbase is created in $KYLIN_HOME -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1707) Error When reinstall kylin
[ https://issues.apache.org/jira/browse/KYLIN-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295347#comment-15295347 ] liyang commented on KYLIN-1707: --- Please try hive shell first, seems hive is broken. > Error When reinstall kylin > -- > > Key: KYLIN-1707 > URL: https://issues.apache.org/jira/browse/KYLIN-1707 > Project: Kylin > Issue Type: Bug >Reporter: jingtao > > I want to reinstall kylin. > Then, I delete all tables in hive, >the meta table in hbase, >and remove /kylin derictory in hdfs; > Finally, I reinstall. > But, when i build cube, it error. > the message is follwing: > OS command error exit with 5 -- hive -e "USE default; > DROP TABLE IF EXISTS > kylin_intermediate_kylin_sales_cube_desc_2012010100_2016050200; > CREATE EXTERNAL TABLE IF NOT EXISTS > kylin_intermediate_kylin_sales_cube_desc_2012010100_2016050200 > ( > DEFAULT_KYLIN_SALES_PART_DT date > ,DEFAULT_KYLIN_SALES_LEAF_CATEG_ID bigint > ,DEFAULT_KYLIN_SALES_LSTG_SITE_ID int > ,DEFAULT_KYLIN_CATEGORY_GROUPINGS_META_CATEG_NAME string > ,DEFAULT_KYLIN_CATEGORY_GROUPINGS_CATEG_LVL2_NAME string > ,DEFAULT_KYLIN_CATEGORY_GROUPINGS_CATEG_LVL3_NAME string > ,DEFAULT_KYLIN_SALES_LSTG_FORMAT_NAME string > ,DEFAULT_KYLIN_SALES_PRICE decimal(19,4) > ,DEFAULT_KYLIN_SALES_SELLER_ID bigint > ) > ROW FORMAT DELIMITED FIELDS TERMINATED BY '\177' > STORED AS SEQUENCEFILE > LOCATION > '/kylin/kylin_metadata/kylin-5020d91f-3114-421b-929b-f733d438411a/kylin_intermediate_kylin_sales_cube_desc_2012010100_2016050200'; > SET dfs.replication=2; > SET dfs.block.size=33554432; > SET hive.exec.compress.output=true; > SET hive.auto.convert.join.noconditionaltask=true; > SET hive.auto.convert.join.noconditionaltask.size=3; > SET > mapreduce.map.output.compress.codec=org.apache.hadoop.io.compress.SnappyCodec; > SET > mapreduce.output.fileoutputformat.compress.codec=org.apache.hadoop.io.compress.SnappyCodec; > SET hive.merge.mapfiles=true; > SET hive.merge.mapredfiles=true; > SET mapred.output.compression.type=BLOCK; > SET hive.merge.size.per.task=25600; > SET hive.support.concurrency=false; > SET mapreduce.job.split.metainfo.maxsize=-1; > INSERT OVERWRITE TABLE > kylin_intermediate_kylin_sales_cube_desc_2012010100_2016050200 SELECT > KYLIN_SALES.PART_DT > ,KYLIN_SALES.LEAF_CATEG_ID > ,KYLIN_SALES.LSTG_SITE_ID > ,KYLIN_CATEGORY_GROUPINGS.META_CATEG_NAME > ,KYLIN_CATEGORY_GROUPINGS.CATEG_LVL2_NAME > ,KYLIN_CATEGORY_GROUPINGS.CATEG_LVL3_NAME > ,KYLIN_SALES.LSTG_FORMAT_NAME > ,KYLIN_SALES.PRICE > ,KYLIN_SALES.SELLER_ID > FROM DEFAULT.KYLIN_SALES as KYLIN_SALES > INNER JOIN DEFAULT.KYLIN_CAL_DT as KYLIN_CAL_DT > ON KYLIN_SALES.PART_DT = KYLIN_CAL_DT.CAL_DT > INNER JOIN DEFAULT.KYLIN_CATEGORY_GROUPINGS as KYLIN_CATEGORY_GROUPINGS > ON KYLIN_SALES.LEAF_CATEG_ID = KYLIN_CATEGORY_GROUPINGS.LEAF_CATEG_ID AND > KYLIN_SALES.LSTG_SITE_ID = KYLIN_CATEGORY_GROUPINGS.SITE_ID > WHERE (KYLIN_SALES.PART_DT >= '2012-01-01' AND KYLIN_SALES.PART_DT < > '2016-05-02') > ; > " > shell-init: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > shell-init: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > chdir: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > chdir: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > chdir: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > shell-init: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > chdir: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > chdir: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > chdir: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > shell-init: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > chdir: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > chdir: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > chdir: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > chdir: error retrieving current directory: getcwd: cannot access parent > directories: No such file or directory > Unable to determine Hadoop version information. > 'hadoop version' returned: > shell-init: error retrieving current directory:
[jira] [Reopened] (KYLIN-1698) Allow bigint(long) as a date partition column
[ https://issues.apache.org/jira/browse/KYLIN-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang reopened KYLIN-1698: --- Assignee: (was: hongbin ma) from 耳东 775620...@qq.com > In my opinion, kylin can change the -MM-dd and MMdd to millis. and > the cardinality is equal to the cardinality of 'MMdd' or -MM-dd. To me, it makes sense. The data format is a separate thing as to cardinality. By rounding millis to hours to days, the column can still be low in cardinality. I'm re-opening the JIRA-1698. > Allow bigint(long) as a date partition column > - > > Key: KYLIN-1698 > URL: https://issues.apache.org/jira/browse/KYLIN-1698 > Project: Kylin > Issue Type: Improvement >Affects Versions: v1.5.1 >Reporter: guohuili > > In many cases, hive tables may use long / bigint as date column. Currently > Kylin only support '-MM-dd' or 'MMdd' as date format. This jira is to > support long / bigint format. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1698) Allow bigint(long) as a date partition column
[ https://issues.apache.org/jira/browse/KYLIN-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295360#comment-15295360 ] liyang commented on KYLIN-1698: --- However by opening this option (millis as partition column), it increases the chances to create poorly designed cube having super high time cardinality. Care must be taken when providing implementation. > Allow bigint(long) as a date partition column > - > > Key: KYLIN-1698 > URL: https://issues.apache.org/jira/browse/KYLIN-1698 > Project: Kylin > Issue Type: Improvement >Affects Versions: v1.5.1 >Reporter: guohuili > > In many cases, hive tables may use long / bigint as date column. Currently > Kylin only support '-MM-dd' or 'MMdd' as date format. This jira is to > support long / bigint format. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (KYLIN-1711) Mainframe import module extension to support sequential data sets
[ https://issues.apache.org/jira/browse/KYLIN-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang closed KYLIN-1711. - Resolution: Invalid > Mainframe import module extension to support sequential data sets > - > > Key: KYLIN-1711 > URL: https://issues.apache.org/jira/browse/KYLIN-1711 > Project: Kylin > Issue Type: Improvement >Reporter: Chris >Priority: Minor > > The current SQOOP-1272 supports partitioned data sets only. It does not > support sequential data sets. Please raise Improvement JIRA as a proposed > patch to SQOOP-1272. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (KYLIN-1709) Shiro - onSuccessfulLogin shiro adds two entries in the response header for remember me cookie.
[
https://issues.apache.org/jira/browse/KYLIN-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liyang closed KYLIN-1709.
-
Resolution: Invalid
> Shiro - onSuccessfulLogin shiro adds two entries in the response header for
> remember me cookie.
>
>
> Key: KYLIN-1709
> URL: https://issues.apache.org/jira/browse/KYLIN-1709
> Project: Kylin
> Issue Type: Improvement
> Components: General, Web
>Affects Versions: v1.2
>Reporter: amit yatagiri
>Assignee: Zhong,Jason
> Labels: shiro,
>
> On successful login, shiro adds two cookie entries one with deleteMe as value
> and other with the encrypted value.
> Though delete-me value cookie has expired state, it should not be resent in
> the header. As per the cookie spec, order of the response header should not
> be relied upon.
> class : AbstractRememberMeManager
> method :
> public void onSuccessfulLogin(Subject subject, AuthenticationToken token,
> AuthenticationInfo info) {
> //always clear any previous identity:
> forgetIdentity(subject);
> //now save the new identity:
> if (isRememberMe(token)) {
> rememberIdentity(subject, token, info);
> } else {
> if (log.isDebugEnabled()) {
> log.debug("AuthenticationToken did not indicate RememberMe is
> requested. " +
> "RememberMe functionality will not be executed for
> corresponding account.");
> }
> }
> }
> In the above code, forget identity happens every time. Better place is in the
> else condition(when isNotRememberMe).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KYLIN-1712) Measures are not getting Calculated after the cube built successfully.
[ https://issues.apache.org/jira/browse/KYLIN-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295370#comment-15295370 ] liyang commented on KYLIN-1712: --- Pls specify the aggr func or group by. Kylin does not store raw records, so what 'select * from fact' returns is some kinda mockup result. > Measures are not getting Calculated after the cube built successfully. > -- > > Key: KYLIN-1712 > URL: https://issues.apache.org/jira/browse/KYLIN-1712 > Project: Kylin > Issue Type: Bug > Components: Client - CLI, General >Affects Versions: v1.5.1 >Reporter: Bhanuprakash > Attachments: screenshot-1.png, screenshot-2.png > > > After the Cube built successfully, we had triggered the below Query to > display complete result set from fact_table. we did'nt find the calculated > results for Measures and also the measure names differed from Actual defined > measures. > select * from KYLIN_SALES -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1721) KylinConfigExt lost base properties when store into file
[
https://issues.apache.org/jira/browse/KYLIN-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295383#comment-15295383
]
liyang commented on KYLIN-1721:
---
Nice catch!! This is critical. Need to patch 1.5.2 release.
> KylinConfigExt lost base properties when store into file
>
>
> Key: KYLIN-1721
> URL: https://issues.apache.org/jira/browse/KYLIN-1721
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
>Affects Versions: v1.5.2
>Reporter: Yerui Sun
>Assignee: Yerui Sun
>Priority: Critical
> Fix For: v1.5.2
>
>
> KylinConfigExt overrides getAllProperties() to merge the base properties and
> the override properties into one Properties, which used to get config or
> write into file.
> In the following code, super properties stored in Properties.*defaults*,
> which will *NOT* written out by store() method, quoted from [java
> document|https://docs.oracle.com/javase/7/docs/api/java/util/Properties.html#store(java.io.OutputStream,%20java.lang.String)].
> That will lost super properties when store KylinConfigExt into file.
> {code}
> protected Properties getAllProperties() {
> Properties result = new Properties(super.getAllProperties());
> result.putAll(overrides);
> return result;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KYLIN-1722) IntegerDimEnc serialization exception inside coprocessor
liyang created KYLIN-1722: - Summary: IntegerDimEnc serialization exception inside coprocessor Key: KYLIN-1722 URL: https://issues.apache.org/jira/browse/KYLIN-1722 Project: Kylin Issue Type: Bug Affects Versions: v1.5.1 Reporter: liyang Caused by: java.io.InvalidClassException: org.apache.kylin.dimension.IntegerDimEnc; local class incompatible: stream classdesc serialVersionUID = -6997498954468581790, local class serialVersionUID = -1616935732097012877 at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:617) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1622) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at org.apache.kylin.cube.gridtable.TrimmedCubeCodeSystem.readDimensionEncoding(TrimmedCubeCodeSystem.java:85) ... 18 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-1722) IntegerDimEnc serialization exception inside coprocessor
[ https://issues.apache.org/jira/browse/KYLIN-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang resolved KYLIN-1722. --- Resolution: Fixed Assignee: liyang Fix Version/s: v1.5.2 > IntegerDimEnc serialization exception inside coprocessor > > > Key: KYLIN-1722 > URL: https://issues.apache.org/jira/browse/KYLIN-1722 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.5.1 >Reporter: liyang >Assignee: liyang > Fix For: v1.5.2 > > > Caused by: java.io.InvalidClassException: > org.apache.kylin.dimension.IntegerDimEnc; local class incompatible: stream > classdesc serialVersionUID = -6997498954468581790, local class > serialVersionUID = -1616935732097012877 > at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:617) > at > java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1622) > at > java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517) > at > java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) > at > org.apache.kylin.cube.gridtable.TrimmedCubeCodeSystem.readDimensionEncoding(TrimmedCubeCodeSystem.java:85) > ... 18 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
