You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Kozlov (JIRA)" <ji...@apache.org> on 2018/08/30 12:42:00 UTC
[jira] [Commented] (IGNITE-9345) Document custom SQL schemas
[ https://issues.apache.org/jira/browse/IGNITE-9345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597406#comment-16597406 ]
Sergey Kozlov commented on IGNITE-9345:
---------------------------------------
The example in Spring configuration:
{code:xml}
<bean id="ignite.cfg" class="org.apache.ignite.configuration.IgniteConfiguration">
...
<property name="sqlSchemas">
<list>
<value>MY_SCHEMA</value>
</list>
</property>
{code}
> Document custom SQL schemas
> ---------------------------
>
> Key: IGNITE-9345
> URL: https://issues.apache.org/jira/browse/IGNITE-9345
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
> Reporter: Vladimir Ozerov
> Priority: Major
> Fix For: 2.7
>
>
> Key highlights:
> 1) DDL operations \{{CREATE TABLE}} and \{{DROP TABLE}} are no longer tied to \{{PUBLIC}} schema. They can be executed on any schema. Need to remove this from docs (if there is such paragraph)
> 2) Added a property \{{IgniteConfiguration.sqlSchemas}} which creates local schemas with provided names.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)