[jira] [Commented] (IGNITE-16434) Use @InternalId in tables configuration.
[ https://issues.apache.org/jira/browse/IGNITE-16434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17485899#comment-17485899 ] Alexander Lapin commented on IGNITE-16434: -- [~ibessonov] LGTM from my side. > Use @InternalId in tables configuration. > > > Key: IGNITE-16434 > URL: https://issues.apache.org/jira/browse/IGNITE-16434 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha4 >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 3h > Remaining Estimate: 0h > > Replace IgniteUuid with UUID in tables configuration. It is more convenient > since https://issues.apache.org/jira/browse/IGNITE-15721 is already closed. > How can it help: > * @InternalId reduces the amount of data that needs to be transfered > * it is integrated with direct proxies in configuration, reducing the amount > of requests to the metastorage when used properly -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16434) Use @InternalId in tables configuration.
[ https://issues.apache.org/jira/browse/IGNITE-16434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17485883#comment-17485883 ] Ivan Bessonov commented on IGNITE-16434: [~alapin] thank you! I replied to your comments > Use @InternalId in tables configuration. > > > Key: IGNITE-16434 > URL: https://issues.apache.org/jira/browse/IGNITE-16434 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha4 >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 2h 40m > Remaining Estimate: 0h > > Replace IgniteUuid with UUID in tables configuration. It is more convenient > since https://issues.apache.org/jira/browse/IGNITE-15721 is already closed. > How can it help: > * @InternalId reduces the amount of data that needs to be transfered > * it is integrated with direct proxies in configuration, reducing the amount > of requests to the metastorage when used properly -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16434) Use @InternalId in tables configuration.
[ https://issues.apache.org/jira/browse/IGNITE-16434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17485219#comment-17485219 ] Alexander Lapin commented on IGNITE-16434: -- [~ibessonov] Please check few minors in PR. > Use @InternalId in tables configuration. > > > Key: IGNITE-16434 > URL: https://issues.apache.org/jira/browse/IGNITE-16434 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha4 >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Replace IgniteUuid with UUID in tables configuration. It is more convenient > since https://issues.apache.org/jira/browse/IGNITE-15721 is already closed. > How can it help: > * @InternalId reduces the amount of data that needs to be transfered > * it is integrated with direct proxies in configuration, reducing the amount > of requests to the metastorage when used properly -- This message was sent by Atlassian Jira (v8.20.1#820001)
