[jira] [Commented] (KYLIN-4550) Provide advanced refresh interface inside the refresh panel
[ https://issues.apache.org/jira/browse/KYLIN-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17216197#comment-17216197 ] Xiaoxiang Yu commented on KYLIN-4550: - Resolved in release 3.1.1 (2020-10-18) > Provide advanced refresh interface inside the refresh panel > --- > > Key: KYLIN-4550 > URL: https://issues.apache.org/jira/browse/KYLIN-4550 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Zhong Yanghong >Assignee: Julian Pan >Priority: Major > Fix For: v3.1.1 > > > Currently for cube refresh, only single segment is allowed in the web portal. > Users may want to refresh multiple segments at once with single job. > Therefore, it's better to provide an advanced refresh interface, which can > refresh multiple segments' data and finally comes to one bigger segment. For > this advanced refresh interface, the starting time should be alined with the > boundary of existing segments, and the ending time should be larger than the > starting time and also should be alined with the boundary of existing > segments or larger than the biggest ending time of existing segments. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-4550) Provide advanced refresh interface inside the refresh panel
[ https://issues.apache.org/jira/browse/KYLIN-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182223#comment-17182223 ] Shao Feng Shi commented on KYLIN-4550: -- This is very helpful; User can do refresh + merge in one step. Kylin already support that, but the front web page didn't provide the option, now it comes. Thanks Julian. > Provide advanced refresh interface inside the refresh panel > --- > > Key: KYLIN-4550 > URL: https://issues.apache.org/jira/browse/KYLIN-4550 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Zhong Yanghong >Assignee: Julian Pan >Priority: Major > Fix For: v3.1.1 > > > Currently for cube refresh, only single segment is allowed in the web portal. > Users may want to refresh multiple segments at once with single job. > Therefore, it's better to provide an advanced refresh interface, which can > refresh multiple segments' data and finally comes to one bigger segment. For > this advanced refresh interface, the starting time should be alined with the > boundary of existing segments, and the ending time should be larger than the > starting time and also should be alined with the boundary of existing > segments or larger than the biggest ending time of existing segments. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-4550) Provide advanced refresh interface inside the refresh panel
[ https://issues.apache.org/jira/browse/KYLIN-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182221#comment-17182221 ] ASF subversion and git services commented on KYLIN-4550: Commit 571466a7aa9a6ba4d91a5e588543c1ee8fea3508 in kylin's branch refs/heads/master from Julian Pan [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=571466a ] KYLIN-4550 Provide advanced refresh interface inside the refresh panel > Provide advanced refresh interface inside the refresh panel > --- > > Key: KYLIN-4550 > URL: https://issues.apache.org/jira/browse/KYLIN-4550 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Zhong Yanghong >Assignee: Julian Pan >Priority: Major > Fix For: v3.1.1 > > > Currently for cube refresh, only single segment is allowed in the web portal. > Users may want to refresh multiple segments at once with single job. > Therefore, it's better to provide an advanced refresh interface, which can > refresh multiple segments' data and finally comes to one bigger segment. For > this advanced refresh interface, the starting time should be alined with the > boundary of existing segments, and the ending time should be larger than the > starting time and also should be alined with the boundary of existing > segments or larger than the biggest ending time of existing segments. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-4550) Provide advanced refresh interface inside the refresh panel
[ https://issues.apache.org/jira/browse/KYLIN-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1718#comment-1718 ] ASF GitHub Bot commented on KYLIN-4550: --- shaofengshi merged pull request #1287: URL: https://github.com/apache/kylin/pull/1287 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Provide advanced refresh interface inside the refresh panel > --- > > Key: KYLIN-4550 > URL: https://issues.apache.org/jira/browse/KYLIN-4550 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: Zhong Yanghong >Assignee: Julian Pan >Priority: Major > Fix For: v3.1.1 > > > Currently for cube refresh, only single segment is allowed in the web portal. > Users may want to refresh multiple segments at once with single job. > Therefore, it's better to provide an advanced refresh interface, which can > refresh multiple segments' data and finally comes to one bigger segment. For > this advanced refresh interface, the starting time should be alined with the > boundary of existing segments, and the ending time should be larger than the > starting time and also should be alined with the boundary of existing > segments or larger than the biggest ending time of existing segments. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-4550) Provide advanced refresh interface inside the refresh panel
[ https://issues.apache.org/jira/browse/KYLIN-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147293#comment-17147293 ] ASF GitHub Bot commented on KYLIN-4550: --- coveralls commented on pull request #1287: URL: https://github.com/apache/kylin/pull/1287#issuecomment-650728964 ## Pull Request Test Coverage Report for [Build 6076](https://coveralls.io/builds/31731357) * **0** of **0** changed or added relevant lines in **0** files are covered. * **6** unchanged lines in **2** files lost coverage. * Overall coverage increased (+**0.004%**) to **27.979%** --- | Files with Coverage Reduction | New Missed Lines | % | | :-|--|--: | | [core-cube/src/main/java/org/apache/kylin/cube/inmemcubing/MemDiskStore.java](https://coveralls.io/builds/31731357/source?filename=core-cube%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Fcube%2Finmemcubing%2FMemDiskStore.java#L449) | 3 | 78.42% | | [tool/src/main/java/org/apache/kylin/tool/query/ProbabilityGenerator.java](https://coveralls.io/builds/31731357/source?filename=tool%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fkylin%2Ftool%2Fquery%2FProbabilityGenerator.java#L42) | 3 | 77.78% | | Totals | [](https://coveralls.io/builds/31731357) | | :-- | --: | | Change from base [Build 6065](https://coveralls.io/builds/31633725): | 0.004% | | Covered Lines: | 26113 | | Relevant Lines: | 93331 | --- # 💛 - [Coveralls](https://coveralls.io) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Provide advanced refresh interface inside the refresh panel > --- > > Key: KYLIN-4550 > URL: https://issues.apache.org/jira/browse/KYLIN-4550 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: Julian Pan >Priority: Major > > Currently for cube refresh, only single segment is allowed in the web portal. > Users may want to refresh multiple segments at once with single job. > Therefore, it's better to provide an advanced refresh interface, which can > refresh multiple segments' data and finally comes to one bigger segment. For > this advanced refresh interface, the starting time should be alined with the > boundary of existing segments, and the ending time should be larger than the > starting time and also should be alined with the boundary of existing > segments or larger than the biggest ending time of existing segments. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-4550) Provide advanced refresh interface inside the refresh panel
[ https://issues.apache.org/jira/browse/KYLIN-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147270#comment-17147270 ] ASF GitHub Bot commented on KYLIN-4550: --- sanjulian opened a new pull request #1287: URL: https://github.com/apache/kylin/pull/1287 ## Proposed changes Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue. ## Types of changes What types of changes does your code introduce to Kylin? _Put an `x` in the boxes that apply_ - [ ] Bugfix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Documentation Update (if none of the other choices apply) ## Checklist _Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code._ - [ ] I have create an issue on [Kylin's jira](https://issues.apache.org/jira/browse/KYLIN), and have described the bug/feature there in detail - [ ] Commit messages in my PR start with the related jira ID, like "KYLIN- Make Kylin project open-source" - [ ] Compiling and unit tests pass locally with my changes - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] If this change need a document change, I will prepare another pr against the `document` branch - [ ] Any dependent changes have been merged ## Further comments If this is a relatively large or complex change, kick off the discussion at user@kylin or dev@kylin by explaining why you chose the solution you did and what alternatives you considered, etc... This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Provide advanced refresh interface inside the refresh panel > --- > > Key: KYLIN-4550 > URL: https://issues.apache.org/jira/browse/KYLIN-4550 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: Julian Pan >Priority: Major > > Currently for cube refresh, only single segment is allowed in the web portal. > Users may want to refresh multiple segments at once with single job. > Therefore, it's better to provide an advanced refresh interface, which can > refresh multiple segments' data and finally comes to one bigger segment. For > this advanced refresh interface, the starting time should be alined with the > boundary of existing segments, and the ending time should be larger than the > starting time and also should be alined with the boundary of existing > segments or larger than the biggest ending time of existing segments. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-4550) Provide advanced refresh interface inside the refresh panel
[ https://issues.apache.org/jira/browse/KYLIN-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146122#comment-17146122 ] Julian Pan commented on KYLIN-4550: --- [https://github.com/sanjulian/kylin/tree/KYLIN-4550] > Provide advanced refresh interface inside the refresh panel > --- > > Key: KYLIN-4550 > URL: https://issues.apache.org/jira/browse/KYLIN-4550 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: Julian Pan >Priority: Major > > Currently for cube refresh, only single segment is allowed in the web portal. > Users may want to refresh multiple segments at once with single job. > Therefore, it's better to provide an advanced refresh interface, which can > refresh multiple segments' data and finally comes to one bigger segment. For > this advanced refresh interface, the starting time should be alined with the > boundary of existing segments, and the ending time should be larger than the > starting time and also should be alined with the boundary of existing > segments or larger than the biggest ending time of existing segments. -- This message was sent by Atlassian Jira (v8.3.4#803005)
