You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Oleg Valuyskiy (Jira)" <ji...@apache.org> on 2024/12/11 09:32:00 UTC
[jira] [Created] (IGNITE-23946) Improve clarity of 'Cache is already indexed' exception message
Oleg Valuyskiy created IGNITE-23946:
---------------------------------------
Summary: Improve clarity of 'Cache is already indexed' exception message
Key: IGNITE-23946
URL: https://issues.apache.org/jira/browse/IGNITE-23946
Project: Ignite
Issue Type: Task
Reporter: Oleg Valuyskiy
Assignee: Oleg Valuyskiy
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.
It appears that for some users, the "Cache is already indexed" message isn't sufficiently informative since it's not entirely clear which user actions trigger this exception.
Therefore, it appears to be beneficial to revise the wording of this exception to ensure greater clarity for users.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)