IGNITE-4534: Implement offheap eviction policies based on page memory #1758
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/pagemem/Page.java # modules/core/src/main/java/org/apache/ignite/internal/pagemem/impl/PageNoStoreImpl.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/CacheOffheapEvictionManager.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/database/CacheDataRowAdapter.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/database/freelist/FreeListImpl.java
…aster # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/database/IgniteCacheDatabaseSharedManager.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/database/MemoryPolicy.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/database/freelist/FreeListImpl.java # modules/core/src/test/java/org/apache/ignite/internal/processors/database/FreeListImplSelfTest.java
…nto ignite-4534-from-3477-master
…ster' into ignite-4534-from-3477-master
agoncharuk
pushed a commit
to gridgain/apache-ignite
that referenced
this pull request
Feb 9, 2021
…multiple Ignite instances on same JVM (apache#1758) Support multiple Ignite instances on same JVM (@RepositoryConfig). Support query tuning parameters in @query annotation Support projections Support Page and Stream responses Support Sql Fields Query resultset transformation into the domain entity Support named parameters (:myParam) into SQL queries, declared using @param("myParam") Support advanced parameter binding and SpEL expressions into SQL queries: Template variables: #entityName - the simple class name of the domain entity Method parameter expressions: Parameters are exposed for indexed access ([0] is the first query method's param) or via the name declared using @param. The actual SpEL expression binding is triggered by ?#. Example: ?#{[0] or ?#{#myParamName} Advanced SpEL expressions: While advanced parameter binding is a very useful feature, the real power of SpEL stems from the fact, that the expressions can refer to framework abstractions or other application components through SpEL EvaluationContext extension model. Support SpEL expressions into Text queries (TextQuery). Signed-off-by: Ilya Kasnacheev <ilya.kasnacheev@gmail.com> Co-authored-by: Manuel Núñez <maxnu00@hotmail.com> (cherry picked from commit 9e99074)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Postreview.