[jira] [Commented] (KYLIN-5676) If the query matches an index that is not built, the front-end prompts you
[ https://issues.apache.org/jira/browse/KYLIN-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751000#comment-17751000 ] ASF GitHub Bot commented on KYLIN-5676: --- LauraXia123 opened a new pull request, #2144: URL: https://github.com/apache/kylin/pull/2144 ## 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. ## Branch to commit - [ ] Branch **kylin3** for v2.x to v3.x - [ ] Branch **kylin4** for v4.x - [ ] Branch **kylin5** for v5.x ## 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 created 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 - [ ] I have added necessary documentation (if appropriate) - [ ] Any dependent changes have been merged ## Further comments If this is a relatively large or complex change, kick off the discussion at u...@kylin.apache.org or d...@kylin.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc... > If the query matches an index that is not built, the front-end prompts you > -- > > Key: KYLIN-5676 > URL: https://issues.apache.org/jira/browse/KYLIN-5676 > Project: Kylin > Issue Type: Bug >Reporter: Laura Xia >Assignee: Laura Xia >Priority: Major > Fix For: 5.0-beta > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [kylin] LauraXia123 opened a new pull request, #2144: KYLIN-5676,KYLIN-5677,KYLIN-5678,KYLIN-5679,KYLIN-5680 Table index issue some issues
LauraXia123 opened a new pull request, #2144: URL: https://github.com/apache/kylin/pull/2144 ## 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. ## Branch to commit - [ ] Branch **kylin3** for v2.x to v3.x - [ ] Branch **kylin4** for v4.x - [ ] Branch **kylin5** for v5.x ## 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 created 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 - [ ] I have added necessary documentation (if appropriate) - [ ] Any dependent changes have been merged ## Further comments If this is a relatively large or complex change, kick off the discussion at u...@kylin.apache.org or d...@kylin.apache.org 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. To unsubscribe, e-mail: issues-unsubscr...@kylin.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (KYLIN-5680) Logical view with Chinese name sampling or building exception
[ https://issues.apache.org/jira/browse/KYLIN-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laura Xia updated KYLIN-5680: - Fix Version/s: 5.0-beta > Logical view with Chinese name sampling or building exception > - > > Key: KYLIN-5680 > URL: https://issues.apache.org/jira/browse/KYLIN-5680 > Project: Kylin > Issue Type: Bug >Reporter: Laura Xia >Assignee: Laura Xia >Priority: Major > Fix For: 5.0-beta > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (KYLIN-5680) Logical view with Chinese name sampling or building exception
[ https://issues.apache.org/jira/browse/KYLIN-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laura Xia reassigned KYLIN-5680: Assignee: Laura Xia > Logical view with Chinese name sampling or building exception > - > > Key: KYLIN-5680 > URL: https://issues.apache.org/jira/browse/KYLIN-5680 > Project: Kylin > Issue Type: Bug >Reporter: Laura Xia >Assignee: Laura Xia >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KYLIN-5680) Logical view with Chinese name sampling or building exception
Laura Xia created KYLIN-5680: Summary: Logical view with Chinese name sampling or building exception Key: KYLIN-5680 URL: https://issues.apache.org/jira/browse/KYLIN-5680 Project: Kylin Issue Type: Bug Reporter: Laura Xia -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [kylin] hit-lacus merged pull request #2143: Kylin5 beta release
hit-lacus merged PR #2143: URL: https://github.com/apache/kylin/pull/2143 -- 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. To unsubscribe, e-mail: issues-unsubscr...@kylin.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [kylin] hit-lacus opened a new pull request, #2143: Kylin5 beta release
hit-lacus opened a new pull request, #2143: URL: https://github.com/apache/kylin/pull/2143 ## 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. ## Branch to commit - [ ] Branch **kylin3** for v2.x to v3.x - [ ] Branch **kylin4** for v4.x - [ ] Branch **kylin5** for v5.x ## 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 created 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 - [ ] I have added necessary documentation (if appropriate) - [ ] Any dependent changes have been merged ## Further comments If this is a relatively large or complex change, kick off the discussion at u...@kylin.apache.org or d...@kylin.apache.org 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. To unsubscribe, e-mail: issues-unsubscr...@kylin.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [kylin] hit-lacus closed pull request #2140: Kylin 5.0 beta
hit-lacus closed pull request #2140: Kylin 5.0 beta URL: https://github.com/apache/kylin/pull/2140 -- 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. To unsubscribe, e-mail: issues-unsubscr...@kylin.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
