[
https://issues.apache.org/jira/browse/IGNITE-19221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17708698#comment-17708698
]
Pavel Tupitsyn commented on IGNITE-19221:
-----------------------------------------
[~alex_pl] using address finder to disable discovery looks more like a
workaround to me.
An explicit option is better for two reasons:
* The entire feature is discoverable. E.g. as a new user, I can see it in the
autocomplete box, so I understand that client has discovery, and how to control
it.
* User code is more readable. If someone uses address finder to disable
discovery, later someone else might think "wtf, why an address finder is used
with a single address, let's fix it"
> Java thin: Add ClientConfiguration.clusterDiscoveryEnabled
> ----------------------------------------------------------
>
> Key: IGNITE-19221
> URL: https://issues.apache.org/jira/browse/IGNITE-19221
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Affects Versions: 2.14
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Fix For: 2.15
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Cluster discovery is always enabled currently, which can be undesirable in
> some use cases. Add a config property to disable discovery.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
