Hi Pavel,
Thank you a lot for the response.
Best Regards,
Roman
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Roman,
Thanks for the reproducer. I needed that to better understand the issue.
And, I'm afraid, we won't have support for this kind of queries anytime
soon.
Even Entity Framework does not support this kind of grouping.
On Fri, Jun 22, 2018 at 1:18 PM Roman Guseinov wrote:
> Hi Pavel,
>
> Than
Hi Pavel,
Thank you for the response. Yes, your LINQ example can be a workaround. And
SQL query can be as well.
The small project with LINQ query example can be found here
https://github.com/gromtech/ignite-linq-issue-reproducer
I just want to know if there any plans to support such LINQ querie
Roman,
Can you try rephrasing the LINQ query as the SQL goes?
var q1 = queryable.GroupBy(o => o.Value.ContractId).Select(g => new
{ContractId = g.Key, MaxVer = g.Select(x=>x.Value.Version).Max()});
var q2 = q1.Select( ...)
At least this first part works for me. I did not try further.
Ideally pl
Hi Pavel,
Thank you for the response. Regarding support every LINQ expression, I agree
with you. It's not possible.
Let me show an example. The following LINQ query:
/var result = queryable.GroupBy(e => e.Value.ContractId).Select(group => new
{
ContractId = group.Key,
Id = group.OrderByD
Hi Roman,
It is even hard to say what kind of SQL should we produce for such a query.
The general idea of Ignite LINQ provider is:
Do not try to support every LINQ expression (which is not possible, because
LINQ and SQL are quite different);
but try to make most SQL scenarios possible to express
