Skip to content

Rename SchemaEngine to LocalSchemaProcessor and Rename SchemaRegionManager to SchemaEngine#5359

Merged
qiaojialin merged 2 commits intoapache:masterfrom
MarcosZyk:local_schema_processor
Mar 28, 2022
Merged

Rename SchemaEngine to LocalSchemaProcessor and Rename SchemaRegionManager to SchemaEngine#5359
qiaojialin merged 2 commits intoapache:masterfrom
MarcosZyk:local_schema_processor

Conversation

@MarcosZyk
Copy link
Contributor

Description

To stick with the design and terms of new cluster, the old SchemaEngine has been renamed to LocalSchemaProcessor to only act as a schema query proxy in standalone mode, and the SchemaRegionManager has been renamed to SchemaEngine to manage multi schemaRegion of the DataNode

@qiaojialin qiaojialin merged commit 5404730 into apache:master Mar 28, 2022
xinzhongtianxia pushed a commit to xinzhongtianxia/iotdb that referenced this pull request Apr 5, 2022
…er_meta

* remotes/upstream/master:
  Rename SchemaEngine to LocalSchemaProcessor and Rename SchemaRegionManager to SchemaEngine (apache#5359)
  Add SchemaRegion Interfaces to SchemaEngine (apache#5349)
  [IOTDB-2803] adapt metadata write operation to plannode (apache#5344)
  [IOTDB-2679] Support logical operators in select clauses (apache#5273)
  [IOTDB-2671][metrics] Improve the implementation of iotdbReporter (apache#5338)

# Conflicts:
#	server/src/main/java/org/apache/iotdb/db/mpp/sql/planner/LogicalPlanner.java
#	server/src/test/java/org/apache/iotdb/db/mpp/sql/plan/LogicalPlannerTest.java
@MarcosZyk MarcosZyk deleted the local_schema_processor branch April 22, 2022 07:17
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