You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/08/15 16:29:00 UTC
[jira] [Commented] (IGNITE-9279) Support custom default SQL schema
name.
[ https://issues.apache.org/jira/browse/IGNITE-9279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581312#comment-16581312 ]
ASF GitHub Bot commented on IGNITE-9279:
----------------------------------------
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4550
IGNITE-9279: support custom default SQL schema.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9279
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4550.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4550
----
commit 87be7921f4b99b5ca36bd2ceba52c30554350f99
Author: Andrey V. Mashenkov <an...@...>
Date: 2018-08-15T16:28:10Z
ignite-9279: support custom default SQL schema.
----
> Support custom default SQL schema name.
> ---------------------------------------
>
> Key: IGNITE-9279
> URL: https://issues.apache.org/jira/browse/IGNITE-9279
> Project: Ignite
> Issue Type: Wish
> Components: sql
> Reporter: Andrew Mashenkov
> Priority: Major
>
> Default SQL schema is PUBLIC and there is no way to customize.
> This may be useful when dynamic schema creation will be implemented.
> Let's make default schema name configurable via node properties and then add it to ignite configuration.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)