Re: Issues if -Djava.net.preferIPv4Stack=true is not set

On Wed, Sep 27, 2017 at 5:08 AM, Yakov Zhdanov wrote: > hmm.. Dmitry, your suggestion may work if Ignite is started before any of > network layer class is loaded/called. E.g. this will not work if Ignite is > started inside application or web server. > Sure, let's do it

Re: Persistence per memory policy configuration

Vote for 1. — Denis > On Sep 26, 2017, at 11:23 PM, Vladimir Ozerov wrote: > > Folks, > > Let me summarize current naming ideas one more time: > > 1) [StorageConfiguration - StorageRegionConfiguration] > 2) [DurableMemoryConfiguration - DataRegionConfiguration] > 3)

[jira] [Created] (IGNITE-6518) Smarter analysis of INSERT and MERGE statements at parsing stage

Alexander Paschenko created IGNITE-6518: --- Summary: Smarter analysis of INSERT and MERGE statements at parsing stage Key: IGNITE-6518 URL: https://issues.apache.org/jira/browse/IGNITE-6518

[jira] [Created] (IGNITE-6517) .NET: DataStreamer DefaultPerNodeBufferSize, DefaultParallelOpsMultiplier

Pavel Tupitsyn created IGNITE-6517: -- Summary: .NET: DataStreamer DefaultPerNodeBufferSize, DefaultParallelOpsMultiplier Key: IGNITE-6517 URL: https://issues.apache.org/jira/browse/IGNITE-6517

[jira] [Created] (IGNITE-6516) .NET: PersistentStoreConfiguration.WriteThrottlingEnabled

Pavel Tupitsyn created IGNITE-6516: -- Summary: .NET: PersistentStoreConfiguration.WriteThrottlingEnabled Key: IGNITE-6516 URL: https://issues.apache.org/jira/browse/IGNITE-6516 Project: Ignite

[jira] [Created] (IGNITE-6515) .NET: Enable persistence on per-cache basis

Pavel Tupitsyn created IGNITE-6515: -- Summary: .NET: Enable persistence on per-cache basis Key: IGNITE-6515 URL: https://issues.apache.org/jira/browse/IGNITE-6515 Project: Ignite Issue Type:

[GitHub] ignite pull request #2754: IGNITE-5615 .NET: IgniteConfiguration.LocalEventL...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2754 ---

[GitHub] ignite pull request #2765: GG-12821 IGNITE-4642: Added "enforceJoinOrder" an...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/2765 GG-12821 IGNITE-4642: Added "enforceJoinOrder" and "lazy" flags to thick JDBC driver. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2764: GG-12826 Backport fixes for NPE in GridDhtPartiti...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/2764 GG-12826 Backport fixes for NPE in GridDhtPartitionDemander. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-6514) Hide QueryEntity.notNullFields from public API

Alexey Goncharuk created IGNITE-6514: Summary: Hide QueryEntity.notNullFields from public API Key: IGNITE-6514 URL: https://issues.apache.org/jira/browse/IGNITE-6514 Project: Ignite

[jira] [Created] (IGNITE-6513) Add ability manage version for WAL serializer via system properties

Dmitriy Govorukhin created IGNITE-6513: -- Summary: Add ability manage version for WAL serializer via system properties Key: IGNITE-6513 URL: https://issues.apache.org/jira/browse/IGNITE-6513

Re: Per-entry overhead - some questions

Yes, Basically, it is a pair of backing arrays of key and value as BinaryObjects, associated GridCacheVersion and expireTime (I may have forgotten something, but this something should not be too large). You can take a closer look at WriteRowHandler class which runs the row store to a data page to

Re: Per-entry overhead - some questions

Thanks Alexey, understood. What is the format of the object that is stored off-heap, is it a BinaryObjectOffheapImpl (or a parent class/interface) or something else? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-6512) Need a possibility to start caches without discarding their 'restarting' state

Eduard Shangareev created IGNITE-6512: - Summary: Need a possibility to start caches without discarding their 'restarting' state Key: IGNITE-6512 URL: https://issues.apache.org/jira/browse/IGNITE-6512

[GitHub] ignite pull request #2763: IGNITE-5713

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/2763 IGNITE-5713 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5713 Alternatively you can review and apply these

