[
https://issues.apache.org/jira/browse/IGNITE-20098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-20098:
-----------------------------------------
Description:
The following exceptions classes were moved to the `core` module due to
CatalogService feature:
- DistributionZoneNotFoundException
- DistributionZoneBindTableException
- DistributionZoneAlreadyExistsException
It seems to me, that this is not the correct way to handle dependencies between
`catalog` and `distribution zone` modules. All exceptions should be moved to
the one place. IMHO, it should be the `distribution zone` module.
was:
The following exceptions classes were moved to the `core` module due to
CatalogService feature:
- DistributionZoneNotFoundException
- DistributionZoneBindTableException
- DistributionZoneAlreadyExistsException
It seems to me, that this is not correct way to handle dependencies between
`catalog` and `distribution zone` modules. All exceptions should be
> Move exception classes related to distribution zones to an appropriate
> package/module
> -------------------------------------------------------------------------------------
>
> Key: IGNITE-20098
> URL: https://issues.apache.org/jira/browse/IGNITE-20098
> Project: Ignite
> Issue Type: Bug
> Reporter: Vyacheslav Koptilin
> Priority: Major
> Labels: ignite-3
>
> The following exceptions classes were moved to the `core` module due to
> CatalogService feature:
> - DistributionZoneNotFoundException
> - DistributionZoneBindTableException
> - DistributionZoneAlreadyExistsException
> It seems to me, that this is not the correct way to handle dependencies
> between `catalog` and `distribution zone` modules. All exceptions should be
> moved to the one place. IMHO, it should be the `distribution zone` module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
