[
https://issues.apache.org/jira/browse/IGNITE-12808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130744#comment-17130744
]
Andrey Mashenkov commented on IGNITE-12808:
-------------------------------------------
[~ivandasch], yes, I've restarted RunAll task on TC.
IgniteDynamicEnableIndexingRestoreTest checks only server nodes. Will client be
able to reconnect in same scenario?
DynamicEnableIndexingBasicSelfTest - I'm not sure it is really test anything as
grid is pre-started once, so the order of cache creation and index enabling
doesn't matters in all tests except the first one.
DynamicEnableIndexingConcurrentSelfTest - cache is started on client, then
indexing is enabled on same client. It doesn't covers case if index information
propagated to client correctly.
AFAIK client actually starts cache after first cli.cache() call only. So, we
can't be sure client correctly process schema update when no one call
cli.cache() before enabling indexing.
> Allow create tables for existing caches
> ---------------------------------------
>
> Key: IGNITE-12808
> URL: https://issues.apache.org/jira/browse/IGNITE-12808
> Project: Ignite
> Issue Type: New Feature
> Components: sql
> Reporter: Mikhail Cherkasov
> Assignee: Ivan Daschinskiy
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> If you have a big cache with a lot of data and you need to index it, right
> now you have to destroy cache and create a new one to index your data. Or
> create a new cache with a table and reload it to data to the new cache which
> definitely is time-consuming and super inconvenient.
> I believe we can allow users to create tables for existing caches.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