[jira] [Created] (IGNITE-6511) ODBC: SQLGetDiagRec doesn't follow specification when buffer size is too small

Sergey Kalashnikov created IGNITE-6511: -- Summary: ODBC: SQLGetDiagRec doesn't follow specification when buffer size is too small Key: IGNITE-6511 URL: https://issues.apache.org/jira/browse/IGNITE-6511

Re: Issues if -Djava.net.preferIPv4Stack=true is not set

hmm.. Dmitry, your suggestion may work if Ignite is started before any of network layer class is loaded/called. E.g. this will not work if Ignite is started inside application or web server. --Yakov

Re: Per-entry overhead - some questions

Hello Mike, With the new Ignite 2.0 architecture, GridCacheMapEntry does not add any overhead because the data is stored off-heap (unless you have on-heap cache enabled) and the GridCacheMapEntry is created only temporarily. Anyways, answering your questions: 1) The reference to GridCacheContext

[jira] [Created] (IGNITE-6510) SQL: document CACHE_NAME, KEY_TYPE and VALUE_TABLE options for CREATE TABLE

Vladimir Ozerov created IGNITE-6510: --- Summary: SQL: document CACHE_NAME, KEY_TYPE and VALUE_TABLE options for CREATE TABLE Key: IGNITE-6510 URL: https://issues.apache.org/jira/browse/IGNITE-6510

[GitHub] ignite pull request #2740: IGNITE-6242

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2740 ---

[jira] [Created] (IGNITE-6509) SQL: Add NOT NULL support to QueryEntity API

Vladimir Ozerov created IGNITE-6509: --- Summary: SQL: Add NOT NULL support to QueryEntity API Key: IGNITE-6509 URL: https://issues.apache.org/jira/browse/IGNITE-6509 Project: Ignite Issue

Re: Persistence per memory policy configuration

I like Vladimir's suggestion - StorageConfiguration - StorageRegionConfiguration --Yakov

[GitHub] ignite pull request #2753: ignite-5714 updateExplicitVersion for detached en...

Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/2753 ---

[GitHub] ignite pull request #2526: IGNITE-6184 Add checkClusterState() call to destr...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2526 ---

[GitHub] ignite pull request #2739: IGNITE-6360: NPE occurs if object with null index...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2739 ---

[GitHub] ignite pull request #2760: IGNITE-6331

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/2760 ---

[GitHub] ignite pull request #2755: IGNITE-5730 .NET: Fix ignite.jni.dll temp dir rac...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2755 ---

[jira] [Created] (IGNITE-6508) Web console: chart has no labels on X axis in some cases

Pavel Konstantinov created IGNITE-6508: -- Summary: Web console: chart has no labels on X axis in some cases Key: IGNITE-6508 URL: https://issues.apache.org/jira/browse/IGNITE-6508 Project: Ignite

[GitHub] ignite pull request #2762: gnite-gg-pitr-2.1.5 merge to ignite-PITR (master)

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/2762 gnite-gg-pitr-2.1.5 merge to ignite-PITR (master) You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-PITR

[GitHub] ignite pull request #2756: ignite-gg-pitr-2.1.5 merge to PITR (master)

Github user DmitriyGovorukhin closed the pull request at: https://github.com/apache/ignite/pull/2756 ---

[GitHub] ignite pull request #2761: Ignite 2.2

GitHub user taoyuyu opened a pull request: https://github.com/apache/ignite/pull/2761 Ignite 2.2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/ignite ignite-2.2 Alternatively you can review and apply these changes as

[GitHub] ignite pull request #2733: IGNITE-6468: Added tests. Fixed some issues

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2733 ---

[GitHub] ignite pull request #2633: IGNITE-6331

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/2633 ---

[GitHub] ignite pull request #2760: IGNITE-6331

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/2760 IGNITE-6331 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6331-more Alternatively you can review and apply

Re: Persistence per memory policy configuration

Folks, Let me summarize current naming ideas one more time: 1) [StorageConfiguration - StorageRegionConfiguration] 2) [DurableMemoryConfiguration - DataRegionConfiguration] 3) [DurableMemoryConfiguration - DurableMemoryRegionConfiguration] - out of question, as "durable memory region" is too