Pavel Tupitsyn commented on IGNITE-1915:

Merged with master, refactored cleanup and version increment to Java approach 
with cache extension.

Discovered an issue: if entity set version data is lost (due to node failure), 
incorrect results can be returned for queries.
We can't have cache with backups to avoid duplicating possibly huge query 

Solution here is similar to IGFS approach: use two caches. One "meta" cache 
with entity set versions, and another "data" cache with actual query results.
To simplify configuration, the only user-provided parameter is "provider name". 
Cache names will be generated automatically form it. Optionally, user would be 
able to provide customized cache configs.

> .NET: Ignite as Entity Framework Second-Level Cache
> ---------------------------------------------------
>                 Key: IGNITE-1915
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1915
>             Project: Ignite
>          Issue Type: Task
>          Components: platforms
>    Affects Versions: 1.1.4
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>              Labels: .net, roadmap
>             Fix For: 1.8
> Entity Framework is #1 ORM for .NET
> We should provide easy solution to boost Entity Framework performance with 
> Ignite.
> EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in 
> one, EF6 requies more customization or a 3rd party lib like 
> https://efcache.codeplex.com/). For now, let's do EF6 only.
> This should be in a separate assembly and a separate NuGet package.

This message was sent by Atlassian JIRA

Reply via email to