ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache
Date Thu, 11 Aug 2016 14:58:20 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402473#comment-15402473
] 

Pavel Tupitsyn edited comment on IGNITE-1915 at 8/11/16 2:58 PM:
-----------------------------------------------------------------

1) We use GetOrCreateCache deliberately. If there is a user-defined cache with specified name,
it will be picked up. User has full control over the cache configuration.
2) Having multiple databases is very unlikely, and user should understand the consequences
of using the same cache for them. Single DB is the most frequent use case, and we want to
reduce configuration efforts for it.
3) Changed to long
4) Changed to pessimistic. Optimistic with retry can cause incorrect update order. As for
isolation, RepeatableRead fits us well. We don't need Serializable (don't care about new rows),
and ReadCommitted is too weak.
5) Fixed
6,7) Can you elaborate on your idea? How can EntryProcessor atomically update two mappings
(SQL->Result and EntitySet->SQL[])?
8) Key value in an SQL query. At the very minimum it is "SELECT X FROM Y", which is never
a valid entity set name.


was (Author: ptupitsyn):
1) We use GetOrCreateCache deliberately. If there is a user-defined cache with specified name,
it will be picked up. User has full control over the cache configuration.
2) Having multiple databases is very unlikely, and user should understand the consequences
of using the same cache for them. Single DB is the most frequent use case, and we want to
reduce configuration efforts for it.
3) Changed to long
4) Changed to pessimistic. Optimistic with retry can cause incorrect update order. As for
isolation, RepeatableRead fits us well. We don't need Serializable (don't care about new rows),
and ReadCommitted is too weak.
5) Fixed
6,7) Can you elaborate on your idea? How can EntryProcessor atomically update two mappings
(SQL->Result and EntitySet->SQL[])?

> .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
(v6.3.4#6332)

Mime
View raw message