[
https://issues.apache.org/jira/browse/IGNITE-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-4462:
---------------------------------
Description:
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.
was:
When the {{HadoopIgfsWrapper}} creates IGFS delegate with in-proc mode 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.
Also the Ignite client mode must supports several connection to the different
clusters. The name a client-note to connect to the target grid must be
generated programmatically by the {{HadoopIgfsWrapper}}
> 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)
