[IGNITE-15382] Decouple API and implementation for Tuple.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha3
• Labels: UX ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Andrey Mashenkov
• Reporter: Andrey Mashenkov
• Created: 27/Aug/21 08:38
• Updated: 24/Sep/21 14:27
• Resolved: 24/Sep/21 14:27

Description

TupleImpl implements a public API interface Tuple and resides in ignite-api module.
Public API implementation must be hidden from a user to avoid direct usage/instantiation.

This can be achieved in next ways
1. Move TupleImpl to an internal package of the e.g. ignite-table module and use ServiceLoader for tuple factory.
This introduces implicit module dependency and a new factory interface/class.
2. Make TupleImpl package-private class.
We will not be able to create a TupleImpl object directly, but seems it is ok to use factory methods.

Let's make TupleImpl a package-private class.

Issue Links

• is a child of: IGNITE-13616 IEP-54 Live schema for tables
• requires: IGNITE-15253 Tuple API improvement.
• links to: GitHub Pull Request #301