Igniters, I'd like to discuss the future of this functionality in Apache
Ignite
Today this functionality seems to be unusable
1. It is limited (especially redis)
2. It doesn't support HA (redis sentinel or redis cluster)
3. Nobody maintains it and even nobody fixes bugs. (i.e. [1] is not merged
fo
Dear Ignite Community!
I suggest starting Apache Ignite 2.13 release activities.
There is a plan to merge the new Calcite SQL engine. [1] I think that
2.13 is a good candidate for it.
Moreover, we've accumulated a hundred resolved [2] issues with new
features and bug fixes which are waiting for
Patch has been reviewed by Andrey Mashenkov and Max Muzafarov and approved.
If nobody disagrees, I will merge it in a few hours.
пн, 7 февр. 2022 г. в 12:21, Ivan Daschinsky :
> Patch is ready for review
>
> пт, 4 февр. 2022 г. в 14:45, Ivan Daschinsky :
>
>> https://issues.apache.org/jira/browse
asfgit closed pull request #4:
URL: https://github.com/apache/ignite-nodejs-thin-client/pull/4
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev
isapego commented on a change in pull request #4:
URL:
https://github.com/apache/ignite-nodejs-thin-client/pull/4#discussion_r801366727
##
File path: api_spec/index.md
##
@@ -0,0 +1,9 @@
+# Node.js Client for Apache Ignite
+
+This thin client allows your Node.js applications t
Looks like it useful remark, thanks !
Hi All
IIUC, the current implementation may be problematic.
Ignite disabled subquery rewriting in this PR(
https://github.com/apache/ignite/pull/9251), and I think the correct
process would be sqlnode => relnode => convert RexSubQuery to Correlate
=>
d
