[jira] [Commented] (IGNITE-4462) Remove grid name from HadoopIgfsEndpoint
[
https://issues.apache.org/jira/browse/IGNITE-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15772914#comment-15772914
]
Taras Ledkov commented on IGNITE-4462:
--
Fixed
> Remove grid name from HadoopIgfsEndpoint
>
>
> Key: IGNITE-4462
> URL: https://issues.apache.org/jira/browse/IGNITE-4462
> Project: Ignite
> Issue Type: Task
> Components: IGFS
>Affects Versions: 1.8
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> When the {{HadoopIgfsWrapper}} creates IGFS delegate with it must not find
> the ignite instance by the the name.
> The collection of available ignite instances must be scanned and the first
> instance with the target file system will be used If the several nodes are
> available on the specified host / localhost / current VM process.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4462) Remove grid name from HadoopIgfsEndpoint
[
https://issues.apache.org/jira/browse/IGNITE-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15772864#comment-15772864
]
Taras Ledkov commented on IGNITE-4462:
--
Logger instance isn't available at the {{HadoopIgfsEndpoint}} constructor.
So, I propose parse the old formatted connection string quiet (without any
warnings).
> Remove grid name from HadoopIgfsEndpoint
>
>
> Key: IGNITE-4462
> URL: https://issues.apache.org/jira/browse/IGNITE-4462
> Project: Ignite
> Issue Type: Task
> Components: IGFS
>Affects Versions: 1.8
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> When the {{HadoopIgfsWrapper}} creates IGFS delegate with it must not find
> the ignite instance by the the name.
> The collection of available ignite instances must be scanned and the first
> instance with the target file system will be used If the several nodes are
> available on the specified host / localhost / current VM process.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4462) Remove grid name from HadoopIgfsEndpoint
[
https://issues.apache.org/jira/browse/IGNITE-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764655#comment-15764655
]
ASF GitHub Bot commented on IGNITE-4462:
GitHub user taras-ledkov opened a pull request:
https://github.com/apache/ignite/pull/1368
IGNITE-4462: Remove grid name from HadoopIgfsEndpoint
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4462
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1368.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 #1368
commit 128e4d737b8a58585d3703917c7d1fc186796821
Author: tledkov-gridgain
Date: 2016-12-20T16:52:49Z
IGNITE-4462: Remove grid name from HadoopIgfsEndpoint
> Remove grid name from HadoopIgfsEndpoint
>
>
> Key: IGNITE-4462
> URL: https://issues.apache.org/jira/browse/IGNITE-4462
> Project: Ignite
> Issue Type: Task
> Components: IGFS
>Affects Versions: 1.8
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> When the {{HadoopIgfsWrapper}} creates IGFS delegate with it must not find
> the ignite instance by the the name.
> The collection of available ignite instances must be scanned and the first
> instance with the target file system will be used If the several nodes are
> available on the specified host / localhost / current VM process.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
