Skip to content

KYLIN-5633、KYLIN-5687~KYLIN-5700#2148

Closed
ygjia wants to merge 24 commits intoapache:kylin5from
ygjia:kylin5-batchpr-0821
Closed

KYLIN-5633、KYLIN-5687~KYLIN-5700#2148
ygjia wants to merge 24 commits intoapache:kylin5from
ygjia:kylin5-batchpr-0821

Conversation

@ygjia
Copy link
Contributor

@ygjia ygjia commented Aug 21, 2023

Proposed changes

issue list
https://issues.apache.org/jira/browse/KYLIN-5633
https://issues.apache.org/jira/browse/KYLIN-5687
https://issues.apache.org/jira/browse/KYLIN-5690
https://issues.apache.org/jira/browse/KYLIN-5691
https://issues.apache.org/jira/browse/KYLIN-5692
https://issues.apache.org/jira/browse/KYLIN-5693
https://issues.apache.org/jira/browse/KYLIN-5694
https://issues.apache.org/jira/browse/KYLIN-5695
https://issues.apache.org/jira/browse/KYLIN-5696
https://issues.apache.org/jira/browse/KYLIN-5697
https://issues.apache.org/jira/browse/KYLIN-5698
https://issues.apache.org/jira/browse/KYLIN-5699
https://issues.apache.org/jira/browse/KYLIN-5700

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, and have described the bug/feature there in detail
  • Commit messages in my PR start with the related jira ID, like "KYLIN-0000 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 user@kylin.apache.org or dev@kylin.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

sibingzhang and others added 24 commits August 15, 2023 16:27
…r groups

---------

Co-authored-by: Zhiting Guo <zhiting.guo@kyligence.io>
* KYLIN-5689 allow 'dev' profile to run without sandbox, just local spark and local fs
* KYLIN-5689 add h2 dependency to profile dev
* KYLIN-5689 support mock prod metadata

---------

Co-authored-by: Li Yang <liyang@apache.org>
1. upgrade nimbus-jose-jwt from 7.9 to 9.23
2. upgrade springboot framework from 2.6.14 to 2.7.12
…filter condition

---------

Co-authored-by: Guangyuan Feng <guangyuan.feng@kyligence.io>
---------

Co-authored-by: Guangyuan Feng <guangyuan.feng@kyligence.io>
…se sensitive, when importing models.

Co-authored-by: Guangyuan Feng <guangyuan.feng@kyligence.io>
1. upgrade tomcat-embed-core to 9.0.74
2. release spark
---------

Co-authored-by: Zhiting Guo <35057824+frearb@users.noreply.github.com>
Co-authored-by: Zhiting Guo <zhiting.guo@kyligence.io>
@ygjia ygjia force-pushed the kylin5-batchpr-0821 branch from a0ff621 to c9df548 Compare August 21, 2023 09:55
@ygjia ygjia closed this Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Comments