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
IGNITE-19082: Catalog. Cleanup dead code #3669
Conversation
600d20a
to
f965bd9
Compare
await for catalog initialization i n system view manager.
update catalog tests.
update catalog tests.
await catalog activation.
await catalog activation.
await catalog activation.
await catalog activation.
await catalog activation.
await catalog activation.
fix some tests.
check style.
check style.
remove unsed SchemaRegistryImpl.
Use schemaId.
Use schemaId. Fix javadoc.
Fix check style error.
I have addressed this issue. |
code style.
Return completed futures.
@@ -49,18 +49,19 @@ public class NewColumnsEntry implements UpdateEntry, Fireable { | |||
|
|||
private final int tableId; | |||
private final List<CatalogTableColumnDescriptor> descriptors; | |||
private final String schemaName; | |||
private final int schemaId; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would delete schema at all because it creates ambiguity. It's better to derive schema from table (table descriptor has schemaId
).
The same for rest of the updateEntries
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
fix serde. removed schema id from new columns entry.
new CatalogTableDescriptor[0], | ||
new CatalogIndexDescriptor[0], | ||
new CatalogSystemViewDescriptor[0], | ||
0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
0 | |
INITIAL_CAUSALITY_TOKEN |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
Add tests.
Add tests.
Update tests.
Remove schema refs.
Remove schema refs.
Remove schema refs.
assertions.
@@ -33,7 +33,7 @@ | |||
* the {@link CatalogIndexStatus#STOPPING} state. | |||
*/ | |||
public class DropIndexEntry extends AbstractChangeIndexStatusEntry implements Fireable { | |||
public static final DropIndexEntrySerializer SERIALIZER = new DropIndexEntrySerializer(); | |||
public static final CatalogObjectSerializer<DropIndexEntry> SERIALIZER = new DropIndexEntrySerializer(); | |||
|
|||
private final int tableId; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like tableId
is not used anywhere but tests. Let's remove it as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
@@ -44,17 +44,17 @@ public class NewIndexEntry implements UpdateEntry, Fireable { | |||
|
|||
private final CatalogIndexDescriptor descriptor; | |||
|
|||
private final String schemaName; | |||
private final int schemaId; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we need schemaId
? It can be derived from table, I believe
remove remaining schema id.
use initial token.
# Conflicts: # modules/catalog/src/main/java/org/apache/ignite/internal/catalog/CatalogManagerImpl.java # modules/catalog/src/test/java/org/apache/ignite/internal/catalog/CatalogManagerSelfTest.java
Remove tableId.
# Conflicts: # modules/sql-engine/src/integrationTest/java/org/apache/ignite/internal/sql/engine/ItCreateTableDdlTest.java
check style.
check style.
https://issues.apache.org/jira/browse/IGNITE-19082
Thank you for submitting the pull request.
To streamline the review process of the patch and ensure better code quality
we ask both an author and a reviewer to verify the following:
The Review Checklist
- There is a single JIRA ticket related to the pull request.
- The web-link to the pull request is attached to the JIRA ticket.
- The JIRA ticket has the Patch Available state.
- The description of the JIRA ticket explains WHAT was made, WHY and HOW.
- The pull request title is treated as the final commit message. The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
Notes