Thanks for all who participated in review.
Cpp transactions functionality already in master.
Appropriate wiki page [1] was updated.
[1] https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features
>
>
>Great, I'll take a look.
>
>Best Regards,
>Igor
>
>
>On Mon, Aug 24, 2020 at
Hello, Igniters.
Alexey, please, include one more Python thin client fix [1] into the 2.9 release
It fixes kinda major issue - "Python client returns fields in wrong order since
the 2 row when fields_count>10"
[1] https://issues.apache.org/jira/browse/IGNITE-12809
[2]
>
> However, could you please elaborate on the relation between Ignite and ORM?
> Is there a use case for Hibernate running on top of Ignite (I haven't seen
> one so far)? If so, what is missing exactly on the Ignite side to support
> this? In my understanding, all you need is SQL API which we
Hi Val,
Thank you for raising a discussion about this significant proposal!
The subject looks very significant and can greatly affect product
spirit and user experience.
While I generally think that schema-first is a good idea, I would love
to see a thorough approaches comparison section. As we
Sergey,
Actually, I missed the point that the discussed mode affects a single
node but not a whole cluster. Perhaps I mixed terms "mode" and
"state".
My next thoughts about maintenance routines are about special
utilities. As far as I remember MySQL provides a bunch of scripts for
various
Ivan,
Thank you for reminding me about the dynamic schema. I've updated the IEP
draft with more details on the approach, hopefully now it's more clear. I
think we will be able to take the best from both fixed-schema and
schemaless approaches.
вт, 1 сент. 2020 г. в 14:31, Ivan Pavlukhin :
> Hi
Alexey,
Thanks for adding more details to the IEP. I have a question regarding the
following:
*When an object is inserted into a table, we attempt to 'fit' object fields
to the schema columns. If a Java object has some extra fields which are not
present in the current schema, the schema is
