Hi, Dmitry!
I guess there will be no IEP specifically for the client, because it has
nothing to do with Ignite enhancing, as what IEP stands for.
From Ignite side, the purpose and potential capabilities of the thin
client, aka binary API client, is best described by this document:
https://apacheignite.readme.io/docs/binary-client-protocol
From our side, there is some basic info about our project in the
corresponding Jira task:
https://issues.apache.org/jira/browse/IGNITE-7782
This info is yet to be extended and adjusted.
For more in-depth look at our current work in progress please consult
our Sphinx documentation. It is contained in our repo in already
prebuilt form, and will be updated frequently:
https://github.com/nobitlost/ignite/tree/ignite-7782/modules/platforms/python/docs/generated
Regarding the feature set, we strive for the most complete
implementation of the protocol. However, some of its features (type IDs,
filter objects, binary type registering, and may be more) are specific
for Java typing system and thus not relevant for Python language, and
will unlikely be implemented.
Regards,
On 06/29/2018 07:53 AM, Dmitriy Setrakyan wrote:
Is there an IEP for it where the community can read about the feature set
that will be supported by the Python client?
D.
