[
https://issues.apache.org/jira/browse/IGNITE-7264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16305621#comment-16305621
]
ASF GitHub Bot commented on IGNITE-7264:
----------------------------------------
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/3318
IGNITE-7264: Caches with forward slash "/" in names cause problems for PDS
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7264
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3318.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 #3318
----
commit fcacf73d2db54865fa3ff1387e04dfc2fe6ca4b8
Author: Stanislav Lukyanov <stanlukyanov@...>
Date: 2017-12-28T09:26:10Z
IGNITE-7264: removed unused method
commit f796b61b8f25c32022c6a3041e46deea2002ad0a
Author: Stanislav Lukyanov <stanlukyanov@...>
Date: 2017-12-28T14:35:06Z
IGNITE-7264: added escaping of unsafe characters in persistent storage names
commit 62d7c38f4cc3c561420ae9f0289acf646011a04a
Author: Stanislav Lukyanov <stanlukyanov@...>
Date: 2017-12-28T16:13:36Z
IGNITE-7264: restored afterTest action in IgnitePdsExoticCacheNamesTest
commit f7bbcc63d91953d8188566442a36661ad4819ced
Author: Stanislav Lukyanov <stanlukyanov@...>
Date: 2017-12-28T17:42:17Z
IGNITE-7264: added handling of long cache names
----
> Caches with forward slash "/" in names cause problems for PDS
> -------------------------------------------------------------
>
> Key: IGNITE-7264
> URL: https://issues.apache.org/jira/browse/IGNITE-7264
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence
> Affects Versions: 2.3
> Reporter: Ilya Kasnacheev
> Assignee: Stanislav Lukyanov
>
> If I am to create cache with name "caches/1", there's no immediate error, but
> nodes fail when trying to rejoin topology with storage already initialized.
> I think there should be an immediate exception in case persistence is enabled
> for such case.
> Moreover, I suggest first trying to create directory, then making sure it was
> created and that dir.parent == expected parent directory. Because on Windows
> there are more restrictions on FS file names, etc...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
