Yes I could do that (that would be fun!).
Although, I don't think I totally understand how the aggregation of the
distributed results should work.
My changes probably don't account for that (I think I understand how the
OSQLFunctionDifference class was doing that, but I'm not 100% sure) and I'd
need to add some unit tests around it.
I noticed the way I was using/running with the difference() function (and
the except() function I created) it always ends up using the stateless
"inline-mode" as opposed to the stateful "aggregation-mode"... maybe other
users are mostly working with the stateful, "aggregation-mode"?
In light of this, I have a few questions:
- For the short-term, and to avoid having to upgrade OrientDB at this
moment, could I accomplish the same functionality with our current OrientDB
version through a custom Java function?
-
https://github.com/orientechnologies/orientdb/wiki/SQL-Functions#custom-functions
- If a custom function won't work, how long would it be until the
next release of OrientDB if I submitted the changes sometime this week?
- Along with that, how much of a risk is there for upgrading from our
current OrientDB version (v.1.7-rc2) to the next release?
...I'm not sure we want to risk updating OrientDB with where we are
at in our release cycle right now.
- It looks like you release a stable version of OrientDB every few
weeks?
https://github.com/orientechnologies/orientdb/releases
Thanks again for your help! I really appreciate it!
~ Andrew
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
