[ignite-3] branch ignite-19497 updated (cee110b072 -> 3b5e57a462)

[am...@apache.org]

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 cee110b072 Fix tests.
 discard e71574260c Replace IgniteIndex with IgniteSchemaIndex. Drop CatalogColumnDescriptor.
    omit 48c0c070f0 Add a hack to get table by name/correct id.
    omit 338d8f6c8a Fix table-by-name resolution.
    omit 27d351666e Fix column mapping.
    omit e5b36f3412 Replace old IgniteSchema with new IgniteCatalogSchema.
    omit ab5191ee8c Styles.
    omit a271616e10 Replace IgniteIndex with IgniteSchemaIndex
    omit 24102d7d34 Replace IgniteTableImpl with IgniteCatalogImpl.
    omit 994ded152f Fix HashFunctionFactoryImpl to use specific schema version. Fix SqlSchemaManager interface. Drop unused code.
    omit d8de394795 Use schema versions for queries. * Use actual schema for query in TX. * Pass schema version to remote fragment. * Wait for catalog schema ready on the remote side.
     add 0b7b537410 Use schema versions for queries. * Use actual schema for query in TX. * Pass schema version to remote fragment. * Wait for catalog schema ready on the remote side. * Planner cache use catalog version.
     add c387b5bc1d Fix HashFunctionFactoryImpl to use specific schema version. Fix SqlSchemaManager interface. Drop unused code.
     add 9a82b7fb7b Replace IgniteTableImpl with IgniteCatalogImpl.
     add d108b5036e Replace IgniteIndex with IgniteSchemaIndex
     add 16644d1ac3 Styles.
     add 41e482e069 Replace old IgniteSchema with new IgniteCatalogSchema.
     add e9a36c0010 Fix column mapping.
     add c8529aeea3 Fix table-by-name resolution.
     add 4a692d5fd5 Add a hack to get table by name/correct id.
     add d66e1e2759 Replace IgniteIndex with IgniteSchemaIndex. Drop CatalogColumnDescriptor.
     add 3b5e57a462 Fix tests.

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   (cee110b072)
            \
             N -- N -- N   refs/heads/ignite-19497 (3b5e57a462)

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/prepare/CacheKey.java      | 22 ++++++++++------------
 .../sql/engine/prepare/PrepareServiceImpl.java     |  4 +++-
 2 files changed, 13 insertions(+), 13 deletions(-)