[jira] [Commented] (IGNITE-23322) Inconsistent method visibility in ClientSchema

["Pavel Tupitsyn (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-23322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887873#comment-17887873 ] 

Pavel Tupitsyn commented on IGNITE-23322:
-----------------------------------------

Merged to main: [3d08df33902b4d705bbcfc8512ee94a1b1007009|https://github.com/apache/ignite-3/commit/3d08df33902b4d705bbcfc8512ee94a1b1007009]

> Inconsistent method visibility in ClientSchema
> ----------------------------------------------
>
>                 Key: IGNITE-23322
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23322
>             Project: Ignite
>          Issue Type: Improvement
>          Components: clients
>    Affects Versions: 3.0.0-beta1
>            Reporter: Tiago Marques Godinho
>            Assignee: Tiago Marques Godinho
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The `org.apache.ignite.internal.client.table.ClientSchema` class has some inconsistencies regarding method visibility that may hinder it's future usage:
> For instance:
> * ClientSchema#column is public, but ClientSchema#columnSafe is package-private.
> * ClientSchema#getMarshaller(Mapper) is public, but ClientSchema#getMarshaller(Mapper, Tuple) is package private; #getMarshaller(Mapper, TuplePart, allowUnmappedFields) is also package-private but we might want to hide the logic of allowing unmapped fields.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)