[GitHub] chenzhx closed pull request #162: KYLIN-3440 Couldn't merge if there is an empty segment

chenzhx closed pull request #162: KYLIN-3440 Couldn't merge if there is an empty segment URL: https://github.com/apache/kylin/pull/162 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a

[GitHub] chenzhx closed pull request #163: KYLIN-3440 Couldn't merge if there is an empty segment

chenzhx closed pull request #163: KYLIN-3440 Couldn't merge if there is an empty segment URL: https://github.com/apache/kylin/pull/163 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a

[GitHub] luguosheng1314 opened a new pull request #163: KYLIN-3440 Couldn't merge if there is an empty segment

luguosheng1314 opened a new pull request #163: KYLIN-3440 Couldn't merge if there is an empty segment URL: https://github.com/apache/kylin/pull/163 This is an automated message from the Apache Git Service. To respond to the

[GitHub] asfgit commented on issue #163: KYLIN-3440 Couldn't merge if there is an empty segment

asfgit commented on issue #163: KYLIN-3440 Couldn't merge if there is an empty segment URL: https://github.com/apache/kylin/pull/163#issuecomment-402378366 Can one of the admins verify this patch? This is an automated message

[GitHub] coveralls commented on issue #161: KYLIN-3440 Couldn't merge if there is an empty segment

coveralls commented on issue #161: KYLIN-3440 Couldn't merge if there is an empty segment URL: https://github.com/apache/kylin/pull/161#issuecomment-402378231 ## Pull Request Test Coverage Report for [Build 3288](https://coveralls.io/builds/17825011) * **0** of **0** changed or ad

[GitHub] luguosheng1314 opened a new pull request #162: KYLIN-3440 Couldn't merge if there is an empty segment

luguosheng1314 opened a new pull request #162: KYLIN-3440 Couldn't merge if there is an empty segment URL: https://github.com/apache/kylin/pull/162 This is an automated message from the Apache Git Service. To respond to the

[GitHub] asfgit commented on issue #162: KYLIN-3440 Couldn't merge if there is an empty segment

asfgit commented on issue #162: KYLIN-3440 Couldn't merge if there is an empty segment URL: https://github.com/apache/kylin/pull/162#issuecomment-402377982 Can one of the admins verify this patch? This is an automated message

[GitHub] chenzhx closed pull request #161: KYLIN-3440 Couldn't merge if there is an empty segment

chenzhx closed pull request #161: KYLIN-3440 Couldn't merge if there is an empty segment URL: https://github.com/apache/kylin/pull/161 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a

[GitHub] luguosheng1314 opened a new pull request #161: KYLIN-3440 Couldn't merge if there is an empty segment

luguosheng1314 opened a new pull request #161: KYLIN-3440 Couldn't merge if there is an empty segment URL: https://github.com/apache/kylin/pull/161 This is an automated message from the Apache Git Service. To respond to the

[GitHub] asfgit commented on issue #161: KYLIN-3440 Couldn't merge if there is an empty segment

asfgit commented on issue #161: KYLIN-3440 Couldn't merge if there is an empty segment URL: https://github.com/apache/kylin/pull/161#issuecomment-402374758 Can one of the admins verify this patch? This is an automated message

Re: How to configure the default data type measure decimal(19, 4)?

Hi, forget to mention, please delete the "signature" property in JSON when you do a manual modification. Kylin doesn't expect the user to manually modify metadata, so adding this check. My method is a hack way (not practice), you need to take the risk on your own. Always taking a backup before doin

[jira] [Created] (KYLIN-3440) Couldn't merge if there is an empty segment

Shaofeng SHI created KYLIN-3440: --- Summary: Couldn't merge if there is an empty segment Key: KYLIN-3440 URL: https://issues.apache.org/jira/browse/KYLIN-3440 Project: Kylin Issue Type: Bug

Re: How to configure the default data type measure decimal(19, 4)?

So I have restored and restarted kylin and I can see that the data type has been changed to decimal(19,6). When I try to build the cube it says, it gives me an error saying that "inconsistent cubedesc_signature". Is there anything I should do for that? -- Sent from: http://apache-kylin.74782.x6.na

Re: How to configure the default data type measure decimal(19, 4)?

Hi, So I have changed the json file of my cube after taking the backup and now do I have to restore to see the change? -- Sent from: http://apache-kylin.74782.x6.nabble.com/

Re: How to configure the default data type measure decimal(19, 4)?

Hi Neethu, I just realized these configurations are used when there is no defined scale and precision, such as "decimal"; If the scale and precision is presented, the parameter has no effect. So far there is no way for the user to modify the return type on GUI, but you can workaround by modifying

Re: How to configure the default data type measure decimal(19, 4)?

One doubt, when I am creating the cube, I see the default type of the measure is decimal(19,4). Will it change after I build the cube? -- Sent from: http://apache-kylin.74782.x6.nabble.com/

Re: How to configure the default data type measure decimal(19, 4)?

Yes, I have sync the hive table again and seems to take the default decimal(19,4). -- Sent from: http://apache-kylin.74782.x6.nabble.com/

Re: How to configure the default data type measure decimal(19, 4)?

Hi, did you re-sync the table from Hive to Kylin? If not, please re-sync it. 2018-07-03 17:23 GMT+08:00 mvneethu : > Hi, > Thanks for your response. I have configured the kylin.properties file with > kylin.source.hive.default-decimal-scale=6 > kylin.source.hive.default-decimal-precision=19 > and

Re: How to configure the default data type measure decimal(19, 4)?

Hi, Thanks for your response. I have configured the kylin.properties file with kylin.source.hive.default-decimal-scale=6 kylin.source.hive.default-decimal-precision=19 and restarted kylin. But still I get the default as decimal(19,4). Please help. -- Sent from: http://apache-kylin.74782.x6.nabble

[jira] [Created] (KYLIN-3439) configuration "kylin.web.timezone" is Inconsistent between kylin-defaults.properties and KylinConfigBase.java

jiatao.tao created KYLIN-3439: - Summary: configuration "kylin.web.timezone" is Inconsistent between kylin-defaults.properties and KylinConfigBase.java Key: KYLIN-3439 URL: https://issues.apache.org/jira/browse/KYLIN-