This is an automated email from the ASF dual-hosted git repository.
amashenkov pushed a change to branch ignite-19497
in repository https://gitbox.apache.org/repos/asf/ignite-3.git
discard 7e9e71671c Fix table-by-name resolution.
discard a0703dc468 Fix column mapping.
discard 3d06abd354 Replace old IgniteSchema with new IgniteCatalogSchema.
discard b93b215284 Styles.
discard 85e262d06a Replace IgniteIndex with IgniteSchemaIndex
add a271616e10 Replace IgniteIndex with IgniteSchemaIndex
add ab5191ee8c Styles.
add e5b36f3412 Replace old IgniteSchema with new IgniteCatalogSchema.
add 27d351666e Fix column mapping.
add 338d8f6c8a Fix table-by-name resolution.
add 30b83bc2db Add a hack to get table by name/correct id.
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (7e9e71671c)
\
N -- N -- N refs/heads/ignite-19497 (30b83bc2db)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../internal/sql/engine/exec/ExecutableTable.java | 6 ++++
.../engine/exec/ExecutableTableRegistryImpl.java | 21 ++++++++++++-
.../sql/engine/exec/ExecutionServiceImpl.java | 35 ++++++++++++----------
.../sql/engine/exec/ResolvedDependencies.java | 5 ++++
.../sql/engine/exec/exp/ExpressionFactoryImpl.java | 2 +-
.../sql/engine/rule/logical/ExposeIndexRule.java | 4 +--
6 files changed, 54 insertions(+), 19 deletions(-)
