Skip to content
GitLab
Switch branch/tag
This project is mirrored from https://gitee.com/yxydde/incubator-kyuubi.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
  1. 16 Mar, 2022 3 commits
  3. 15 Mar, 2022 1 commit
  5. 14 Mar, 2022 1 commit
    • sychen's avatar
      [KYUUBI #2125] closeSession should avoid sending RPC after openSession fails · ed177fc5
      sychen authored 
      ### _Why are the changes needed?_
https://github.com/apache/incubator-kyuubi/issues/2125

Now after the `openSession` call fails, `closeSession` is called. But because there is no `_remoteSessionHandle`, the `CloseSession` RPC request fails.
This does not need to send RPC and also increases the complexity of logging.

```
org.apache.kyuubi.KyuubiSQLException: Error while cleaning up the engine resources
        at org.apache.kyuubi.KyuubiSQLException$.apply(KyuubiSQLException.scala:69)
        at org.apache.kyuubi.session.KyuubiSessionImpl.close(KyuubiSessionImpl.scala:156)
        at org.apache.kyuubi.session.KyuubiSessionManager.openSession(KyuubiSessionManager.scala:75)
        at org.apache.kyuubi.service.AbstractBackendService.openSession(AbstractBackendService.scala:45)
        at org.apache.kyuubi.service.ThriftBinaryFrontendService.getSessionHandle(ThriftBinaryFrontendService.scala:199)
```

### _How was this patch tested?_
- [ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

- [x] Add screenshots for manual tests if appropriate

- [x] [Run test](https://kyuubi.apache.org/docs/latest/develop_tools/testing.html#running-tests

) locally before make a pull request

Closes #2126 from cxzl25/KYUUBI-2125.

Closes #2125

2e96f418 [sychen] optimize closeSession
Authored-by: default avatarsychen <sychen@trip.com>
Signed-off-by: default avatarKent Yao <yao@apache.org>
(cherry picked from commit 8c85480b

)
Signed-off-by: default avatarKent Yao <yao@apache.org>
      ed177fc5
  7. 12 Mar, 2022 3 commits
  9. 11 Mar, 2022 3 commits
  11. 10 Mar, 2022 3 commits
  13. 09 Mar, 2022 2 commits
    • Fei Wang's avatar
      [KYUUBI #2075] Using thread-safe FastDateFormat instead of SimpleDateFormat · 4a54b18d
      Fei Wang authored 
      
### _Why are the changes needed?_

We met below issue when fetching result.

```
Caused by: java.lang.RuntimeException: java.lang.ArrayIndexOutOfBoundsException:46
7022	at sun.util.calendar.BaseCalendar.getCalendarDateFromFixedDate(BaseCalendar.java:453)
7023	at java.util.GregorianCalendar.computeFields(GregorianCalendar.java:2397)
7024	at java.util.GregorianCalendar.computeFields(GregorianCalendar.java:2312)
7025	at java.util.Calendar.setTimeInMillis(Calendar.java:1804)
7026	at java.util.Calendar.setTime(Calendar.java:1770)
7027	at java.text.SimpleDateFormat.format(SimpleDateFormat.java:943)
7028	at java.text.SimpleDateFormat.format(SimpleDateFormat.java:936)
7029	at java.text.DateFormat.format(DateFormat.java:345)
7030	at org.apache.kyuubi.schema.RowSet$.toHiveString(RowSet.scala:245)
7031	at org.apache.kyuubi.schema.RowSet$.$anonfun$toTColumn$3(RowSet.scala:120)
7032	at scala.collection.immutable.List.map(List.scala:290)
7033	at org.apache.kyuubi.schema.RowSet$.toTColumn(RowSet.scala:115)
7034	at org.apache.kyuubi.schema.RowSet$.$anonfun$toColumnBasedSet$1(RowSet.scala:65)
7035	at org.apache.kyuubi.schema.RowSet$.$anonfun$toColumnBasedSet$1$adapted(RowSet.scala:64)
7036	at scala.collection.immutable.List.foreach(List.scala:392)
7037	at org.apache.kyuubi.schema.RowSet$.toColumnBasedSet(RowSet.scala:64)
7038	at org.apache.kyuubi.schema.RowSet$.toTRowSet(RowSet.scala:47)
7039	at org.apache.kyuubi.engine.spark.operation.SparkOperation.getNextRowSet(SparkOperation.scala:183)
7040	at org.apache.kyuubi.operation.OperationManager.getOperationNextRowSet(OperationManager.scala:116)
7041	at org.apache.kyuubi.session.AbstractSession.fetchResults(AbstractSession.scala:197)
7042	at org.apache.kyuubi.service.AbstractBackendService.fetchResults(AbstractBackendService.scala:169)
7043	at org.apache.kyuubi.service.ThriftBinaryFrontendService.FetchResults(ThriftBinaryFrontendService.scala:505)
```

The root cause is that the date time formatter used to convert the result to rowSet is not thread-safe.
In this pr, we use thread-safe FastDateFormat instead of SimpleDateFormat.

### _How was this patch tested?_
Existing UT.

Closes #2075 from turboFei/thread_safe_fat_stimeformatter.

Closes #2075

44ae8fd1 [Fei Wang] Using thread-safe FastDateFormat instead of SimpleDateFormat
Authored-by: default avatarFei Wang <fwang12@ebay.com>
Signed-off-by: default avatarKent Yao <yao@apache.org>
(cherry picked from commit 5a64e124

)
Signed-off-by: default avatarKent Yao <yao@apache.org>
      4a54b18d
    • yanghua's avatar
      [KYUUBI #2063] Fix engine idle timeout lose efficacy for Flink Engine · 6f98cc21
      yanghua authored 
      ### _Why are the changes needed?_

### _How was this patch tested?_
- [ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

- [ ] Add screenshots for manual tests if appropriate

- [ ] [Run test](https://kyuubi.apache.org/docs/latest/develop_tools/testing.html#running-tests

) locally before make a pull request

Closes #2064 from yanghua/KYUUBI-2063.

Closes #2063

35ea82cf [yanghua] [KYUUBI #2063] Fix engine idle timeout lose efficacy for Flink Engine
Authored-by: default avataryanghua <yanghua1127@gmail.com>
Signed-off-by: default avatarKent Yao <yao@apache.org>
(cherry picked from commit dde83819

)
Signed-off-by: default avatarKent Yao <yao@apache.org>
      6f98cc21
  15. 08 Mar, 2022 4 commits
  17. 07 Mar, 2022 2 commits
  19. 05 Mar, 2022 6 commits
  21. 04 Mar, 2022 3 commits
  23. 03 Mar, 2022 6 commits
    • HYBG-1126's avatar
      [KYUUBI #1999] Update quick_start_with_helm.md · 85d515db
      HYBG-1126 authored 
      cretate ns kyuubi ---> create ns kyuubi

### _Why are the changes needed?_

### _How was this patch tested?_
- [ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

- [ ] Add screenshots for manual tests if appropriate

- [ ] [Run test](https://kyuubi.apache.org/docs/latest/develop_tools/testing.html#running-tests

) locally before make a pull request

Closes #1999 from HYBG-1126/patch-1.

Closes #1999

f68f73e9 [HYBG] Update quick_start_with_helm.md
Lead-authored-by: default avatarHYBG-1126 <hybg1126@outlook.com>
Co-authored-by: default avatarHYBG <44338121+HYBG-1126@users.noreply.github.com>
Signed-off-by: default avatarCheng Pan <chengpan@apache.org>
      85d515db
    • Ada Wong's avatar
      [KYUUBI #2000][DEPS] Bump Hadoop 3.3.2 · e250c4ae
      Ada Wong authored 
      ### _Why are the changes needed?_

Hadoop 3.3.2 is out.

### _How was this patch tested?_
- [ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

- [ ] Add screenshots for manual tests if appropriate

- [x] [Run test](https://kyuubi.apache.org/docs/latest/develop_tools/testing.html#running-tests

) locally before make a pull request

Closes #2003 from deadwind4/KYUUBI-2000.

Closes #2000

3b5b3f85 [Ada Wong] [KYUUBI #2000][DEPS] Bump Hadoop 3.3.2
Authored-by: default avatarAda Wong <rsl4@foxmail.com>
Signed-off-by: default avatarCheng Pan <chengpan@apache.org>
      e250c4ae
    • Kent Yao's avatar
      [KYUUBI #2004] Sync contents for CONTRIBUTING & COMMUNITY between web and main repo · 114fefef
      Kent Yao authored 
      <!--
Thanks for sending a pull request!

Here are some tips for you:
  1. If this is your first time, please read our contributor guidelines: https://kyuubi.readthedocs.io/en/latest/community/contributions.html
  2. If the PR is related to an issue in https://github.com/apache/incubator-kyuubi/issues, add '[KYUUBI #XXXX]' in your PR title, e.g., '[KYUUBI #XXXX] Your PR title ...'.
  3. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP][KYUUBI #XXXX] Your PR title ...'.
-->

### _Why are the changes needed?_
<!--
Please clarify why the changes are needed. For instance,
  1. If you add a feature, you can talk about the use case of it.
  2. If you fix a bug, you can clarify why it is a bug.
-->

Add CONTRIBUTING.md to list COMMUNITY resources that I contributor can use
delete contributions and improvement-proposal in main repo

### _How was this patch tested?_
- [ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

- [ ] Add screenshots for manual tests if appropriate

- [x] [Run test](https://kyuubi.apache.org/docs/latest/develop_tools/testing.html#running-tests

) locally before make a pull request

Closes #2004 from yaooqinn/CONTRIBUTING.

Closes #2004

ddbcd521 [Kent Yao] CONTRIBUTING
f81c14b3 [Kent Yao] Merge branch 'master' of github.com:apache/incubator-kyuubi into CONTRIBUTING
3bdbdc9b [Kent Yao] CONTRIBUTING
574ceff2 [Kent Yao] CONTRIBUTING
f0a6b4c4 [Kent Yao] CONTRIBUTING
c55c6a02 [Kent Yao] CONTRIBUTING
Authored-by: default avatarKent Yao <yao@apache.org>
Signed-off-by: default avatarulysses-you <ulyssesyou@apache.org>
      114fefef
    • Cheng Pan's avatar
      [KYUUBI #1996] Clean up log4j2 conf and enhance surefire plugin conf · 7887a47e
      Cheng Pan authored 
      ### _Why are the changes needed?_

[THRIFT-4805](https://issues.apache.org/jira/browse/THRIFT-4805) has been fixed in thrift 0.13.0, we can remove the workaround of log4j2 configurations because we use thrift 0.16.0 now, the change also removes the following warnings.

```
2022-03-01 23:18:16,530 main ERROR Filters contains invalid attributes "onMatch", "onMismatch"
2022-03-01 23:18:16,543 main ERROR Filters contains invalid attributes "onMatch", "onMismatch"
```

`maven-surefire-plugin` is only used in `kyuubi-hive-jdbc`, we should disable it in other modules.

```
[INFO] --- maven-surefire-plugin:2.22.0:test (default-test)  kyuubi-ctl_2.12 ---
[INFO]
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
2022-03-01 23:18:16,530 main ERROR Filters contains invalid attributes "onMatch", "onMismatch"
2022-03-01 23:18:16,543 main ERROR Filters contains invalid attributes "onMatch", "onMismatch"
[INFO] Running org.apache.kyuubi.ctl.ServiceControlCliSuite
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 s - in org.apache.kyuubi.ctl.ServiceControlCliSuite
[INFO] Running org.apache.kyuubi.ctl.ServiceControlCliArgumentsSuite
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.apache.kyuubi.ctl.ServiceControlCliArgumentsSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
```

### _How was this patch tested?_
- [ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

- [ ] Add screenshots for manual tests if appropriate

- [ ] [Run test](https://kyuubi.apache.org/docs/latest/develop_tools/testing.html#running-tests

) locally before make a pull request

Closes #1996 from pan3793/log.

Closes #1996

291441c0 [Cheng Pan] nit
f2c94246 [Cheng Pan] Tune surefire plugin in conf
e1ee6402 [Cheng Pan] Clean up log4j2 conf
Authored-by: default avatarCheng Pan <chengpan@apache.org>
Signed-off-by: default avatarCheng Pan <chengpan@apache.org>
      7887a47e
    • Kent Yao's avatar
      [KYUUBI #1986] Apache Kyuubi(Incubating) Maturity Self Assessment · 5d400ea3
      Kent Yao authored 
      ### _Why are the changes needed?_

# Apache Kyuubi(Incubating) Maturity Self Assessment

## Overview

This is an assessment of the overall maturity of Apache Kyuubi(Incubating) as an Apache project, meant to inform the decision (of mentors, community, incubator PMCs, and ASF Board of Directors) to graduate Kyuubi as a top-level Apache project. It is based on the [Apache Project Maturity Model](https://community.apache.org/apache-way/apache-project-maturity-model.html).

Mentors and community members are encouraged to contribute to this page and comment on it, the following tables summarize our self-assessment against the **Apache Project Maturity Model**.

✅ means that the related item is in good status.
⬜ means that the related item need long-term attention.
❌ means that the related item need to be fixed ASAP.

## Code

| ID  | Description                                                                                                                                                                                                                                                     | Status                                                                                                                                                                                                                                                                                                                                                                                       |
|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| C10 | The project produces Open Source software for distribution to the public, at no charge.                                                                                                                                                                         | ✅ The project source code is licensed under the [Apache License, v2.0](https://github.com/apache/incubator-kyuubi/blob/master/LICENSE)                                                                                                                                                                                                                                      |
| C20 | Anyone can easily discover and access the project's code.                                                                                                                                                                                                       | ❌ The source code is available on GitHub directly, ‼ Missing link on website                                                                                                                                                                                                                                                                                                      |
| C30 | Anyone using standard, widely-available tools, can build the code in a reproducible way.                                                                                                                                                                        | ❌ The source code is automatically built for each Pull Request commit, with license checks, style checks, doc builds unit and end to end tests, via GitHub actions and Travis. Development environment setup and build instructions to do the same locally are documented on the [website](https://kyuubi.apache.org/developer-tools.html). ‼ The side is not sync with codebase. |
| C40 | The full history of the project's code is available via a source code control system, in a way that allows anyone to recreate any released version.                                                                                                             | ✅ The project uses git to manage source code, documentation and website, all releases are tagged. The commit history is available from the beginning of the project.                                                                                                                                                                                                        |
| C50 | The source code control system establishes the provenance of each line of code in a reliable way, based on strong authentication of the committer. When third parties contribute code, commit messages provide reliable information about the code provenance.  | ✅ The project uses GitHub which managed by Apache Infra, it ensuring provenance of each line of code to a committer. All code is checked in after review and approval via GitHub pull requests.                                                                                                                                                                             |

## Licenses and Copyright

| ID   | Description                                                                                                                                                                       | Status                                                                                                                                                                                                                                            |
|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| LC10 | The Apache License, version 2.0, covers the released code.                                                                                                                        | ✅ The [LICENSE file](https://github.com/apache/incubator-kyuubi/blob/master/LICENSE) is in GitHub repository. [All releases](https://kyuubi.apache.org/releases.html) are verified by IPMC to contain the copy.                  |
| LC20 | Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does.                                                     | ✅ [The list of mandatory dependencies](https://github.com/apache/incubator-kyuubi/tree/master/licenses-binary) have been reviewed to contain approved and compatible licenses only.                                              |
| LC30 | The libraries mentioned in LC20 are available as Open Source software.                                                                                                            | ✅ All mandatory dependencies listed in L20 are available as open source software.                                                                                                                                                |
| LC40 | Committers are bound by an Individual Contributor Agreement (the "Apache iCLA") that defines which code they may commit and how they need to identify code that is not their own. | ✅ All committers have iCLAs on file before they have an apache account.                                                                                                                                                          |
| LC50 | The project clearly defines and documents the copyright ownership of everything that the project produces.                                                                        | ✅ All files in the source repository have appropriate headers. [The Github workflow](https://github.com/apache/incubator-kyuubi/actions/workflows/license.yml) is in place to ensure every file has the expected license header. |

## Releases

| ID   | Description                                                                                                                                                            | Status                                                                                                                                                                                                                                                                                    |
|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| RE10 | Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term.                              | ✅ Recent releases are available via the [download page](https://kyuubi.apache.org/releases.html) on the website. All releases are available via the [apache archive](https://archive.apache.org/dist/incubator/kyuubi/).                                                 |
| RE20 | The project's PMC (Project Management Committee, see CS10) approves each software release in order to make the release an act of the Foundation.                       | ✅ All incubating releases have been approved by the Kyuubi community and the Incubator, all with at least 3 PPMC/IPMC votes and more +1 than -1.                                                                                                                         |
| RE30 | Releases are signed and/or distributed along with digests that anyone can reliably use to validate the downloaded archives.                                            | ✅ [Releases](https://kyuubi.apache.org/releases.html) are signed, the [keys](https://downloads.apache.org/incubator/kyuubi/KEYS) are available from the download page. Every release has a corresponding hash(sha512) to prevent content tampering.                      |
| RE40 | The project can distribute convenience binaries alongside source code, but they are not Apache Releases, they are provided with no guarantee.                          | ✅ Convenience binaries are distributed alongside source code at the same time via <ul><li>[Maven Central Repository](https://mvnrepository.com/artifact/org.apache.kyuubi)</li><li>[DockerHub](https://hub.docker.com/r/apache/kyuubi)</li><li>dist.apache.org</li></ul> |
| RE50 | The project documents a repeatable release process so that someone new to the project can independently generate the complete set of artifacts required for a release. | ✅ [Release guide](https://github.com/apache/incubator-kyuubi/blob/master/docs/community/release.md) is available. The releases of the project have been performed by 4 different release managers.                                                                       |

## Quality

| ID   | Description                                                                                                                                                                                    | Status                                                                                                                                                           |
|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| QU10 | The project is open and honest about the quality of its code. Various levels of quality and maturity for various modules are natural and acceptable as long as they are clearly communicated.  | ✅ All issues are tracked on Kyuubi's GitHub [Issues](https://github.com/apache/incubator-kyuubi/issues).                                        |
| QU20 | The project puts a very high priority on producing secure software.                                                                                                                            | ✅ Security issues are treated with the highest priority. We use Apache's default way to submit security related information.                    |
| QU30 | The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them.                                               | ✅ Website provides a link to https://www.apache.org/security/                                                                                   |
| QU40 | The project puts a high priority on backwards compatibility and aims to document any incompatible changes and provide tools and documentation to help users transition to new features.        | ✅ Each release note contains all related issues and pull requests in the milestone, and extract mainly updates and API changes from milestones. |
| QU50 | The project strives to respond to documented bug reports in a timely manner.                                                                                                                   | ✅ The community is very active in responding to bug reports and usually fixes them within a short time period.                                  |

## Community

| ID   | Description                                                                                                                                                            | Status                                                                                                                                                                                                                                |
|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| CO10 | The project has a well-known homepage that points to all the information required to operate according to this maturity model.                                         | ✅ The website describes of the project with download, user manual, technical details, how to contribute and team introduce.                                                                                          |
| CO20 | The community welcomes contributions from anyone who acts in good faith and in a respectful manner, and who adds value to the project.                                 | ⬜ Committers are really welcome contributions and the community is actively seeking for new committers. The community has elected 0 new PPMC members and 2 new committers during incubation, based on meritocracy. |
| CO30 | Contributions include source code, documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project. | ✅ The community welcomes all contributions. The contribution guide refers to non source code contribution. The community is very clear about contributions being more than code.                                     |
| CO40 | The community strives to be meritocratic and gives more rights and responsibilities to contributors who, over time, add value to the project.                          | ⬜. The community has elected 0 new PPMC members and 2 new committers during incubation, based on meritocracy.                                                                                                      |
| CO50 | The project documents how contributors can earn more rights such as commit access or decision power, and applies these principles consistently.                        | ❌ ~The process to become a committer or PPMC member is documented on the website~. see, https://community.apache.org/newcommitter.html                                                                                              |
| CO60 | The community operates based on consensus of its members (see CS10) who have decision power. Dictators, benevolent or not, are not welcome in Apache projects.         | ⬜ The project works to build consensus. All PPMC votes have been unanimous so far.                                                                                                                                 |
| CO70 | The project strives to answer user questions in a timely manner.                                                                                                       | ⬜ The project typically provides detailed answers to user questions within a few days via dev mailing list, GitHub issues and Github Discussions.                                                                  |

## Consensus Building

| ID   | Description                                                                                                                                                                                                               | Status                                                                                                                                                                                                            |
|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| CS10 | The project maintains a public list of its contributors who have decision power. The project's PMC (Project Management Committee) consists of those contributors.                                                         | ❌ ~Committers and PPMC members are listed on the website’s community page~                                                                                                                                      |
| CS20 | Decisions require a consensus among PMC members and are documented on the project's main communications channel. The PMC takes community opinions into account, but the PMC has the final word.                           | ✅ The project has been making important decisions on the mailing lists.                                                                                                                          |
| CS30 | The project uses documented voting rules to build consensus when discussion is not sufficient.                                                                                                                            | ✅ The project uses the standard ASF voting rules.                                                                                                                                                |
| CS40 | In Apache projects, vetoes are only valid for code commits. The person exercising the veto must justify it with a technical explanation, as per the Apache voting rules defined in CS30.                                  | ⬜ The project has not used a veto at any point during incubation.                                                                                                                              |
| CS50 | All "important" discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions that affect the project are also documented on that channel. | ⬜ The project has been making important decisions on the project mailing lists. Minor decisions may occasionally happen during code reviews, which are also asynchronous and in written form.  |

## Independence

| ID   | Description                                                                              | Status                                                                                                                                                                                                                                                                     |
|------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| IN10 | The project is independent from any corporate or organizational influence.               | ⬜ The project team gathers people from different companies (China Mobile, eBay, NetEase, T3). No company or organization has significantly more influence than any other. We can note a growth of the contributions coming from different contributors. |
| IN20 | Contributors act as themselves, not as representatives of a corporation or organization. | ✅

 The contributors act on their own initiative without representing a corporation or organization.                                                                                                                                                        |

### _How was this patch tested?_

Pending reviews by Kyuubi Mentors, PPMC, and community.

Closes #1986 from yaooqinn/MATURITY.

Closes #1986

1c76752a [Kent Yao] Apache Kyuubi(Incubating) Maturity Self Assessment
3ce62adf [Kent Yao] Apache Kyuubi(Incubating) Maturity Self Assessment
ac436ab3 [Kent Yao] Apache Kyuubi(Incubating) Maturity Self Assessment
Authored-by: default avatarKent Yao <yao@apache.org>
Signed-off-by: default avatarKent Yao <yao@apache.org>
      5d400ea3
    • Cheng Pan's avatar
      [KYUUBI #1988] Tune initialization of vars depend on system level confs · dfd71242
      Cheng Pan authored 
      <!--
Thanks for sending a pull request!

Here are some tips for you:
  1. If this is your first time, please read our contributor guidelines: https://kyuubi.readthedocs.io/en/latest/community/contributions.html
  2. If the PR is related to an issue in https://github.com/apache/incubator-kyuubi/issues, add '[KYUUBI #XXXX]' in your PR title, e.g., '[KYUUBI #XXXX] Your PR title ...'.
  3. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP][KYUUBI #XXXX] Your PR title ...'.
-->

### _Why are the changes needed?_
<!--
Please clarify why the changes are needed. For instance,
  1. If you add a feature, you can talk about the use case of it.
  2. If you fix a bug, you can clarify why it is a bug.
-->
The `new SparkConf()` and `KyuubiConf()` executes early than UT, and can not re-initialize after changing system properties, which makes conf overwriting does not work.

After the change, the `sparkConf.setIfMissing("spark.sql.catalogImplementation", defaultCat)` work as expected when we overwriting `spark.sql.catalogImplementation` in UT, and Hudi uses `in-memory` catalog to create table.

<img width="891" alt="Xnip2022-03-02_19-10-06" src="https://user-images.githubusercontent.com/26535726/156351805-bb403ee8-0b89-4db2-b91f-d7b2b9957838.png">

### _How was this patch tested?_
- [ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

- [ ] Add screenshots for manual tests if appropriate

- [ ] [Run test](https://kyuubi.apache.org/docs/latest/develop_tools/testing.html#running-tests

) locally before make a pull request

Closes #1995 from pan3793/lazy.

Closes #1988

c264a224 [Cheng Pan] Fix
d1a23fbc [Cheng Pan] Lazy initialize vars depends on system level confs
Authored-by: default avatarCheng Pan <chengpan@apache.org>
Signed-off-by: default avatarulysses-you <ulyssesyou@apache.org>
      dfd71242
  25. 02 Mar, 2022 1 commit
  27. 01 Mar, 2022 2 commits

免费DevSecOps平台，让您的项目体验完整的DevSecOps流程，让项目更安全