Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warn message about Scoped meta share #51

Open
zhfeng opened this issue Dec 20, 2024 · 0 comments
Open

Warn message about Scoped meta share #51

zhfeng opened this issue Dec 20, 2024 · 0 comments

Comments

@zhfeng
Copy link
Contributor

zhfeng commented Dec 20, 2024

There is a WARN message like

2024-12-20 01:02:38 WARN  FuryBuilder:392 [executor-thread-1] - Scoped meta share is for CompatibleMode only, disable it for SCHEMA_CONSISTENT

since we add the compatibleMode property with the default value of SCHEMA_CONSISTENT.

chaokunyang pushed a commit to apache/fury that referenced this issue Dec 20, 2024
#1985)

…and not in CompatibleMode

<!--
**Thanks for contributing to Fury.**

**If this is your first time opening a PR on fury, you can refer to
[CONTRIBUTING.md](https://github.com/apache/fury/blob/main/CONTRIBUTING.md).**

Contribution Checklist

- The **Apache Fury (incubating)** community has restrictions on the
naming of pr titles. You can also find instructions in
[CONTRIBUTING.md](https://github.com/apache/fury/blob/main/CONTRIBUTING.md).

- Fury has a strong focus on performance. If the PR you submit will have
an impact on performance, please benchmark it first and provide the
benchmark result here.
-->

## What does this PR do?

<!-- Describe the purpose of this PR. -->

## Related issues

- quarkiverse/quarkus-fury#51

## Does this PR introduce any user-facing change?

<!--
If any user-facing interface changes, please [open an
issue](https://github.com/apache/fury/issues/new/choose) describing the
need to do so and update the document if necessary.
-->

- [ ] Does this PR introduce any public API change?
- [ ] Does this PR introduce any binary protocol compatibility change?

## Benchmark

<!--
When the PR has an impact on performance (if you don't know whether the
PR will have an impact on performance, you can submit the PR first, and
if it will have impact on performance, the code reviewer will explain
it), be sure to attach a benchmark data here.
-->
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

No branches or pull requests

1 participant