Skip to content

Conversation

@morningman
Copy link
Contributor

Use Catalog.getCurrentCatalog() instead, to avoid potential meta operation error.

Fix: #3778

This CL does not change any logic.

morningman and others added 2 commits June 5, 2020 11:28
Use Catalog.getCurrentCatalog() instead, to avoid potential meta operation error.
@morningman morningman added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. area/catalog Issues or PRs related to catalog management kind/refactor Issues or PRs to refactor code and removed kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Jun 5, 2020
Copy link
Contributor

@kangkaisen kangkaisen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1. LGTM

@kangkaisen kangkaisen added the approved Indicates a PR has been approved by one committer. label Jun 5, 2020
@imay imay merged commit 173dd39 into apache:master Jun 6, 2020
morningman added a commit to morningman/doris that referenced this pull request Jun 7, 2020
Use Catalog.getCurrentCatalog() instead, to avoid potential meta operation error.

Change-Id: If0f70e82a636390924f0217fd064ce17bce6fc3f
morningman added a commit that referenced this pull request Jun 20, 2020
This bug is introduced by PR #3784 
In #3784, I remove the `Catalog.getInstance()`, and use `Catalog.getCurrentCatalog()` instead.

But actually, there are some place that should use the serving catalog explicitly.

Mainly changed:

1. Add a new method `getServingCatalog()` to explicitly return the real catalog instance.
2. Fix a compile bug of broker introduced by #3881
morningman added a commit to morningman/doris that referenced this pull request Jun 22, 2020
This bug is introduced by PR apache#3784 
In apache#3784, I remove the `Catalog.getInstance()`, and use `Catalog.getCurrentCatalog()` instead.

But actually, there are some place that should use the serving catalog explicitly.

Mainly changed:

1. Add a new method `getServingCatalog()` to explicitly return the real catalog instance.
2. Fix a compile bug of broker introduced by apache#3881
acelyc111 pushed a commit to acelyc111/incubator-doris that referenced this pull request Jan 20, 2021
Use Catalog.getCurrentCatalog() instead, to avoid potential meta operation error.
acelyc111 pushed a commit to acelyc111/incubator-doris that referenced this pull request Jan 20, 2021
This bug is introduced by PR apache#3784
In apache#3784, I remove the `Catalog.getInstance()`, and use `Catalog.getCurrentCatalog()` instead.

But actually, there are some place that should use the serving catalog explicitly.

Mainly changed:

1. Add a new method `getServingCatalog()` to explicitly return the real catalog instance.
2. Fix a compile bug of broker introduced by apache#3881
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by one committer. area/catalog Issues or PRs related to catalog management kind/refactor Issues or PRs to refactor code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Catalog] Should not use getInstance() of Catalog anymore

4 participants