[
https://issues.apache.org/jira/browse/IGNITE-23368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-23368:
--------------------------------------
Description:
* We should get rid of `instance of LazyServiceConfiguration` usages. It is
always the extended configuration with normal deployment, with the public API.
No need to check/cast.
* The {{ServiceConfiguration}} class should not participate in serialization.
Or the extended configuration should be `Externalizable` for example.
`LazyServiceConfiguration` should not have the duplicates of the base
`ServiceConfiguration`s `IgnitePredicate<ClusterNode> nodeFilter`,
`ServiceCallInterceptor[] interceptors` and probably `Service svc`.
* Revisit #toString method. It might give more info like `serviceName`,
`nodeFilterClass`, `totalCnt`, `perNodeCnt`, etc.
* Is the name "lazy" appropriate for this class? Maybe like
`BinaryServiceConfiguration`, or `SerializationServiceConfiguration`, or
`ExtendedServiceConfiguration`.
was:
* We should get rid of `instance of LazyServiceConfiguration` usages. It is
always the extended configuration with normal deployment, with the public API.
No need to check/cast.
* The {{ServiceConfiguration}} class should not participate in serialization.
Or the extended configuration should be `Externalizable` for example.
`LazyServiceConfiguration` should not have the duplicates of the base
`ServiceConfiguration`s `IgnitePredicate<ClusterNode> nodeFilter`,
`ServiceCallInterceptor[] interceptors` and probably `Service svc`.
* Revisit #toString method. It might give more info like `serviceName`,
`nodeFilterClass`, `totalCnt`, `perNodeCnt`, etc.
* Is the name "lazy" appropriate for this class? Maybe like
`BinaryServiceConfiguration` or `SerializationServiceConfiguration`.
> Refactor processing of LazyServiceConfiguration
> -----------------------------------------------
>
> Key: IGNITE-23368
> URL: https://issues.apache.org/jira/browse/IGNITE-23368
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.14
> Reporter: Nikita Amelchev
> Priority: Minor
> Labels: ise
>
> * We should get rid of `instance of LazyServiceConfiguration` usages. It is
> always the extended configuration with normal deployment, with the public
> API. No need to check/cast.
> * The {{ServiceConfiguration}} class should not participate in serialization.
> Or the extended configuration should be `Externalizable` for example.
> `LazyServiceConfiguration` should not have the duplicates of the base
> `ServiceConfiguration`s `IgnitePredicate<ClusterNode> nodeFilter`,
> `ServiceCallInterceptor[] interceptors` and probably `Service svc`.
> * Revisit #toString method. It might give more info like `serviceName`,
> `nodeFilterClass`, `totalCnt`, `perNodeCnt`, etc.
> * Is the name "lazy" appropriate for this class? Maybe like
> `BinaryServiceConfiguration`, or `SerializationServiceConfiguration`, or
> `ExtendedServiceConfiguration`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
