[jira] [Updated] (KYLIN-1920) Add view CubeInstance json function
[ https://issues.apache.org/jira/browse/KYLIN-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1920: - Attachment: 0001-KYLIN-1920-web.patch I have completed this function.Please check this patch.Thanks! > Add view CubeInstance json function > --- > > Key: KYLIN-1920 > URL: https://issues.apache.org/jira/browse/KYLIN-1920 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v1.5.2 >Reporter: Zhong,Jason >Assignee: Zhong,Jason > Attachments: 0001-KYLIN-1920-web.patch > > > Now at cube list page we can edit CubeDesc json file, we also need to view > CubeInstance json, need to add this to UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1194) Filter(CubeName) on Jobs/Monitor page works only once
[ https://issues.apache.org/jira/browse/KYLIN-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1194: - Attachment: 0001-KYLIN-1194-web-fix-filter-cubes-issue.patch > Filter(CubeName) on Jobs/Monitor page works only once > - > > Key: KYLIN-1194 > URL: https://issues.apache.org/jira/browse/KYLIN-1194 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.4.0, v1.1.1 >Reporter: Dong Li >Assignee: Zhong,Jason >Priority: Minor > Attachments: 0001-KYLIN-1194-web-fix-filter-cubes-issue.patch > > > 1. Navigate to: http://localhost:7070/kylin/jobs > 2. Entry a valid cube name in Cube name textbox, and press Enter to filter, > found there're jobs displayed > 3. Clear the textbox, and press Enter. > Actual: No jobs display > Expect: All jobs should display -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KYLIN-1194) Filter(CubeName) on Jobs/Monitor page works only once
[ https://issues.apache.org/jira/browse/KYLIN-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391251#comment-15391251 ] Zhixiong Chen edited comment on KYLIN-1194 at 7/25/16 3:00 AM: --- I have fixed this issue.Please check this patch .Thanks! was (Author: zhixiong chen): I have fixed this issue.Please check this patch .Thanks! > Filter(CubeName) on Jobs/Monitor page works only once > - > > Key: KYLIN-1194 > URL: https://issues.apache.org/jira/browse/KYLIN-1194 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.4.0, v1.1.1 >Reporter: Dong Li >Assignee: Zhong,Jason >Priority: Minor > Attachments: 0001-KYLIN-1194-web-fix-filter-cubes-issue.patch > > > 1. Navigate to: http://localhost:7070/kylin/jobs > 2. Entry a valid cube name in Cube name textbox, and press Enter to filter, > found there're jobs displayed > 3. Clear the textbox, and press Enter. > Actual: No jobs display > Expect: All jobs should display -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1194) Filter(CubeName) on Jobs/Monitor page works only once
[ https://issues.apache.org/jira/browse/KYLIN-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1194: - Attachment: 0001-KYLIN-1194-web-fix-filter-issue.patch.patch I have fixed this issue.Please check this patch .Thanks! > Filter(CubeName) on Jobs/Monitor page works only once > - > > Key: KYLIN-1194 > URL: https://issues.apache.org/jira/browse/KYLIN-1194 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.4.0, v1.1.1 >Reporter: Dong Li >Assignee: Zhong,Jason >Priority: Minor > Attachments: 0001-KYLIN-1194-web-fix-filter-issue.patch.patch > > > 1. Navigate to: http://localhost:7070/kylin/jobs > 2. Entry a valid cube name in Cube name textbox, and press Enter to filter, > found there're jobs displayed > 3. Clear the textbox, and press Enter. > Actual: No jobs display > Expect: All jobs should display -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1848) Can't sort cubes by any field in Web UI
[ https://issues.apache.org/jira/browse/KYLIN-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1848: - Attachment: 0001-KYLIN-1848-web-fix-sort-cubes-issue.patch I have fixed this and created a patch, please help review, thanks! > Can't sort cubes by any field in Web UI > --- > > Key: KYLIN-1848 > URL: https://issues.apache.org/jira/browse/KYLIN-1848 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.5.2 >Reporter: Dayue Gao >Assignee: Zhong,Jason > Attachments: 0001-KYLIN-1848-web-fix-sort-cubes-issue.patch > > > In a project containing dozens of cubes, it's helpful to sort cubes by fields > like "Create Time", "Status", and so on. I tried it today but found it's not > working, could we fix it? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1488) When modifying a model, Save after deleting a lookup table. The internal error will pop up.
[
https://issues.apache.org/jira/browse/KYLIN-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15403579#comment-15403579
]
Zhixiong Chen commented on KYLIN-1488:
--
As if there is an error in your patch :
if (model.cubes.length == 0) {
$location.path("/models/edit/"+model.name);
}else{
for(var i = 0; i < model.cubes.length; i++){
cubename[i] = model.cubes[i].name;
}
SweetAlert.swal('sorry','this is model still be used by '+
cubename.join(','));
}
,
even if disable a cube ,however the model.cubes still include this cube,so it
will pop up "sorry,this is model..."
> When modifying a model, Save after deleting a lookup table. The internal
> error will pop up.
> ---
>
> Key: KYLIN-1488
> URL: https://issues.apache.org/jira/browse/KYLIN-1488
> Project: Kylin
> Issue Type: Bug
> Components: Web
>Reporter: Zhong Yanghong
>Assignee: Zhong,Jason
> Attachments: modelEditFuc-modify.patch
>
>
> In case of modifying a model which is already used by some cubes, users can
> delete the lookup table and do the "Save" operation. However, after it's
> done, the internal error will pop up.
> In normal case, if the model is used by some cubes, we cannot modify the
> model without disable or drop those cubes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (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 ] Zhixiong Chen updated KYLIN-2445: - Attachment: 0001-KYLIN-2445-UI-select-cube-engine-in-Advanced-setting.patch I have completed this issue.Please check it.Thanks! > 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 > > Attachments: > 0001-KYLIN-2445-UI-select-cube-engine-in-Advanced-setting.patch > > > 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-2370) Refine unload table
[ https://issues.apache.org/jira/browse/KYLIN-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2370: - Attachment: 0001-KYLIN-2370-Refine-unload-and-reload-table.patch I have completed this issue.Please check it.Thanks! > Refine unload table > --- > > Key: KYLIN-2370 > URL: https://issues.apache.org/jira/browse/KYLIN-2370 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Zhixiong Chen >Assignee: Zhixiong Chen > Attachments: 0001-KYLIN-2370-Refine-unload-and-reload-table.patch > > > Move the Unload Button to the Table level . > Add a reload button side by side. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1904) WebUI for GlobalDictionary
[ https://issues.apache.org/jira/browse/KYLIN-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1904: - Attachment: 0001-KYLIN-1904-WEB-Global-Dictionary.patch I have fixed this issue.Please check it .Thanks. > WebUI for GlobalDictionary > -- > > Key: KYLIN-1904 > URL: https://issues.apache.org/jira/browse/KYLIN-1904 > Project: Kylin > Issue Type: Improvement > Components: Metadata >Affects Versions: v1.5.3 >Reporter: Yerui Sun >Assignee: Zhong,Jason > Fix For: Backlog > > Attachments: 0001-KYLIN-1904-WEB-Global-Dictionary.patch > > > Global Dictionary is introduced since v1.5.3. However, there's no Web UI to > config with Global Dict, it's not convenience for users. > The use case can be found in > examples/test_case_data/localmeta/cube_desc/test_kylin_cube_without_slr_left_join_desc.json, > the "dictionaries" arrays. > One Global Dict config may contains three elements, "column", the column to > generate dict, "builder", the builder to build dict, and "reuse", the column > to be reused. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1965) Check duplicated measure name
[ https://issues.apache.org/jira/browse/KYLIN-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1965: - Attachment: (was: 0001-KYLIN-1965-UPDATE.patch) > Check duplicated measure name > - > > Key: KYLIN-1965 > URL: https://issues.apache.org/jira/browse/KYLIN-1965 > Project: Kylin > Issue Type: Improvement > Components: Metadata >Affects Versions: v1.5.2, v1.5.3 >Reporter: kangkaisen >Assignee: kangkaisen > Fix For: v1.5.4 > > Attachments: KYLIN-1965-bug-fix.patch, KYLIN-1965.patch > > > The duplicated measure's name will lead to query failed, so we should check > duplicated measure name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1698) Allow bigint(long) as a partition date column
[ https://issues.apache.org/jira/browse/KYLIN-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1698: - Attachment: 0001-KYLIN-1698-BIGINT.patch > Allow bigint(long) as a partition date 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 > Attachments: 0001-KYLIN-1698-BIGINT.patch > > > 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] [Updated] (KYLIN-1926) Loosen the constraint on FK-PK data type matching
[ https://issues.apache.org/jira/browse/KYLIN-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1926: - Attachment: 0001-KYLIN-1926-FK-PK-data-type-matching.patch > Loosen the constraint on FK-PK data type matching > - > > Key: KYLIN-1926 > URL: https://issues.apache.org/jira/browse/KYLIN-1926 > Project: Kylin > Issue Type: Improvement > Components: Metadata >Affects Versions: all >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI >Priority: Minor > Fix For: v1.5.4 > > Attachments: 0001-KYLIN-1926-FK-PK-data-type-matching.patch > > > If lookup table's PK datatype isn't equal to fact table's FK datatype, Kylin > will report error saying "Primary key are not consistent with Foreign key". > This constraint is too strong. Should allow user to disable this check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1926) Loosen the constraint on FK-PK data type matching
[ https://issues.apache.org/jira/browse/KYLIN-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1926: - Attachment: 0001-KYLIN-1926-FK-PK-data-type-matching.patch > Loosen the constraint on FK-PK data type matching > - > > Key: KYLIN-1926 > URL: https://issues.apache.org/jira/browse/KYLIN-1926 > Project: Kylin > Issue Type: Improvement > Components: Metadata >Affects Versions: all >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI >Priority: Minor > Fix For: v1.5.4 > > Attachments: 0001-KYLIN-1926-FK-PK-data-type-matching.patch > > > If lookup table's PK datatype isn't equal to fact table's FK datatype, Kylin > will report error saying "Primary key are not consistent with Foreign key". > This constraint is too strong. Should allow user to disable this check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1926) Loosen the constraint on FK-PK data type matching
[ https://issues.apache.org/jira/browse/KYLIN-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1926: - Attachment: (was: 0001-KYLIN-1926-FK-PK-data-type-matching.patch) > Loosen the constraint on FK-PK data type matching > - > > Key: KYLIN-1926 > URL: https://issues.apache.org/jira/browse/KYLIN-1926 > Project: Kylin > Issue Type: Improvement > Components: Metadata >Affects Versions: all >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI >Priority: Minor > Fix For: v1.5.4 > > > If lookup table's PK datatype isn't equal to fact table's FK datatype, Kylin > will report error saying "Primary key are not consistent with Foreign key". > This constraint is too strong. Should allow user to disable this check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1698) Allow bigint(long) as a partition date column
[ https://issues.apache.org/jira/browse/KYLIN-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1698: - Attachment: 0001-KYLIN-1698-INT.patch > Allow bigint(long) as a partition date 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 > Attachments: 0001-KYLIN-1698-BIGINT.patch, 0001-KYLIN-1698-INT.patch > > > 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] [Updated] (KYLIN-1767) Update UI for TopN: specify encoding and multiple "group by"
[ https://issues.apache.org/jira/browse/KYLIN-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1767: - Attachment: 0001-KYLIN-1767-WEB-UI-FOR-TOPN.patch I have completed the upgrade.Please check it. Thanks. > Update UI for TopN: specify encoding and multiple "group by" > > > Key: KYLIN-1767 > URL: https://issues.apache.org/jira/browse/KYLIN-1767 > Project: Kylin > Issue Type: Task > Components: Web >Reporter: Shaofeng SHI >Assignee: Zhong,Jason > Fix For: v1.5.4 > > Attachments: 0001-KYLIN-1767-WEB-UI-FOR-TOPN.patch > > > KYLIN-1478 and KYLIN-1693 need changes from the UI part. The sample json can > be found in these two JIRAs; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1997) add pivot feature back in query result page
[ https://issues.apache.org/jira/browse/KYLIN-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1997: - Attachment: 0001-KYLIN-1997-add-pivot-feature-back-in-query-result-pa.patch I have fixed this issue.Please check it.Thanks. > add pivot feature back in query result page > --- > > Key: KYLIN-1997 > URL: https://issues.apache.org/jira/browse/KYLIN-1997 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v1.5.2 >Reporter: Zhong,Jason >Assignee: Zhong,Jason > Attachments: > 0001-KYLIN-1997-add-pivot-feature-back-in-query-result-pa.patch > > > from KYLIN-989 we replace ng-grid with ui-grid > which cause lose pivot feature, need to add it back -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1928) Query elapsed time not shown when query returns 0 result
[ https://issues.apache.org/jira/browse/KYLIN-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1928: - Attachment: 0001-KYLIN-1928-Query-elapsed-time-not-shown-when-query-r.patch I have fixed this bug.Please check it .Thanks! > Query elapsed time not shown when query returns 0 result > > > Key: KYLIN-1928 > URL: https://issues.apache.org/jira/browse/KYLIN-1928 > Project: Kylin > Issue Type: Improvement >Reporter: hongbin ma >Assignee: Zhong,Jason > Attachments: > 0001-KYLIN-1928-Query-elapsed-time-not-shown-when-query-r.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1698) Allow bigint(long) as a partition date column
[ https://issues.apache.org/jira/browse/KYLIN-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1698: - Attachment: (was: 0001-KYLIN-1698-INT.patch) > Allow bigint(long) as a partition date 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 > Attachments: 0001-KYLIN-1698-BIGINT.patch > > > 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] [Updated] (KYLIN-1698) Allow bigint(long) as a partition date column
[ https://issues.apache.org/jira/browse/KYLIN-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1698: - Attachment: 0001-KYLIN-1698-INT.patch > Allow bigint(long) as a partition date 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 > Attachments: 0001-KYLIN-1698-BIGINT.patch, 0001-KYLIN-1698-INT.patch > > > 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] [Updated] (KYLIN-1488) When modifying a model, Save after deleting a lookup table. The internal error will pop up.
[ https://issues.apache.org/jira/browse/KYLIN-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1488: - Attachment: (was: 0001-KYLIN-1488-modify-model-issue.patch) > When modifying a model, Save after deleting a lookup table. The internal > error will pop up. > --- > > Key: KYLIN-1488 > URL: https://issues.apache.org/jira/browse/KYLIN-1488 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Zhong Yanghong >Assignee: Zhong,Jason > Attachments: modelEditFuc-modify.patch > > > In case of modifying a model which is already used by some cubes, users can > delete the lookup table and do the "Save" operation. However, after it's > done, the internal error will pop up. > In normal case, if the model is used by some cubes, we cannot modify the > model without disable or drop those cubes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1866) add tip for field at 'Add Streaming' table page.
[ https://issues.apache.org/jira/browse/KYLIN-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1866: - Attachment: 0001-KYLIN-1866-web-add-streaming-tip-issue.patch I have fixed this issue.Please check this patch.Thanks! > add tip for field at 'Add Streaming' table page. > > > Key: KYLIN-1866 > URL: https://issues.apache.org/jira/browse/KYLIN-1866 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v1.5.2.1 >Reporter: Zhong,Jason >Assignee: Zhong,Jason > Attachments: 0001-KYLIN-1866-web-add-streaming-tip-issue.patch > > > when add streaming table in kylin,we have 'Add Straming' table page, > but user may not understand some specific words, need to add tip for user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1488) When modifying a model, Save after deleting a lookup table. The internal error will pop up.
[ https://issues.apache.org/jira/browse/KYLIN-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1488: - Attachment: 0001-KYLIN-1488-web-modify-model-issue.patch > When modifying a model, Save after deleting a lookup table. The internal > error will pop up. > --- > > Key: KYLIN-1488 > URL: https://issues.apache.org/jira/browse/KYLIN-1488 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Zhong Yanghong >Assignee: Zhong,Jason > Attachments: 0001-KYLIN-1488-web-modify-model-issue.patch, > modelEditFuc-modify.patch > > > In case of modifying a model which is already used by some cubes, users can > delete the lookup table and do the "Save" operation. However, after it's > done, the internal error will pop up. > In normal case, if the model is used by some cubes, we cannot modify the > model without disable or drop those cubes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1904) WebUI for GlobalDictionary
[ https://issues.apache.org/jira/browse/KYLIN-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1904: - Attachment: 0001-KYLIN-1904-WBE-DICTIONARY-UPDATE.patch > WebUI for GlobalDictionary > -- > > Key: KYLIN-1904 > URL: https://issues.apache.org/jira/browse/KYLIN-1904 > Project: Kylin > Issue Type: Improvement > Components: Metadata >Affects Versions: v1.5.3 >Reporter: Yerui Sun >Assignee: Zhong,Jason > Fix For: v1.5.4 > > Attachments: 0001-KYLIN-1904-WBE-DICTIONARY-UPDATE.patch, > 0001-KYLIN-1904-WEB-Global-Dictionary.patch > > > Global Dictionary is introduced since v1.5.3. However, there's no Web UI to > config with Global Dict, it's not convenience for users. > The use case can be found in > examples/test_case_data/localmeta/cube_desc/test_kylin_cube_without_slr_left_join_desc.json, > the "dictionaries" arrays. > One Global Dict config may contains three elements, "column", the column to > generate dict, "builder", the builder to build dict, and "reuse", the column > to be reused. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1820) Column autocomplete should remove the user input in model designer
[ https://issues.apache.org/jira/browse/KYLIN-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1820: - Attachment: 0001-KYLIN-1820-Column-autocomplete-should-remove-the-use.patch I have fixed this bug.Please check it. thanks! > Column autocomplete should remove the user input in model designer > -- > > Key: KYLIN-1820 > URL: https://issues.apache.org/jira/browse/KYLIN-1820 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.5.2 > Environment: OS:Mac > Safari/Chrome >Reporter: Billy(Yiming) Liu >Assignee: Zhong,Jason >Priority: Minor > Fix For: Backlog > > Attachments: > 0001-KYLIN-1820-Column-autocomplete-should-remove-the-use.patch > > > In step 3 add column dimension in Model Designer, user enters the column name > and the column name autocompletion pops up. When some item is selected, the > column name shows in the textbox. At this time, the selected column should > replace the user input, not insert before the user input. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1321) Add derived checkbox for lookup table columns on Auto Generate Dimensions panel
[ https://issues.apache.org/jira/browse/KYLIN-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1321: - Attachment: 0001-KYLIN-1321-Add-derived-checkbox-for-lookup-table-col.patch I have fixed this issue.Please check it .Thanks. > Add derived checkbox for lookup table columns on Auto Generate Dimensions > panel > --- > > Key: KYLIN-1321 > URL: https://issues.apache.org/jira/browse/KYLIN-1321 > Project: Kylin > Issue Type: Task > Components: Web >Affects Versions: v1.4.0 >Reporter: Lola Liu >Assignee: Zhong,Jason > Fix For: Backlog > > Attachments: > 0001-KYLIN-1321-Add-derived-checkbox-for-lookup-table-col.patch, auto > generate dimensions.png > > > Currently auto generate dimensions in lookup table are derived. > 1. Add derived checkbox for lookup table dimensions > 2. Add explanation for derived concept, link to kylin document -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2158) Delete joint dimension not right
[ https://issues.apache.org/jira/browse/KYLIN-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2158: - Attachment: 0001-KYLIN-2158-Delete-joint-dimension-not-right.patch I have fixed this bug.Please check it .Thanks! > Delete joint dimension not right > > > Key: KYLIN-2158 > URL: https://issues.apache.org/jira/browse/KYLIN-2158 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.5.4.1 >Reporter: Zhong,Jason >Assignee: Zhong,Jason > Attachments: 0001-KYLIN-2158-Delete-joint-dimension-not-right.patch > > > Say I create multiple joints in aggregation group, > when I delete one joint group, it always delete the last one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2090) Allow updating cube level config even the cube is ready
[ https://issues.apache.org/jira/browse/KYLIN-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2090: - Attachment: 0001-KYLIN-2090-Allow-updating-cube-level-config-even-the.patch I have completed this issue.Please checked it .Thanks! > Allow updating cube level config even the cube is ready > --- > > Key: KYLIN-2090 > URL: https://issues.apache.org/jira/browse/KYLIN-2090 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Shaofeng SHI >Assignee: Zhong,Jason > Fix For: Backlog > > Attachments: > 0001-KYLIN-2090-Allow-updating-cube-level-config-even-the.patch > > > Now once a Cube be built to "ready" state, user will not be able to update > it, including changing the cube level configurations, this is bad; as > sometimes user may want to add/change the config. > It should be designed as the "Notification List": user can change at anytime, > and it doesn't impact other things. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2052) Edit "Top N" measure, the "group by" column wasn't displayed
[ https://issues.apache.org/jira/browse/KYLIN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2052: - Attachment: 0001-KYLIN-2052-the-group-by-column-wasn-t-displayed.patch I have fixed this bug.Please check it.Thanks. > Edit "Top N" measure, the "group by" column wasn't displayed > > > Key: KYLIN-2052 > URL: https://issues.apache.org/jira/browse/KYLIN-2052 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.5.4, v1.5.4.1 >Reporter: Shaofeng SHI >Assignee: Zhong,Jason >Priority: Minor > Attachments: > 0001-KYLIN-2052-the-group-by-column-wasn-t-displayed.patch, Screen Shot > 2016-09-26 at 2.12.52 PM.png, Screen Shot 2016-09-26 at 2.13.02 PM.png > > > When edit the "kylin_sales" cube, in the measure page, click "Edit" button on > the "Top Seller" measure, the "group by" column list is empty, "seller_id" > wasn't recognized well; If click "Save" directly, Kylin will report error. > See the screen shot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1683) Row key could drag and drop in view state of cube - advanced settings tabpage
[ https://issues.apache.org/jira/browse/KYLIN-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1683: - Attachment: 0001-KYLIN-1683-Row-key-could-drag-and-drop-in-view-state.patch I have fixed this bug.Please check it.Thanks! > Row key could drag and drop in view state of cube - advanced settings tabpage > - > > Key: KYLIN-1683 > URL: https://issues.apache.org/jira/browse/KYLIN-1683 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.5.1 >Reporter: Dong Li >Assignee: Zhong,Jason >Priority: Minor > Attachments: > 0001-KYLIN-1683-Row-key-could-drag-and-drop-in-view-state.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2370) Refine unload table
Zhixiong Chen created KYLIN-2370: Summary: Refine unload table Key: KYLIN-2370 URL: https://issues.apache.org/jira/browse/KYLIN-2370 Project: Kylin Issue Type: Improvement Components: Web Reporter: Zhixiong Chen Assignee: Zhixiong Chen Move the Unload Button to the Table level . Add a reload button side by side. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2370) Refine unload table
[ https://issues.apache.org/jira/browse/KYLIN-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2370: - Attachment: 0001-KYLIN-2370-Refine-unload-and-reload-table.patch I have fixed this issue.Please check it .Thanks! > Refine unload table > --- > > Key: KYLIN-2370 > URL: https://issues.apache.org/jira/browse/KYLIN-2370 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Zhixiong Chen >Assignee: Zhixiong Chen > Attachments: 0001-KYLIN-2370-Refine-unload-and-reload-table.patch > > > Move the Unload Button to the Table level . > Add a reload button side by side. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2370) Refine unload table
[ https://issues.apache.org/jira/browse/KYLIN-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2370: - Attachment: (was: 0001-KYLIN-2370-Refine-unload-and-reload-table.patch) > Refine unload table > --- > > Key: KYLIN-2370 > URL: https://issues.apache.org/jira/browse/KYLIN-2370 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Zhixiong Chen >Assignee: Zhixiong Chen > > Move the Unload Button to the Table level . > Add a reload button side by side. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (KYLIN-2370) Refine unload table
[ https://issues.apache.org/jira/browse/KYLIN-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2370: - Comment: was deleted (was: I have fixed this issue.Please check it .Thanks!) > Refine unload table > --- > > Key: KYLIN-2370 > URL: https://issues.apache.org/jira/browse/KYLIN-2370 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Zhixiong Chen >Assignee: Zhixiong Chen > > Move the Unload Button to the Table level . > Add a reload button side by side. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2544) lookup table show wrong join type
[ https://issues.apache.org/jira/browse/KYLIN-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2544: - Component/s: Web > lookup table show wrong join type > - > > Key: KYLIN-2544 > URL: https://issues.apache.org/jira/browse/KYLIN-2544 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Zhixiong Chen >Assignee: Zhixiong Chen > > lookup table show wrong join type,when edit a left join lookup table -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2769) Non-partitioned cube doesn't need show start/end time
[ https://issues.apache.org/jira/browse/KYLIN-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2769: - Attachment: 0001-KYLIN-2769-Non-partitioned-cube-not-show-start-and-e.patch I have fix this bug.Please check it. Thanks! > Non-partitioned cube doesn't need show start/end time > - > > Key: KYLIN-2769 > URL: https://issues.apache.org/jira/browse/KYLIN-2769 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2769-Non-partitioned-cube-not-show-start-and-e.patch, 屏幕快照 > 2017-07-30 下午3.34.33.png > > > Create a non-partitioned cube, after build, the "Storage" section shows > invalid characters, see the attachment. actually there is no need to show the > start/end time for non-partitioned cube. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2768) Wrong UI for count distinct measure
[ https://issues.apache.org/jira/browse/KYLIN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16106375#comment-16106375 ] Zhixiong Chen commented on KYLIN-2768: -- Yes.It is for "multiple columns" support for count distinct.I will update the lable later. > Wrong UI for count distinct measure > --- > > Key: KYLIN-2768 > URL: https://issues.apache.org/jira/browse/KYLIN-2768 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > Attachments: 屏幕快照 2017-07-30 下午3.16.41.png > > > I made a build from 2.1.x branch, when create a count distinct measure, it > shows "Group by Column" input widget (se attachement). This is strange, as > embeded "group by column" is just in the "TopN" case, not applicable for > count distinct. > Is it for "multiple columns" support for count distinct? if so, the lable > need be updated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2768) Wrong UI for count distinct measure
[ https://issues.apache.org/jira/browse/KYLIN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2768: - Attachment: 0001-KYLIN-2768-wrong-UI-for-count-distinct-measure.patch I have fixed this bug.Please check it.Thanks! > Wrong UI for count distinct measure > --- > > Key: KYLIN-2768 > URL: https://issues.apache.org/jira/browse/KYLIN-2768 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2768-wrong-UI-for-count-distinct-measure.patch, 屏幕快照 2017-07-30 > 下午3.16.41.png > > > I made a build from 2.1.x branch, when create a count distinct measure, it > shows "Group by Column" input widget (se attachement). This is strange, as > embeded "group by column" is just in the "TopN" case, not applicable for > count distinct. > Is it for "multiple columns" support for count distinct? if so, the lable > need be updated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2769) Non-partitioned cube doesn't need show start/end time
[ https://issues.apache.org/jira/browse/KYLIN-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-2769. -- Resolution: Fixed > Non-partitioned cube doesn't need show start/end time > - > > Key: KYLIN-2769 > URL: https://issues.apache.org/jira/browse/KYLIN-2769 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2769-Non-partitioned-cube-not-show-start-and-e.patch, 屏幕快照 > 2017-07-30 下午3.34.33.png > > > Create a non-partitioned cube, after build, the "Storage" section shows > invalid characters, see the attachment. actually there is no need to show the > start/end time for non-partitioned cube. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2768) Wrong UI for count distinct measure
[ https://issues.apache.org/jira/browse/KYLIN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16106512#comment-16106512 ] Zhixiong Chen commented on KYLIN-2768: -- OK. I will add this lable. > Wrong UI for count distinct measure > --- > > Key: KYLIN-2768 > URL: https://issues.apache.org/jira/browse/KYLIN-2768 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2768-wrong-UI-for-count-distinct-measure.patch, 屏幕快照 2017-07-30 > 下午3.16.41.png > > > I made a build from 2.1.x branch, when create a count distinct measure, it > shows "Group by Column" input widget (se attachement). This is strange, as > embeded "group by column" is just in the "TopN" case, not applicable for > count distinct. > Is it for "multiple columns" support for count distinct? if so, the lable > need be updated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2769) Non-partitioned cube doesn't need show start/end time
[ https://issues.apache.org/jira/browse/KYLIN-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16106508#comment-16106508 ] Zhixiong Chen commented on KYLIN-2769: -- OK. > Non-partitioned cube doesn't need show start/end time > - > > Key: KYLIN-2769 > URL: https://issues.apache.org/jira/browse/KYLIN-2769 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2769-Non-partitioned-cube-not-show-start-and-e.patch, 屏幕快照 > 2017-07-30 下午3.34.33.png > > > Create a non-partitioned cube, after build, the "Storage" section shows > invalid characters, see the attachment. actually there is no need to show the > start/end time for non-partitioned cube. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2789) Cube's last build time is wrong
[
https://issues.apache.org/jira/browse/KYLIN-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128270#comment-16128270
]
Zhixiong Chen commented on KYLIN-2789:
--
Hi, Hongtao. Could you put your changes into a patch. [~Hongtao He]
> Cube's last build time is wrong
> ---
>
> Key: KYLIN-2789
> URL: https://issues.apache.org/jira/browse/KYLIN-2789
> Project: Kylin
> Issue Type: Bug
> Components: REST Service, Web
>Affects Versions: v1.6.0
>Reporter: Hongtao He
>Assignee: Zhixiong Chen
>Priority: Minor
> Labels: cube.last_build_time, cube.segments
> Attachments: cubeListModel.js
>
>
> Firstly, we create a segment in a cube, then we can get the attributes of
> this segment，such as
> { "date_range_start " : 2017-08-02 00:00:00,
> "date_range_end" : 2017-08-03 00:00:00,
> "last_build_time": 2017-08-16 01:00:00
> }
> Secondly, we create another segment in this cube, which has an earlier data
> range，such as
> { "date_range_start " : 2017-08-01 00:00:00,
> "date_range_end" : 2017-08-02 00:00:00,
> "last_build_time": 2017-08-16 02:00:00
> }
> Under these circumstances, the Cube's last creation time should be 2017-08-16
> 02:00:00, not 2017-08-16 01:00:00.However, we get the opposite answer in
> kylin 1.6.0.
> the realization of cube's last build time is :
> if(cube.name){
> if (cube.segments && cube.segments.length > 0) {
> for(var i= cube.segments.length-1;i>=0;i--){
> if(cube.segments[i].status==="READY"){
>cube.last_build_time =
> cube.segments[i].last_build_time;
> break;
> }else if(i===0){
> cube.last_build_time = undefined;
> }
> }
> } else {
> cube.last_build_time = undefined;
> }
> }
> (the code is in kylin/webapp/app/js/model/cubeListModel.js)
> The last build time may come from any segment，I changed the code to the
> following:
> if(cube.name){
> cube.last_build_time = undefined;
> if (cube.segments && cube.segments.length > 0) {
> for(var i= cube.segments.length-1;i>=0;i--){
> if(cube.segments[i].status==="READY"){
>if(cube.last_build_time===undefined ||
> cube.last_build_time
> cube.last_build_time =
> cube.segments[i].last_build_time;
> }
> }
> }
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-2789) Cube's last build time is wrong
[
https://issues.apache.org/jira/browse/KYLIN-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128368#comment-16128368
]
Zhixiong Chen commented on KYLIN-2789:
--
Hi, Hongtao.The git tells me 'Patch format detection failed.'
Could you rebuild a new patch and modify the commit message like
'KYLIN-2789-jira-description'.
> Cube's last build time is wrong
> ---
>
> Key: KYLIN-2789
> URL: https://issues.apache.org/jira/browse/KYLIN-2789
> Project: Kylin
> Issue Type: Bug
> Components: REST Service, Web
>Affects Versions: v1.6.0
>Reporter: Hongtao He
>Assignee: Zhixiong Chen
>Priority: Minor
> Labels: cube.last_build_time, cube.segments
> Attachments: cubeListModel.js, cubeListModel.js.patch
>
>
> Firstly, we create a segment in a cube, then we can get the attributes of
> this segment，such as
> { "date_range_start " : 2017-08-02 00:00:00,
> "date_range_end" : 2017-08-03 00:00:00,
> "last_build_time": 2017-08-16 01:00:00
> }
> Secondly, we create another segment in this cube, which has an earlier data
> range，such as
> { "date_range_start " : 2017-08-01 00:00:00,
> "date_range_end" : 2017-08-02 00:00:00,
> "last_build_time": 2017-08-16 02:00:00
> }
> Under these circumstances, the Cube's last creation time should be 2017-08-16
> 02:00:00, not 2017-08-16 01:00:00.However, we get the opposite answer in
> kylin 1.6.0.
> the realization of cube's last build time is :
> if(cube.name){
> if (cube.segments && cube.segments.length > 0) {
> for(var i= cube.segments.length-1;i>=0;i--){
> if(cube.segments[i].status==="READY"){
>cube.last_build_time =
> cube.segments[i].last_build_time;
> break;
> }else if(i===0){
> cube.last_build_time = undefined;
> }
> }
> } else {
> cube.last_build_time = undefined;
> }
> }
> (the code is in kylin/webapp/app/js/model/cubeListModel.js)
> The last build time may come from any segment，I changed the code to the
> following:
> if(cube.name){
> cube.last_build_time = undefined;
> if (cube.segments && cube.segments.length > 0) {
> for(var i= cube.segments.length-1;i>=0;i--){
> if(cube.segments[i].status==="READY"){
>if(cube.last_build_time===undefined ||
> cube.last_build_time
> cube.last_build_time =
> cube.segments[i].last_build_time;
> }
> }
> }
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-2789) Cube's last build time is wrong
[
https://issues.apache.org/jira/browse/KYLIN-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16130077#comment-16130077
]
Zhixiong Chen commented on KYLIN-2789:
--
Hi Hongtao. Please use 'git format-patch' command to rebuild a new patch.
Because use 'git format-patch' command will save your name as a contributor in
the patch.
> Cube's last build time is wrong
> ---
>
> Key: KYLIN-2789
> URL: https://issues.apache.org/jira/browse/KYLIN-2789
> Project: Kylin
> Issue Type: Bug
> Components: REST Service, Web
>Affects Versions: v1.6.0
>Reporter: Hongtao He
>Assignee: Zhixiong Chen
>Priority: Minor
> Labels: cube.last_build_time, cube.segments
> Attachments: KYLIN-2789.patch
>
>
> Firstly, we create a segment in a cube, then we can get the attributes of
> this segment，such as
> { "date_range_start " : 2017-08-02 00:00:00,
> "date_range_end" : 2017-08-03 00:00:00,
> "last_build_time": 2017-08-16 01:00:00
> }
> Secondly, we create another segment in this cube, which has an earlier data
> range，such as
> { "date_range_start " : 2017-08-01 00:00:00,
> "date_range_end" : 2017-08-02 00:00:00,
> "last_build_time": 2017-08-16 02:00:00
> }
> Under these circumstances, the Cube's last creation time should be 2017-08-16
> 02:00:00, not 2017-08-16 01:00:00.However, we get the opposite answer in
> kylin 1.6.0.
> the realization of cube's last build time is :
> if(cube.name){
> if (cube.segments && cube.segments.length > 0) {
> for(var i= cube.segments.length-1;i>=0;i--){
> if(cube.segments[i].status==="READY"){
>cube.last_build_time =
> cube.segments[i].last_build_time;
> break;
> }else if(i===0){
> cube.last_build_time = undefined;
> }
> }
> } else {
> cube.last_build_time = undefined;
> }
> }
> (the code is in kylin/webapp/app/js/model/cubeListModel.js)
> The last build time may come from any segment，I changed the code to the
> following:
> if(cube.name){
> cube.last_build_time = undefined;
> if (cube.segments && cube.segments.length > 0) {
> for(var i= cube.segments.length-1;i>=0;i--){
> if(cube.segments[i].status==="READY"){
>if(cube.last_build_time===undefined ||
> cube.last_build_time
> cube.last_build_time =
> cube.segments[i].last_build_time;
> }
> }
> }
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-2789) Cube's last build time is wrong
[
https://issues.apache.org/jira/browse/KYLIN-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16130128#comment-16130128
]
Zhixiong Chen commented on KYLIN-2789:
--
I have reviewed this patch. I will merge it into KYLIN master branch.
Thanks Hongtao!
> Cube's last build time is wrong
> ---
>
> Key: KYLIN-2789
> URL: https://issues.apache.org/jira/browse/KYLIN-2789
> Project: Kylin
> Issue Type: Bug
> Components: REST Service, Web
>Affects Versions: v1.6.0
>Reporter: Hongtao He
>Assignee: Zhixiong Chen
>Priority: Minor
> Labels: cube.last_build_time, cube.segments
> Attachments: 0001-KYLIN-2789-jira-description.patch, KYLIN-2789.patch
>
>
> Firstly, we create a segment in a cube, then we can get the attributes of
> this segment，such as
> { "date_range_start " : 2017-08-02 00:00:00,
> "date_range_end" : 2017-08-03 00:00:00,
> "last_build_time": 2017-08-16 01:00:00
> }
> Secondly, we create another segment in this cube, which has an earlier data
> range，such as
> { "date_range_start " : 2017-08-01 00:00:00,
> "date_range_end" : 2017-08-02 00:00:00,
> "last_build_time": 2017-08-16 02:00:00
> }
> Under these circumstances, the Cube's last creation time should be 2017-08-16
> 02:00:00, not 2017-08-16 01:00:00.However, we get the opposite answer in
> kylin 1.6.0.
> the realization of cube's last build time is :
> if(cube.name){
> if (cube.segments && cube.segments.length > 0) {
> for(var i= cube.segments.length-1;i>=0;i--){
> if(cube.segments[i].status==="READY"){
>cube.last_build_time =
> cube.segments[i].last_build_time;
> break;
> }else if(i===0){
> cube.last_build_time = undefined;
> }
> }
> } else {
> cube.last_build_time = undefined;
> }
> }
> (the code is in kylin/webapp/app/js/model/cubeListModel.js)
> The last build time may come from any segment，I changed the code to the
> following:
> if(cube.name){
> cube.last_build_time = undefined;
> if (cube.segments && cube.segments.length > 0) {
> for(var i= cube.segments.length-1;i>=0;i--){
> if(cube.segments[i].status==="READY"){
>if(cube.last_build_time===undefined ||
> cube.last_build_time
> cube.last_build_time =
> cube.segments[i].last_build_time;
> }
> }
> }
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (KYLIN-2789) Cube's last build time is wrong
[
https://issues.apache.org/jira/browse/KYLIN-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhixiong Chen resolved KYLIN-2789.
--
Resolution: Fixed
Fix Version/s: v2.2.0
> Cube's last build time is wrong
> ---
>
> Key: KYLIN-2789
> URL: https://issues.apache.org/jira/browse/KYLIN-2789
> Project: Kylin
> Issue Type: Bug
> Components: REST Service, Web
>Affects Versions: v1.6.0
>Reporter: Hongtao He
>Assignee: Zhixiong Chen
>Priority: Minor
> Labels: cube.last_build_time, cube.segments
> Fix For: v2.2.0
>
> Attachments: 0001-KYLIN-2789-jira-description.patch, KYLIN-2789.patch
>
>
> Firstly, we create a segment in a cube, then we can get the attributes of
> this segment，such as
> { "date_range_start " : 2017-08-02 00:00:00,
> "date_range_end" : 2017-08-03 00:00:00,
> "last_build_time": 2017-08-16 01:00:00
> }
> Secondly, we create another segment in this cube, which has an earlier data
> range，such as
> { "date_range_start " : 2017-08-01 00:00:00,
> "date_range_end" : 2017-08-02 00:00:00,
> "last_build_time": 2017-08-16 02:00:00
> }
> Under these circumstances, the Cube's last creation time should be 2017-08-16
> 02:00:00, not 2017-08-16 01:00:00.However, we get the opposite answer in
> kylin 1.6.0.
> the realization of cube's last build time is :
> if(cube.name){
> if (cube.segments && cube.segments.length > 0) {
> for(var i= cube.segments.length-1;i>=0;i--){
> if(cube.segments[i].status==="READY"){
>cube.last_build_time =
> cube.segments[i].last_build_time;
> break;
> }else if(i===0){
> cube.last_build_time = undefined;
> }
> }
> } else {
> cube.last_build_time = undefined;
> }
> }
> (the code is in kylin/webapp/app/js/model/cubeListModel.js)
> The last build time may come from any segment，I changed the code to the
> following:
> if(cube.name){
> cube.last_build_time = undefined;
> if (cube.segments && cube.segments.length > 0) {
> for(var i= cube.segments.length-1;i>=0;i--){
> if(cube.segments[i].status==="READY"){
>if(cube.last_build_time===undefined ||
> cube.last_build_time
> cube.last_build_time =
> cube.segments[i].last_build_time;
> }
> }
> }
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (KYLIN-2616) Multiple column count distinct misses GUI
[ https://issues.apache.org/jira/browse/KYLIN-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-2616. -- Resolution: Fixed Fix Version/s: v2.1.0 > Multiple column count distinct misses GUI > - > > Key: KYLIN-2616 > URL: https://issues.apache.org/jira/browse/KYLIN-2616 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: liyang >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2616-COUNT-DISTINCT-SUPPORT-MULTIPLE-COLUMN.patch > > > Although KYLIN-490 is done, user still cannot create a count distinct measure > with multiple column. The GUI of creating measure needs a patch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2741) Project config Form Validation Is Ineffective
Zhixiong Chen created KYLIN-2741: Summary: Project config Form Validation Is Ineffective Key: KYLIN-2741 URL: https://issues.apache.org/jira/browse/KYLIN-2741 Project: Kylin Issue Type: Bug Affects Versions: v2.0.0 Reporter: Zhixiong Chen Assignee: Zhixiong Chen If user create a project, and project config value is empty.The form validation should stop user saving the project. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2616) Multiple column count distinct misses GUI
[ https://issues.apache.org/jira/browse/KYLIN-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2616: - Attachment: 0001-KYLIN-2616-COUNT-DISTINCT-SUPPORT-MULTIPLE-COLUMN.patch I have fixed this bug. > Multiple column count distinct misses GUI > - > > Key: KYLIN-2616 > URL: https://issues.apache.org/jira/browse/KYLIN-2616 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: liyang >Assignee: Zhixiong Chen > Attachments: > 0001-KYLIN-2616-COUNT-DISTINCT-SUPPORT-MULTIPLE-COLUMN.patch > > > Although KYLIN-490 is done, user still cannot create a count distinct measure > with multiple column. The GUI of creating measure needs a patch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2744) Should return correct type for SUM measure in web
[ https://issues.apache.org/jira/browse/KYLIN-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088945#comment-16088945 ] Zhixiong Chen edited comment on KYLIN-2744 at 7/16/17 2:50 PM: --- If return double type for the sum measure of double type,it could cause floating point error.And you say the decimal type will result in wrong result.Could you show more detail about it? [~kangkaisen] was (Author: zhixiong chen): If return double type for the sum measure of double type,it could cause floating point error.And you say the decimal type will result in wrong result.Could you show more detail about it? [~kangkaisen]en > Should return correct type for SUM measure in web > - > > Key: KYLIN-2744 > URL: https://issues.apache.org/jira/browse/KYLIN-2744 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.0.0 >Reporter: kangkaisen >Assignee: kangkaisen > Attachments: KYLIN-2744.patch > > > Currently, Kylin return decimal type for the sum measure of double type, > which will result in wrong result. So, We should return correct type for SUM > measure in web. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-1130) Adding alias in data modeling step to support role-play dimensions
[ https://issues.apache.org/jira/browse/KYLIN-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-1130. -- Resolution: Fixed Fix Version/s: v2.0.0 This issue had fixed in Kylin 2.0. > Adding alias in data modeling step to support role-play dimensions > -- > > Key: KYLIN-1130 > URL: https://issues.apache.org/jira/browse/KYLIN-1130 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Haowei Ji >Assignee: Zhong,Jason >Priority: Minor > Fix For: v2.0.0 > > > When building the cube, step 2 data model, as in DW star schema, it’s normal > we have some role play dimensions, like org unit, date or employee, one > dimension could be used several times to join with fact table when doing the > data modeling, and when it comes to step 3 Dimentions, when adding > dimensions, the dimension tables displayed multiple times. Normally it shall > be good to use some alias in this step, otherwise I don’t know which > dimension I’m actually using. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-1683) Row key could drag and drop in view state of cube - advanced settings tabpage
[ https://issues.apache.org/jira/browse/KYLIN-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-1683. -- Resolution: Fixed > Row key could drag and drop in view state of cube - advanced settings tabpage > - > > Key: KYLIN-1683 > URL: https://issues.apache.org/jira/browse/KYLIN-1683 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.5.1 >Reporter: Dong Li >Assignee: luguosheng >Priority: Minor > Attachments: 0001-KYLIN-1683.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2544) lookup table show wrong join type
[ https://issues.apache.org/jira/browse/KYLIN-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2544: - Attachment: 0001-KYLIN-2544-LOOKUP-TABLE-SHOW-WRONG-JOIN-TYPE.patch I have fixed this bug.Thanks! > lookup table show wrong join type > - > > Key: KYLIN-2544 > URL: https://issues.apache.org/jira/browse/KYLIN-2544 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Zhixiong Chen >Assignee: Zhixiong Chen > Attachments: 0001-KYLIN-2544-LOOKUP-TABLE-SHOW-WRONG-JOIN-TYPE.patch > > > lookup table show wrong join type,when edit a left join lookup table -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2544) lookup table show wrong join type
[ https://issues.apache.org/jira/browse/KYLIN-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-2544. -- Resolution: Fixed > lookup table show wrong join type > - > > Key: KYLIN-2544 > URL: https://issues.apache.org/jira/browse/KYLIN-2544 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Zhixiong Chen >Assignee: Zhixiong Chen > Attachments: 0001-KYLIN-2544-LOOKUP-TABLE-SHOW-WRONG-JOIN-TYPE.patch > > > lookup table show wrong join type,when edit a left join lookup table -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-1668) Rowkey column shouldn't allow delete and add
[ https://issues.apache.org/jira/browse/KYLIN-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-1668. -- Resolution: Fixed Fix Version/s: v2.1.0 > Rowkey column shouldn't allow delete and add > > > Key: KYLIN-1668 > URL: https://issues.apache.org/jira/browse/KYLIN-1668 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.5.0, v1.3.0, v1.5.1 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > > Every column in rowkey are required, couldn't be deleted. And no need to add > other columns. The "-" icon and "New Rowkey Column" button should be removed > from the UI. > Besides, please add some text to let user know the column sequence is > adjustable with drag -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2604) Use global dict as the default encoding for precise distinct count in web
[ https://issues.apache.org/jira/browse/KYLIN-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085543#comment-16085543 ] Zhixiong Chen commented on KYLIN-2604: -- [~kangkaisen],had you completed this feature. > Use global dict as the default encoding for precise distinct count in web > - > > Key: KYLIN-2604 > URL: https://issues.apache.org/jira/browse/KYLIN-2604 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v2.0.0 >Reporter: kangkaisen >Assignee: kangkaisen >Priority: Minor > > we should use global dict as the default encoding for precise distinct count > in web, which more easy-to-use for users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2604) Use global dict as the default encoding for precise distinct count in web
[ https://issues.apache.org/jira/browse/KYLIN-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085548#comment-16085548 ] Zhixiong Chen commented on KYLIN-2604: -- OK. Thanks Kaisen. > Use global dict as the default encoding for precise distinct count in web > - > > Key: KYLIN-2604 > URL: https://issues.apache.org/jira/browse/KYLIN-2604 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v2.0.0 >Reporter: kangkaisen >Assignee: kangkaisen >Priority: Minor > > we should use global dict as the default encoding for precise distinct count > in web, which more easy-to-use for users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2744) Should return correct type for SUM measure in web
[ https://issues.apache.org/jira/browse/KYLIN-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088945#comment-16088945 ] Zhixiong Chen commented on KYLIN-2744: -- If return double type for the sum measure of double type,it could cause floating point error.And you say the decimal type will result in wrong result.Could you show more detail about it? [~kangkaisen]en > Should return correct type for SUM measure in web > - > > Key: KYLIN-2744 > URL: https://issues.apache.org/jira/browse/KYLIN-2744 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.0.0 >Reporter: kangkaisen >Assignee: kangkaisen > Attachments: KYLIN-2744.patch > > > Currently, Kylin return decimal type for the sum measure of double type, > which will result in wrong result. So, We should return correct type for SUM > measure in web. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2604) Use global dict as the default encoding for precise distinct count in web
[ https://issues.apache.org/jira/browse/KYLIN-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097343#comment-16097343 ] Zhixiong Chen commented on KYLIN-2604: -- OK. I have reviewed this patch . I will merge it into Kylin master branch and 2.1 branch. Thanks [~kangkaisen]. > Use global dict as the default encoding for precise distinct count in web > - > > Key: KYLIN-2604 > URL: https://issues.apache.org/jira/browse/KYLIN-2604 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v2.0.0 >Reporter: kangkaisen >Assignee: kangkaisen >Priority: Minor > Attachments: KYLIN-2604.patch > > > we should use global dict as the default encoding for precise distinct count > in web, which more easy-to-use for users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2604) Use global dict as the default encoding for precise distinct count in web
[ https://issues.apache.org/jira/browse/KYLIN-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-2604. -- Resolution: Fixed Fix Version/s: v2.1.0 > Use global dict as the default encoding for precise distinct count in web > - > > Key: KYLIN-2604 > URL: https://issues.apache.org/jira/browse/KYLIN-2604 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v2.0.0 >Reporter: kangkaisen >Assignee: kangkaisen >Priority: Minor > Fix For: v2.1.0 > > Attachments: KYLIN-2604.patch > > > we should use global dict as the default encoding for precise distinct count > in web, which more easy-to-use for users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-1683) Row key could drag and drop in view state of cube - advanced settings tabpage
[ https://issues.apache.org/jira/browse/KYLIN-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1683: - Attachment: (was: 0001-KYLIN-1683-Row-key-could-drag-and-drop-in-view-state.patch) > Row key could drag and drop in view state of cube - advanced settings tabpage > - > > Key: KYLIN-1683 > URL: https://issues.apache.org/jira/browse/KYLIN-1683 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.5.1 >Reporter: Dong Li >Assignee: Zhong,Jason >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2161) On saving a DataModel Kylin didn't do enough validation
[ https://issues.apache.org/jira/browse/KYLIN-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074211#comment-16074211 ] Zhixiong Chen commented on KYLIN-2161: -- This issue had fixed in Kylin 2.0. > On saving a DataModel Kylin didn't do enough validation > > > Key: KYLIN-2161 > URL: https://issues.apache.org/jira/browse/KYLIN-2161 > Project: Kylin > Issue Type: Bug > Components: Metadata, Web >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > > I have a data model, which have a lookup table A, and have picked some > columns on A as the dimension; Then delete the table's join condition, saving > it and can get success; while in the "dimensions", table A still exists. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (KYLIN-2161) On saving a DataModel Kylin didn't do enough validation
[ https://issues.apache.org/jira/browse/KYLIN-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen closed KYLIN-2161. Resolution: Fixed > On saving a DataModel Kylin didn't do enough validation > > > Key: KYLIN-2161 > URL: https://issues.apache.org/jira/browse/KYLIN-2161 > Project: Kylin > Issue Type: Bug > Components: Metadata, Web >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > > I have a data model, which have a lookup table A, and have picked some > columns on A as the dimension; Then delete the table's join condition, saving > it and can get success; while in the "dimensions", table A still exists. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2699) Tomcat LinkageError for curator-client jar file conflict
[ https://issues.apache.org/jira/browse/KYLIN-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074215#comment-16074215 ] Zhixiong Chen commented on KYLIN-2699: -- Dong Li , could you review the patch? > Tomcat LinkageError for curator-client jar file conflict > > > Key: KYLIN-2699 > URL: https://issues.apache.org/jira/browse/KYLIN-2699 > Project: Kylin > Issue Type: Bug > Components: Job Engine, Web >Affects Versions: v2.0.0 >Reporter: qiumingming >Assignee: Dong Li > Attachments: KYLIN-2699.patch > > > Exception: java.lang.LinkageError: loader constraint violation: loader > (instance of sun/misc/Launcher$AppClassLoader) previously initiated loading > for a different type with name "org/apache/curator/RetryPolicy" > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:763) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) > at java.net.URLClassLoader.access$100(URLClassLoader.java:73) > at java.net.URLClassLoader$1.run(URLClassLoader.java:368) > at java.net.URLClassLoader$1.run(URLClassLoader.java:362) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:361) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at > org.apache.curator.CuratorZookeeperClient.(CuratorZookeeperClient.java:97) > at > org.apache.curator.framework.imps.CuratorFrameworkImpl.(CuratorFrameworkImpl.java:108) > at > org.apache.curator.framework.CuratorFrameworkFactory$Builder.build(CuratorFrameworkFactory.java:124) > at > org.apache.kylin.storage.hbase.util.ZookeeperJobLock.lock(ZookeeperJobLock.java:70) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler.init(DefaultScheduler.java:208) > at org.apache.kylin.rest.service.JobService$1.run(JobService.java:116) > at java.lang.Thread.run(Thread.java:745) > This exception will make kylin job engine does not work. And I found it > occured because in the kylin/WEB-INF/lib contains the > curator-client-2.7.1.jar which make some conflicts. In general, the HBase and > Hadoop cluster always contain their own curator-client jar files. So there is > no need to include the curator-client jar file in kylin/WEB-INF/lib. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (KYLIN-2699) Tomcat LinkageError for curator-client jar file conflict
[ https://issues.apache.org/jira/browse/KYLIN-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2699: - Comment: was deleted (was: Dong Li , could you review the patch?) > Tomcat LinkageError for curator-client jar file conflict > > > Key: KYLIN-2699 > URL: https://issues.apache.org/jira/browse/KYLIN-2699 > Project: Kylin > Issue Type: Bug > Components: Job Engine, Web >Affects Versions: v2.0.0 >Reporter: qiumingming >Assignee: Dong Li > Attachments: KYLIN-2699.patch > > > Exception: java.lang.LinkageError: loader constraint violation: loader > (instance of sun/misc/Launcher$AppClassLoader) previously initiated loading > for a different type with name "org/apache/curator/RetryPolicy" > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:763) > at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) > at java.net.URLClassLoader.access$100(URLClassLoader.java:73) > at java.net.URLClassLoader$1.run(URLClassLoader.java:368) > at java.net.URLClassLoader$1.run(URLClassLoader.java:362) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:361) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at > org.apache.curator.CuratorZookeeperClient.(CuratorZookeeperClient.java:97) > at > org.apache.curator.framework.imps.CuratorFrameworkImpl.(CuratorFrameworkImpl.java:108) > at > org.apache.curator.framework.CuratorFrameworkFactory$Builder.build(CuratorFrameworkFactory.java:124) > at > org.apache.kylin.storage.hbase.util.ZookeeperJobLock.lock(ZookeeperJobLock.java:70) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler.init(DefaultScheduler.java:208) > at org.apache.kylin.rest.service.JobService$1.run(JobService.java:116) > at java.lang.Thread.run(Thread.java:745) > This exception will make kylin job engine does not work. And I found it > occured because in the kylin/WEB-INF/lib contains the > curator-client-2.7.1.jar which make some conflicts. In general, the HBase and > Hadoop cluster always contain their own curator-client jar files. So there is > no need to include the curator-client jar file in kylin/WEB-INF/lib. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (KYLIN-1683) Row key could drag and drop in view state of cube - advanced settings tabpage
[ https://issues.apache.org/jira/browse/KYLIN-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1683: - Comment: was deleted (was: I have fixed this bug.Please check it.Thanks!) > Row key could drag and drop in view state of cube - advanced settings tabpage > - > > Key: KYLIN-1683 > URL: https://issues.apache.org/jira/browse/KYLIN-1683 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.5.1 >Reporter: Dong Li >Assignee: Zhong,Jason >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-1895) Cube Name displays the name of CubeDesc on UI
[ https://issues.apache.org/jira/browse/KYLIN-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-1895. -- Resolution: Fixed > Cube Name displays the name of CubeDesc on UI > - > > Key: KYLIN-1895 > URL: https://issues.apache.org/jira/browse/KYLIN-1895 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.5.2 >Reporter: Dong Li >Assignee: Zhong,Jason >Priority: Minor > Labels: newbie > Attachments: > 0001-KYLIN-1895-Cube-Name-displays-the-name-of-CubeDesc-o.patch, Screen Shot > 2016-07-15 at 09.26.25.png > > > In the cube list, the name displays the real name of cube. > In cube detail tabpage, the cube name displays the name of CubeDesc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2705) Should allow user to remove partition_date_column for model in web
[ https://issues.apache.org/jira/browse/KYLIN-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074187#comment-16074187 ] Zhixiong Chen commented on KYLIN-2705: -- I have reviewed this patch. Thanks Kaisen. > Should allow user to remove partition_date_column for model in web > -- > > Key: KYLIN-2705 > URL: https://issues.apache.org/jira/browse/KYLIN-2705 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.0.0 >Reporter: kangkaisen >Assignee: kangkaisen >Priority: Minor > Attachments: KYLIN-2705.patch > > > Currently, User couldn't remove partition_date_column for model in web. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (KYLIN-811) Kylin streaming branch GUI enhancement
[ https://issues.apache.org/jira/browse/KYLIN-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen closed KYLIN-811. --- Resolution: Fixed > Kylin streaming branch GUI enhancement > -- > > Key: KYLIN-811 > URL: https://issues.apache.org/jira/browse/KYLIN-811 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Zhong,Jason >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-1642) UI Refresh needed after Purging the Cube before Build ...
[ https://issues.apache.org/jira/browse/KYLIN-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-1642. -- Resolution: Fixed > UI Refresh needed after Purging the Cube before Build ... > -- > > Key: KYLIN-1642 > URL: https://issues.apache.org/jira/browse/KYLIN-1642 > Project: Kylin > Issue Type: Bug > Components: General, Web >Affects Versions: all, v1.5.1 >Reporter: Richard Calaba >Priority: Trivial > > Hello, minor bug on Web UI of Kylin discovered: > - After calling Purge on Cube and then trying immediately Build the cube > again (and selecting a Today as the time dimension selection for new segment) > I was getting an error that the selected date (of the new segment) should be > bigger than the date of last loaded segment - which was already Purged ... > - I had to refresh the Web UI in order to be able to schedule the Build of > empty cube > Seems the Purge need to refresh the WebUI metadata about the loaded segments > ... > Observed on version 1.5.1 but assuming all affected ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2276) It has two fact table when modify model
[ https://issues.apache.org/jira/browse/KYLIN-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-2276. -- Resolution: Fixed Fix Version/s: v2.0.0 > It has two fact table when modify model > --- > > Key: KYLIN-2276 > URL: https://issues.apache.org/jira/browse/KYLIN-2276 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.6.0, v1.5.4.1 >Reporter: PengwenYuan >Assignee: Zhong,Jason >Priority: Trivial > Fix For: v2.0.0 > > > I found when I modify a model and chose another fact table. At 'Model > Designer 3 Dimensions' it had two fact table (old table didn't delete). > But it can be successfully build. > kylin version : 1.5.4.1 and 1.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KYLIN-2691) Broken cube cannot be deleted
[ https://issues.apache.org/jira/browse/KYLIN-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen reassigned KYLIN-2691: Assignee: luguosheng (was: Zhong,Jason) > Broken cube cannot be deleted > - > > Key: KYLIN-2691 > URL: https://issues.apache.org/jira/browse/KYLIN-2691 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: jiatao.tao >Assignee: luguosheng >Priority: Minor > > Broken cube cannot be deleted -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (KYLIN-2370) Refine unload table
[ https://issues.apache.org/jira/browse/KYLIN-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen closed KYLIN-2370. Resolution: Fixed > Refine unload table > --- > > Key: KYLIN-2370 > URL: https://issues.apache.org/jira/browse/KYLIN-2370 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Zhixiong Chen >Assignee: Zhixiong Chen > Attachments: 0001-KYLIN-2370-Refine-unload-and-reload-table.patch > > > Move the Unload Button to the Table level . > Add a reload button side by side. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (KYLIN-2689) Only dimension columns can join when create a model
[ https://issues.apache.org/jira/browse/KYLIN-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen closed KYLIN-2689. Resolution: Fixed This issue has fixed. > Only dimension columns can join when create a model > --- > > Key: KYLIN-2689 > URL: https://issues.apache.org/jira/browse/KYLIN-2689 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v2.1.0 >Reporter: luguosheng >Assignee: luguosheng > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2689-Only-dimension-columns-can-join-when-crea.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2689) Only dimension columns can join when create a model
[ https://issues.apache.org/jira/browse/KYLIN-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2689: - Attachment: 0001-KYLIN-2689-Only-dimension-columns-can-join-when-crea.patch > Only dimension columns can join when create a model > --- > > Key: KYLIN-2689 > URL: https://issues.apache.org/jira/browse/KYLIN-2689 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v2.1.0 >Reporter: luguosheng >Assignee: luguosheng > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2689-Only-dimension-columns-can-join-when-crea.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2688) When the model has a ready cube, should not allow user to edit model JSON in web.
[ https://issues.apache.org/jira/browse/KYLIN-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16068186#comment-16068186 ] Zhixiong Chen commented on KYLIN-2688: -- I have reviewed this patch. > When the model has a ready cube, should not allow user to edit model JSON in > web. > - > > Key: KYLIN-2688 > URL: https://issues.apache.org/jira/browse/KYLIN-2688 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Minor > Labels: patch > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2688-When-the-model-has-a-ready-cube-should-no.patch > > > When the model has a ready cube，user can not edit model and prompt “This > model is still used by xxxCube”，but user can edit model JSON in the web。It > should be kept consistent。 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2688) When the model has a ready cube, should not allow user to edit model JSON in web.
[ https://issues.apache.org/jira/browse/KYLIN-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-2688. -- Resolution: Fixed This issue has fixed.Thanks! > When the model has a ready cube, should not allow user to edit model JSON in > web. > - > > Key: KYLIN-2688 > URL: https://issues.apache.org/jira/browse/KYLIN-2688 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Minor > Labels: patch > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2688-When-the-model-has-a-ready-cube-should-no.patch > > > When the model has a ready cube，user can not edit model and prompt “This > model is still used by xxxCube”，but user can edit model JSON in the web。It > should be kept consistent。 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2688) When the model has a ready cube, should not allow user to edit model JSON in web.
[ https://issues.apache.org/jira/browse/KYLIN-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16068318#comment-16068318 ] Zhixiong Chen commented on KYLIN-2688: -- However,if user edit model JSON when there are cubes in this model,it could lead to the cube's metadata broken. > When the model has a ready cube, should not allow user to edit model JSON in > web. > - > > Key: KYLIN-2688 > URL: https://issues.apache.org/jira/browse/KYLIN-2688 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Minor > Labels: patch > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2688-When-the-model-has-a-ready-cube-should-no.patch > > > When the model has a ready cube，user can not edit model and prompt “This > model is still used by xxxCube”，but user can edit model JSON in the web。It > should be kept consistent。 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2688) When the model has a ready cube, should not allow user to edit model JSON in web.
[ https://issues.apache.org/jira/browse/KYLIN-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16068384#comment-16068384 ] Zhixiong Chen commented on KYLIN-2688: -- But if user want to edit model's JSON, it requires him to have sufficient understanding of the model's metadata. > When the model has a ready cube, should not allow user to edit model JSON in > web. > - > > Key: KYLIN-2688 > URL: https://issues.apache.org/jira/browse/KYLIN-2688 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Minor > Labels: patch > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2688-When-the-model-has-a-ready-cube-should-no.patch > > > When the model has a ready cube，user can not edit model and prompt “This > model is still used by xxxCube”，but user can edit model JSON in the web。It > should be kept consistent。 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2768) Wrong UI for count distinct measure
[ https://issues.apache.org/jira/browse/KYLIN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2768: - Attachment: 0001-KYLIN-2768-wrong-UI-for-count-distinct-measure.patch I have update the patch. Please check it .Thanks! > Wrong UI for count distinct measure > --- > > Key: KYLIN-2768 > URL: https://issues.apache.org/jira/browse/KYLIN-2768 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2768-wrong-UI-for-count-distinct-measure.patch, 屏幕快照 2017-07-30 > 下午3.16.41.png > > > I made a build from 2.1.x branch, when create a count distinct measure, it > shows "Group by Column" input widget (se attachement). This is strange, as > embeded "group by column" is just in the "TopN" case, not applicable for > count distinct. > Is it for "multiple columns" support for count distinct? if so, the lable > need be updated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2768) Wrong UI for count distinct measure
[ https://issues.apache.org/jira/browse/KYLIN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2768: - Attachment: (was: 0001-KYLIN-2768-wrong-UI-for-count-distinct-measure.patch) > Wrong UI for count distinct measure > --- > > Key: KYLIN-2768 > URL: https://issues.apache.org/jira/browse/KYLIN-2768 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > Attachments: 屏幕快照 2017-07-30 下午3.16.41.png > > > I made a build from 2.1.x branch, when create a count distinct measure, it > shows "Group by Column" input widget (se attachement). This is strange, as > embeded "group by column" is just in the "TopN" case, not applicable for > count distinct. > Is it for "multiple columns" support for count distinct? if so, the lable > need be updated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-2768) Wrong UI for count distinct measure
[ https://issues.apache.org/jira/browse/KYLIN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16106517#comment-16106517 ] Zhixiong Chen edited comment on KYLIN-2768 at 7/30/17 2:26 PM: --- I have updated the patch. Please check it .Thanks! was (Author: zhixiong chen): I have update the patch. Please check it .Thanks! > Wrong UI for count distinct measure > --- > > Key: KYLIN-2768 > URL: https://issues.apache.org/jira/browse/KYLIN-2768 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2768-wrong-UI-for-count-distinct-measure.patch, 屏幕快照 2017-07-30 > 下午3.16.41.png > > > I made a build from 2.1.x branch, when create a count distinct measure, it > shows "Group by Column" input widget (se attachement). This is strange, as > embeded "group by column" is just in the "TopN" case, not applicable for > count distinct. > Is it for "multiple columns" support for count distinct? if so, the lable > need be updated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2768) Wrong UI for count distinct measure
[ https://issues.apache.org/jira/browse/KYLIN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108288#comment-16108288 ] Zhixiong Chen commented on KYLIN-2768: -- OK.I will double commit in master and 2.1.x. > Wrong UI for count distinct measure > --- > > Key: KYLIN-2768 > URL: https://issues.apache.org/jira/browse/KYLIN-2768 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2768-wrong-UI-for-count-distinct-measure.patch, 屏幕快照 2017-07-30 > 下午3.16.41.png > > > I made a build from 2.1.x branch, when create a count distinct measure, it > shows "Group by Column" input widget (se attachement). This is strange, as > embeded "group by column" is just in the "TopN" case, not applicable for > count distinct. > Is it for "multiple columns" support for count distinct? if so, the lable > need be updated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2768) Wrong UI for count distinct measure
[ https://issues.apache.org/jira/browse/KYLIN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-2768. -- Resolution: Fixed > Wrong UI for count distinct measure > --- > > Key: KYLIN-2768 > URL: https://issues.apache.org/jira/browse/KYLIN-2768 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2768-wrong-UI-for-count-distinct-measure.patch, 屏幕快照 2017-07-30 > 下午3.16.41.png > > > I made a build from 2.1.x branch, when create a count distinct measure, it > shows "Group by Column" input widget (se attachement). This is strange, as > embeded "group by column" is just in the "TopN" case, not applicable for > count distinct. > Is it for "multiple columns" support for count distinct? if so, the lable > need be updated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (KYLIN-2798) Can't rearrange the order of rowkey columns though web UI
[ https://issues.apache.org/jira/browse/KYLIN-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen closed KYLIN-2798. > Can't rearrange the order of rowkey columns though web UI > - > > Key: KYLIN-2798 > URL: https://issues.apache.org/jira/browse/KYLIN-2798 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: zhengdong >Assignee: Zhixiong Chen > Fix For: v2.2.0 > > Attachments: > 0001-KYLIN-2798-Can-t-rearrange-the-order-of-rowkey-colum.patch > > > In the 'advanced setting' step of cube designer, dragging row key columns > doesn't have real impact on theirs' order. Further more, if we drag a column > to the top and then change the encoding of those columns below it, we may get > an exception with 'Row key count doesn't match..' when saving the cube > description. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2798) Can't rearrange the order of rowkey columns though web UI
[ https://issues.apache.org/jira/browse/KYLIN-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134723#comment-16134723 ] Zhixiong Chen commented on KYLIN-2798: -- I have reviewed this patch. I will merge this patch into KYLIN master branch. Thanks Zhengdong ! > Can't rearrange the order of rowkey columns though web UI > - > > Key: KYLIN-2798 > URL: https://issues.apache.org/jira/browse/KYLIN-2798 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: zhengdong >Assignee: Zhong,Jason > Attachments: > 0001-KYLIN-2798-Can-t-rearrange-the-order-of-rowkey-colum.patch > > > In the 'advanced setting' step of cube designer, dragging row key columns > doesn't have real impact on theirs' order. Further more, if we drag a column > to the top and then change the encoding of those columns below it, we may get > an exception with 'Row key count doesn't match..' when saving the cube > description. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2798) Can't rearrange the order of rowkey columns though web UI
[ https://issues.apache.org/jira/browse/KYLIN-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-2798. -- Resolution: Fixed Assignee: Zhixiong Chen (was: Zhong,Jason) Fix Version/s: v2.2.0 > Can't rearrange the order of rowkey columns though web UI > - > > Key: KYLIN-2798 > URL: https://issues.apache.org/jira/browse/KYLIN-2798 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: zhengdong >Assignee: Zhixiong Chen > Fix For: v2.2.0 > > Attachments: > 0001-KYLIN-2798-Can-t-rearrange-the-order-of-rowkey-colum.patch > > > In the 'advanced setting' step of cube designer, dragging row key columns > doesn't have real impact on theirs' order. Further more, if we drag a column > to the top and then change the encoding of those columns below it, we may get > an exception with 'Row key count doesn't match..' when saving the cube > description. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-1131) Enabling saving incomplete cube
[ https://issues.apache.org/jira/browse/KYLIN-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1131: - Description: _emphasized text_When adding cubes, the cube could only be saved when it comes to the last step, and if user switch to other functions and back, it will disappear, seems the web does not caching what user has just done, it's annoying to start up again, especially when some cubes are complicated. So suggest to caching the cube and adding save button in the process of creating the cube. (was: When adding cubes, the cube could only be saved when it comes to the last step, and if user switch to other functions and back, it will disappear, seems the web does not caching what user has just done, it's annoying to start up again, especially when some cubes are complicated. So suggest to caching the cube and adding save button in the process of creating the cube. ) > Enabling saving incomplete cube > --- > > Key: KYLIN-1131 > URL: https://issues.apache.org/jira/browse/KYLIN-1131 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Haowei Ji >Assignee: Zhong,Jason > > _emphasized text_When adding cubes, the cube could only be saved when it > comes to the last step, and if user switch to other functions and back, it > will disappear, seems the web does not caching what user has just done, it's > annoying to start up again, especially when some cubes are complicated. So > suggest to caching the cube and adding save button in the process of creating > the cube. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-1131) Enabling saving incomplete cube
[ https://issues.apache.org/jira/browse/KYLIN-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-1131: - Description: When adding cubes, the cube could only be saved when it comes to the last step, and if user switch to other functions and back, it will disappear, seems the web does not caching what user has just done, it's annoying to start up again, especially when some cubes are complicated. So suggest to caching the cube and adding save button in the process of creating the cube. (was: _emphasized text_When adding cubes, the cube could only be saved when it comes to the last step, and if user switch to other functions and back, it will disappear, seems the web does not caching what user has just done, it's annoying to start up again, especially when some cubes are complicated. So suggest to caching the cube and adding save button in the process of creating the cube. ) > Enabling saving incomplete cube > --- > > Key: KYLIN-1131 > URL: https://issues.apache.org/jira/browse/KYLIN-1131 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Haowei Ji >Assignee: Zhong,Jason > > When adding cubes, the cube could only be saved when it comes to the last > step, and if user switch to other functions and back, it will disappear, > seems the web does not caching what user has just done, it's annoying to > start up again, especially when some cubes are complicated. So suggest to > caching the cube and adding save button in the process of creating the cube. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2939) Get config properties not correct in UI
[
https://issues.apache.org/jira/browse/KYLIN-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16207241#comment-16207241
]
Zhixiong Chen commented on KYLIN-2939:
--
Could you give a patch?[~julianpan]
> Get config properties not correct in UI
> ---
>
> Key: KYLIN-2939
> URL: https://issues.apache.org/jira/browse/KYLIN-2939
> Project: Kylin
> Issue Type: Bug
> Components: Web
>Reporter: Pan, Julian
>Assignee: Pan, Julian
>Priority: Critical
>
> When I want to get kylin.env by getDeployEnv(), it will return
> kylin.env.hdfs-working-dir value. There is a bug in getProperty in
> kylinProperties.js.
> This function will return first properties will contains this name.
> Here is the fix:
> this.getProperty = function (name) {
> var keyIndex = _config.indexOf('\n' + name + '=');
> var keyLength = name.length;
> var partialResult = _config.substr(keyIndex);
> var preValueIndex = partialResult.indexOf("=");
> var sufValueIndex = partialResult.indexOf("\n", 2);
> return partialResult.substring(preValueIndex + 1, sufValueIndex);
> }
> If necessary, I can create a patch for it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-2604) Use global dict as the default encoding for precise distinct count in web
[ https://issues.apache.org/jira/browse/KYLIN-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151763#comment-16151763 ] Zhixiong Chen commented on KYLIN-2604: -- Hi, Kaishen . Why do you add a check to distinguish whether the measure is int? > Use global dict as the default encoding for precise distinct count in web > - > > Key: KYLIN-2604 > URL: https://issues.apache.org/jira/browse/KYLIN-2604 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v2.0.0 >Reporter: kangkaisen >Assignee: kangkaisen >Priority: Minor > Fix For: v2.2.0 > > Attachments: > KYLIN-2602-Non-Int-type-precise-count-distinct-measure-must-set-advanced-dict.patch, > KYLIN-2604.patch > > > we should use global dict as the default encoding for precise distinct count > in web, which more easy-to-use for users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2920) Failed to get streaming config on WebUI
[ https://issues.apache.org/jira/browse/KYLIN-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209099#comment-16209099 ] Zhixiong Chen commented on KYLIN-2920: -- I have reviewed this patch. Thanks! > Failed to get streaming config on WebUI > --- > > Key: KYLIN-2920 > URL: https://issues.apache.org/jira/browse/KYLIN-2920 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.2.0 >Reporter: Dong Li >Assignee: luguosheng > Fix For: v2.2.0 > > Attachments: > 0001-KYLIN-2920-Failed-to-get-streaming-config-on-WebUI.patch, Screen Shot > 2017-10-09 at 10.09.32.png > > > Paramters "project" of rest api call /kylin/api/streaming/getConfig are > missed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2756) Let "LIMIT" be optional in "Inspect" page
[ https://issues.apache.org/jira/browse/KYLIN-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2756: - Attachment: 0001-KYLIN-2756-Let-LIMIT-be-optional-in-inspect-page.patch I have completed this issue.Please review it.Thanks! > Let "LIMIT" be optional in "Inspect" page > - > > Key: KYLIN-2756 > URL: https://issues.apache.org/jira/browse/KYLIN-2756 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Attachments: > 0001-KYLIN-2756-Let-LIMIT-be-optional-in-inspect-page.patch > > > Kylin's "Inspect" page will append a LIMIT clause for queries if the query > doesn't have "LIMIT"; > While this will make some query be invalid because "LIMIT" not always appear > in the last position. For example: > select * from KYLIN_SALES OFFSET 100 ROWS FETCH FIRST 10 ROWS ONLY > According to Calcite's SQL reference, LIMIT should be before OFFSET clause. > So, Kylin should give user the option of not append the "LIMIT". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2875) Cube e-mail notification Validation
[ https://issues.apache.org/jira/browse/KYLIN-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16208763#comment-16208763 ] Zhixiong Chen commented on KYLIN-2875: -- Could you give a patch to resolve this jira? [~julianpan] > Cube e-mail notification Validation > --- > > Key: KYLIN-2875 > URL: https://issues.apache.org/jira/browse/KYLIN-2875 > Project: Kylin > Issue Type: Improvement > Components: REST Service, Web >Reporter: Pan, Julian >Assignee: Pan, Julian > > Validation e-mail notification list avoid EmailException: > 2017-03-28 20:01:56,453 INFO [pool-10-thread-8] > execution.AbstractExecutable:250 : notify > list:[us...@apache.com;us...@apache.com;, dl-user-gr...@apache.com] > 2017-03-28 20:01:56,453 ERROR [pool-10-thread-8] util.MailService:112 : > Illegal semicolon, not in group > org.apache.commons.mail.EmailException: Illegal semicolon, not in group > at org.apache.commons.mail.Email.createInternetAddress(Email.java:541) > at org.apache.commons.mail.Email.addTo(Email.java:653) > at org.apache.commons.mail.Email.addTo(Email.java:636) > at org.apache.commons.mail.Email.addTo(Email.java:618) > at org.apache.kylin.common.util.MailService.sendMail(MailService.java:97) > at org.apache.kylin.common.util.MailService.sendMail(MailService.java:70) > at > org.apache.kylin.job.execution.AbstractExecutable.notifyUserStatusChange(AbstractExecutable.java:251) > at > org.apache.kylin.job.execution.DefaultChainedExecutable.onStatusChange(DefaultChainedExecutable.java:105) > at org.apache.kylin.engine.mr.CubingJob.onStatusChange(CubingJob.java:296) > at > org.apache.kylin.job.execution.DefaultChainedExecutable.onExecuteFinished(DefaultChainedExecutable.java:89) > at org.apache.kylin.engine.mr.CubingJob.onExecuteFinished(CubingJob.java:292) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:135) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:133) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: javax.mail.internet.AddressException: Illegal semicolon, not in > group in string > ``cais...@ebay.com;kalagupack...@ebay.com;cb...@ebay.com;cb...@ebay.com;'' at > position 16 > at javax.mail.internet.InternetAddress.parse(InternetAddress.java:780) > at javax.mail.internet.InternetAddress.parse(InternetAddress.java:555) > at javax.mail.internet.InternetAddress.(InternetAddress.java:91) > at org.apache.commons.mail.Email.createInternetAddress(Email.java:514) > ... 15 more -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2157) add select/unselect all when select dimensions and measures in model
[ https://issues.apache.org/jira/browse/KYLIN-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen updated KYLIN-2157: - Summary: add select/unselect all when select dimensions and measures in model (was: add select/unselect all when select dimensions and measures in morel) > add select/unselect all when select dimensions and measures in model > > > Key: KYLIN-2157 > URL: https://issues.apache.org/jira/browse/KYLIN-2157 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v1.5.4.1 >Reporter: Zhong,Jason >Assignee: Zhong,Jason > > add select/unselect all when select dimensions and measures in morel -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2882) Disable datepicker input avoid user typing issue
[ https://issues.apache.org/jira/browse/KYLIN-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264224#comment-16264224 ] Zhixiong Chen commented on KYLIN-2882: -- We shouldn't forbid user to type in input. Maybe there is other way to resolve the issue that user input wrong type date. > Disable datepicker input avoid user typing issue > > > Key: KYLIN-2882 > URL: https://issues.apache.org/jira/browse/KYLIN-2882 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Pan, Julian >Assignee: Pan, Julian >Priority: Minor > > When user typing in input for datepicker, which will cause date error issue. > Could we add the attribute read-only for datepicker input? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-3030) In the cubes table, the options of last column action are missing partly.
[ https://issues.apache.org/jira/browse/KYLIN-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264214#comment-16264214 ] Zhixiong Chen commented on KYLIN-3030: -- Hi,[~peng.jianhua].Sorry for late to check this patch.I will merge it into KYLIN master. Thanks! > In the cubes table, the options of last column action are missing partly. > - > > Key: KYLIN-3030 > URL: https://issues.apache.org/jira/browse/KYLIN-3030 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: peng.jianhua >Assignee: peng.jianhua > Labels: patch > Attachments: > 0001-KYLIN-3030-In-the-cubes-table-the-options-of-last-co.patch, > action_item_is_missing_partly1.png, action_item_is_missing_partly2.png > > > 1. Open the Model page; > 2. Choose one cube in table, and click the "Action" button, then you can find > serveral options, just like "Edit CubeDesc", "View Cube"; > 3. Then you can find the "Edit CubeDesc" option is missing partly, refer to > [^action_item_is_missing_partly1.png]; > 4. If you zoom out the browser window, you can even find not only "Edit > CubeDesc" but also "View Cube" is missing partly, refer to > [^action_item_is_missing_partly2.png] > So we can modify cubes.html, add the margin-right setting for div, which can > give more space to options. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-3030) In the cubes table, the options of last column action are missing partly.
[ https://issues.apache.org/jira/browse/KYLIN-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-3030. -- Resolution: Fixed Fix Version/s: v2.3.0 > In the cubes table, the options of last column action are missing partly. > - > > Key: KYLIN-3030 > URL: https://issues.apache.org/jira/browse/KYLIN-3030 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: peng.jianhua >Assignee: peng.jianhua > Labels: patch > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-3030-In-the-cubes-table-the-options-of-last-co.patch, > action_item_is_missing_partly1.png, action_item_is_missing_partly2.png > > > 1. Open the Model page; > 2. Choose one cube in table, and click the "Action" button, then you can find > serveral options, just like "Edit CubeDesc", "View Cube"; > 3. Then you can find the "Edit CubeDesc" option is missing partly, refer to > [^action_item_is_missing_partly1.png]; > 4. If you zoom out the browser window, you can even find not only "Edit > CubeDesc" but also "View Cube" is missing partly, refer to > [^action_item_is_missing_partly2.png] > So we can modify cubes.html, add the margin-right setting for div, which can > give more space to options. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-1533) UI doesn't support drop a cube for who is admin for that cube
[ https://issues.apache.org/jira/browse/KYLIN-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264230#comment-16264230 ] Zhixiong Chen commented on KYLIN-1533: -- Sorry for late to review this patch. This patch is fine for me. > UI doesn't support drop a cube for who is admin for that cube > - > > Key: KYLIN-1533 > URL: https://issues.apache.org/jira/browse/KYLIN-1533 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong > Attachments: addDropFunc.patch > > > For a cube, its admin can drop it through rest API. However, UI doesn't > support it for the admin. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KYLIN-3017) Footer covers the selection box and some options can not be selected
[ https://issues.apache.org/jira/browse/KYLIN-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256530#comment-16256530 ] Zhixiong Chen edited comment on KYLIN-3017 at 11/23/17 7:37 AM: Hi,[~peng.jianhua] This patch will let selection box covers the footer. !MG113.jpeg! Maybe you could modify the 'position' style. was (Author: zhixiong chen): This patch will let selection box covers the footer. Maybe you could modify the 'position' style. > Footer covers the selection box and some options can not be selected > > > Key: KYLIN-3017 > URL: https://issues.apache.org/jira/browse/KYLIN-3017 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.3.0 > Environment: Chrome >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Trivial > Attachments: > 0001-KYLIN-3017-Footer-covers-the-selection-box-and-some-.patch, > 2017-11-07.PNG, MG113.jpeg > > > Footer covers the selection box and some options can not be selected -- This message was sent by Atlassian JIRA (v6.4.14#64029)
