[
https://issues.apache.org/jira/browse/IGNITE-20409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Gagarkin updated IGNITE-20409:
-----------------------------------
Description:
In the current implementation, the method {{org.apache.ignite.Ignition#init}}
accepts an instance of {{{}org.apache.ignite.InitParameters{}}}. Within this
parameter object, there's a field called {{{}destinationNodeName{}}}. After
reviewing the API consistency and internal usage, it appears that the current
structure might be over-complicated and inconsistent with other methods of the
{{Ignition}} class.Proposed Changes: # Refactor the
{{org.apache.ignite.Ignition#init}} method to accept {{destinationNodeName}} as
a direct parameter rather than as part of the {{InitParameters}} object.
# Update the {{InitParameters}} class to remove the {{destinationNodeName}}
field.
# Update tests which are affected by these changes.
Rationale:
* Enhances API clarity by reducing the complexity of method parameters.
* Makes the method signature more consistent with other methods in the
{{Ignition}} class.
* Provides flexibility for internal usage of the {{InitParameters}} without
the node name.
was:
In the current implementation, the method {{org.apache.ignite.Ignition#init}}
accepts an instance of {{{}org.apache.ignite.InitParameters{}}}. Within this
parameter object, there's a field called {{{}destinationNodeName{}}}. After
reviewing the API consistency and internal usage, it appears that the current
structure might be over-complicated and inconsistent with other methods of the
{{Ignition}} class.Proposed Changes: # Refactor the
{{org.apache.ignite.Ignition#init}} method to accept {{destinationNodeName}} as
a direct parameter rather than as part of the {{InitParameters}} object.
# Update the {{InitParameters}} class to remove the {{destinationNodeName}}
field.
# Update tests which are affected by these changes.
Rationale: * Enhances API clarity by reducing the complexity of method
parameters.
* Makes the method signature more consistent with other methods in the
{{Ignition}} class.
* Provides flexibility for internal usage of the {{InitParameters}} without
the node name.
> Refactor org.apache.ignite.Ignition#init
> ----------------------------------------
>
> Key: IGNITE-20409
> URL: https://issues.apache.org/jira/browse/IGNITE-20409
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Gagarkin
> Assignee: Ivan Gagarkin
> Priority: Major
> Labels: ignite-3
>
> In the current implementation, the method {{org.apache.ignite.Ignition#init}}
> accepts an instance of {{{}org.apache.ignite.InitParameters{}}}. Within this
> parameter object, there's a field called {{{}destinationNodeName{}}}. After
> reviewing the API consistency and internal usage, it appears that the current
> structure might be over-complicated and inconsistent with other methods of
> the {{Ignition}} class.Proposed Changes: # Refactor the
> {{org.apache.ignite.Ignition#init}} method to accept {{destinationNodeName}}
> as a direct parameter rather than as part of the {{InitParameters}} object.
> # Update the {{InitParameters}} class to remove the {{destinationNodeName}}
> field.
> # Update tests which are affected by these changes.
> Rationale:
> * Enhances API clarity by reducing the complexity of method parameters.
> * Makes the method signature more consistent with other methods in the
> {{Ignition}} class.
> * Provides flexibility for internal usage of the {{InitParameters}} without
> the node name.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
