[
https://issues.apache.org/jira/browse/IGNITE-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048373#comment-16048373
]
Sergey Stronchinskiy commented on IGNITE-4636:
----------------------------------------------
[~ptupitsyn],
Please take a look, I've committed few style fixes and launched build jobs
again.
Current implementation supports joining with collections of "simple" types
(which can be directly mapped to SQL types). The {{Join}} clause with local
collections can be used in compiled query when the collection is constant (not
passed as a parameter). When IGNITE-5404 will be fixed, local join should
support collections passed as parameter to compiled query(with one limitation
compared to other cases - subqueries will not be supported). Also local joins
support left outer join via {{DefaultIfEmpty}} operator.
> .NET: Support local collection joins in LINQ
> --------------------------------------------
>
> Key: IGNITE-4636
> URL: https://issues.apache.org/jira/browse/IGNITE-4636
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Affects Versions: 1.8
> Reporter: Pavel Tupitsyn
> Assignee: Sergey Stronchinskiy
> Labels: .NET, LINQ
> Fix For: 2.1
>
>
> LINQ {{IN}} clause is implemented in IGNITE-4425 and maps from
> {{ICollection.Contains}}.
> However, {{IN}} has some limitations in Ignite, and better alternative is
> temporary table join:
> https://apacheignite.readme.io/docs/sql-performance-and-debugging#sql-performance-and-usability-considerations
> Example SQL:
> {code}
> new SqlFieldsQuery("select p.name from Person p join table(id bigint = ?) i
> on p.OrgId = i.id", new object[] { new object[] {1,3}})
> {code}
> Add support in LINQ like this:
> {code}persons.AsCacheQueryable().Join(new[] {1, 3}, p => p.Value.OrgId, x =>
> x, (p, x) => p);{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
