[
https://issues.apache.org/jira/browse/IGNITE-26755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18032769#comment-18032769
]
Ignite TC Bot commented on IGNITE-26755:
----------------------------------------
{panel:title=Branch: [pull/12453/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/12453/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8665526&buildTypeId=IgniteTests24Java8_RunAll]
> Prohibit to set schema for cache without query entities or allow to create
> tables on such caches
> ------------------------------------------------------------------------------------------------
>
> Key: IGNITE-26755
> URL: https://issues.apache.org/jira/browse/IGNITE-26755
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: ise
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When a user sets an SQL schema for a cache and then attempts to execute a
> "CREATE TABLE" query, the "Cache is already indexed" exception is thrown.
> This happens because using the setSqlSchema method marks the cache as
> supporting SQL. However, "CREATE TABLE" queries should only be executed on
> caches without this marking.
> But cache if we don't have query entities configured cache cannot be
> considered as indexed.
> To avoid such a problem we should prohibit setting schema without query
> entities or allow "CREATE TABLE" on caches with provided schema, but without
> query entities (perhaps with check that schema of created table is the same
> as cache schema).
> Reporducer can be found in IGNITE-23946
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
