Skip to content

KYLIN-5376 transform OpenAPI datasource-manage fields [table/database…#2066

Merged
hit-lacus merged 1 commit intoapache:kylin5from
yabola:kylin-5376
Dec 26, 2022
Merged

KYLIN-5376 transform OpenAPI datasource-manage fields [table/database…#2066
hit-lacus merged 1 commit intoapache:kylin5from
yabola:kylin-5376

Conversation

@yabola
Copy link
Contributor

@yabola yabola commented Dec 23, 2022

…] from case sensitive to case insensitive

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, 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...

@yabola
Copy link
Contributor Author

yabola commented Dec 24, 2022

retest this please

3 similar comments
@yabola
Copy link
Contributor Author

yabola commented Dec 24, 2022

retest this please

@yabola
Copy link
Contributor Author

yabola commented Dec 24, 2022

retest this please

@yabola
Copy link
Contributor Author

yabola commented Dec 25, 2022

retest this please

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

66.7% 66.7% Coverage
0.0% 0.0% Duplication

@hit-lacus hit-lacus merged commit 21d4282 into apache:kylin5 Dec 26, 2022
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.

2 participants