igniterouter.sh

Folks, Our bin folder still contains igniterouter.{sh|bat} script. Previously it was used to support indirect access from thin client to cluster. Since thin client is deprecated for a while, is there a use case when router can be used? I think it makes sense to remove these scripts for now. If

[jira] [Created] (IGNITE-5978) [Test Failed] IgnitePartitionedCountDownLatchSelfTest.testLatchMultinode1

Eduard Shangareev created IGNITE-5978: - Summary: [Test Failed] IgnitePartitionedCountDownLatchSelfTest.testLatchMultinode1 Key: IGNITE-5978 URL: https://issues.apache.org/jira/browse/IGNITE-5978

[jira] [Created] (IGNITE-5980) [Test Failed] IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover

Eduard Shangareev created IGNITE-5980: - Summary: [Test Failed] IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover Key: IGNITE-5980 URL:

[jira] [Created] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync

Eduard Shangareev created IGNITE-5979: - Summary: [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync Key: IGNITE-5979 URL: https://issues.apache.org/jira/browse/IGNITE-5979

Re: igniterouter.sh

I'm pretty sure current router will not be able to work with new client anyway, which will make even more confusing than now. I think it's better to remove these scripts in next release (unless both client and router are back in this release of course :) ). -Val On Mon, Aug 7, 2017 at 1:13 PM,

Re: igniterouter.sh

Val, Thin client is like Arnold - he'll be back ) We already working on it. I propose to delay this question a bit, until we understand that router is not needed for new thin client. пн, 7 авг. 2017 г. в 23:07, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Folks, > > Our bin folder

[jira] [Created] (IGNITE-5981) IgniteContext starts server nodes on executors

Valentin Kulichenko created IGNITE-5981: --- Summary: IgniteContext starts server nodes on executors Key: IGNITE-5981 URL: https://issues.apache.org/jira/browse/IGNITE-5981 Project: Ignite

[jira] [Created] (IGNITE-5955) Ignite Continuous Query (Queries 3): IgniteCacheContinuousQueryClientReconnectTest fails

Sergey Chugunov created IGNITE-5955: --- Summary: Ignite Continuous Query (Queries 3): IgniteCacheContinuousQueryClientReconnectTest fails Key: IGNITE-5955 URL: https://issues.apache.org/jira/browse/IGNITE-5955

Re: release procedure

Vote for #3 On Sun, Aug 6, 2017 at 3:37 PM, Oleg Ostanin wrote: > Hi, > > I'd like to start a discussion about Apache Ignite release procedure. > > I'm working on ticket Ignite-5249 "The release build procedure should be > placed on the CI/CD server and available to run

[jira] [Created] (IGNITE-5954) Ignite Cache Failover: GridCacheAtomicNearRemoveFailureTest.testPutAndRemove fails

Eduard Shangareev created IGNITE-5954: - Summary: Ignite Cache Failover: GridCacheAtomicNearRemoveFailureTest.testPutAndRemove fails Key: IGNITE-5954 URL: https://issues.apache.org/jira/browse/IGNITE-5954

Re: ODBC API conformance page updated

Igor, can you please rename the page for now? On Mon, Aug 7, 2017 at 2:33 AM, Igor Sapego wrote: > Dmitriy, > > There are comments where there are issues with implementation of certain > features. Where there are no such comment, it is simply means that those > features are

[jira] [Created] (IGNITE-5956) Ignite Continuous Query (Queries 3): IgniteCacheDistributedJoinPartitionedAndReplicatedTest fails

Sergey Chugunov created IGNITE-5956: --- Summary: Ignite Continuous Query (Queries 3): IgniteCacheDistributedJoinPartitionedAndReplicatedTest fails Key: IGNITE-5956 URL:

[jira] [Created] (IGNITE-5951) DDL: Support CREATE VIEW

Vyacheslav Koptilin created IGNITE-5951: --- Summary: DDL: Support CREATE VIEW Key: IGNITE-5951 URL: https://issues.apache.org/jira/browse/IGNITE-5951 Project: Ignite Issue Type:

Re: [IGNITE-5717] improvements of MemoryPolicy default size

Dmitriy, When Ignite node "allocates memory" it actually just reserves a chunk in its address space, almost no physical RAM is used. I can easily start half a dozen of ignite nodes with current defaults on my laptop with only 16 Gigs of RAM; and each node will "allocate" around 12 Gigs; 72

[GitHub] ignite pull request #2408: IGNITE-5941 : Fixed index name length restriction...

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2408 IGNITE-5941 : Fixed index name length restrictions. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5941

[GitHub] ignite pull request #2409: Ignite gg 12508

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2409 Ignite gg 12508 PR for tests run. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12508 Alternatively you can

[jira] [Created] (IGNITE-5952) Need to refactor IgniteSystemProperties

Yakov Zhdanov created IGNITE-5952: - Summary: Need to refactor IgniteSystemProperties Key: IGNITE-5952 URL: https://issues.apache.org/jira/browse/IGNITE-5952 Project: Ignite Issue Type:

[GitHub] ignite pull request #2405: IGNITE-5384: cleanup

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/2405 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[jira] [Created] (IGNITE-5960) Ignite Continuous Query (Queries 3): CacheContinuousQueryConcurrentPartitionUpdateTest::testConcurrentUpdatesAndQueryStartAtomic is flaky

Sergey Chugunov created IGNITE-5960: --- Summary: Ignite Continuous Query (Queries 3): CacheContinuousQueryConcurrentPartitionUpdateTest::testConcurrentUpdatesAndQueryStartAtomic is flaky Key: IGNITE-5960 URL:

[jira] [Created] (IGNITE-5961) Align pages in LFS partition files to pageSize

Ivan Rakov created IGNITE-5961: -- Summary: Align pages in LFS partition files to pageSize Key: IGNITE-5961 URL: https://issues.apache.org/jira/browse/IGNITE-5961 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-5958) Ignite Cache 3: IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator fails

Pavel Kovalenko created IGNITE-5958: --- Summary: Ignite Cache 3: IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator fails Key: IGNITE-5958 URL: https://issues.apache.org/jira/browse/IGNITE-5958

[GitHub] ignite pull request #2407: IGNITE-5211 Classes based constructor for QueryEn...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2407 IGNITE-5211 Classes based constructor for QueryEntities You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-5957) Ignite IGFS: IgfsStreamsSelfTest.testCreateFileColocated fails

Pavel Kovalenko created IGNITE-5957: --- Summary: Ignite IGFS: IgfsStreamsSelfTest.testCreateFileColocated fails Key: IGNITE-5957 URL: https://issues.apache.org/jira/browse/IGNITE-5957 Project: Ignite

[jira] [Created] (IGNITE-5959) Ignite Hadoop: testClientReconnect and testClientReconnectMultithreaded fail

Pavel Kovalenko created IGNITE-5959: --- Summary: Ignite Hadoop: testClientReconnect and testClientReconnectMultithreaded fail Key: IGNITE-5959 URL: https://issues.apache.org/jira/browse/IGNITE-5959

[jira] [Created] (IGNITE-5962) Increase max length of index name

Ilya Lantukh created IGNITE-5962: Summary: Increase max length of index name Key: IGNITE-5962 URL: https://issues.apache.org/jira/browse/IGNITE-5962 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-5963) Ignite Cache 6: Flaky failure IgniteOptimisticTxSuspendResumeMultiServerTest.testTxTimeoutOnSuspend on TC

Dmitriy Pavlov created IGNITE-5963: -- Summary: Ignite Cache 6: Flaky failure IgniteOptimisticTxSuspendResumeMultiServerTest.testTxTimeoutOnSuspend on TC Key: IGNITE-5963 URL:

[jira] [Created] (IGNITE-5948) SQL: UNIQUE constraint support.

Andrew Mashenkov created IGNITE-5948: Summary: SQL: UNIQUE constraint support. Key: IGNITE-5948 URL: https://issues.apache.org/jira/browse/IGNITE-5948 Project: Ignite Issue Type: New

[GitHub] ignite pull request #2403: for test purposes.

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2403 for test purposes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4800-fix-test Alternatively you can

[jira] [Created] (IGNITE-5950) Incorrect assertion for cache size

Sergey Chugunov created IGNITE-5950: --- Summary: Incorrect assertion for cache size Key: IGNITE-5950 URL: https://issues.apache.org/jira/browse/IGNITE-5950 Project: Ignite Issue Type: Bug

Re: ODBC API conformance page updated

Dmitriy, There are comments where there are issues with implementation of certain features. Where there are no such comment, it is simply means that those features are not implemented just because no one has ever implemented them. Best Regards, Igor On Fri, Aug 4, 2017 at 9:32 PM, Dmitriy

[GitHub] ignite pull request #2404: Ignite 5953 - Missed off-heap unswapping in GridC...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/2404 Ignite 5953 - Missed off-heap unswapping in GridCacheMap.versionedValue() You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-5949) DDL: Support ALTER TABLE DROP COLUMN

Andrew Mashenkov created IGNITE-5949: Summary: DDL: Support ALTER TABLE DROP COLUMN Key: IGNITE-5949 URL: https://issues.apache.org/jira/browse/IGNITE-5949 Project: Ignite Issue Type:

[GitHub] ignite pull request #2394: IGNITE-5880: BLAS integration phase 2

Github user ybabak closed the pull request at: https://github.com/apache/ignite/pull/2394 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-5967) Flaky fail in Ignite Java Client: RedisProtocolStringSelfTest.testGetSet

Dmitriy Govorukhin created IGNITE-5967: -- Summary: Flaky fail in Ignite Java Client: RedisProtocolStringSelfTest.testGetSet Key: IGNITE-5967 URL: https://issues.apache.org/jira/browse/IGNITE-5967

[jira] [Created] (IGNITE-5968) Test fail in Ignite Cache 2: GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead

Dmitriy Govorukhin created IGNITE-5968: -- Summary: Test fail in Ignite Cache 2: GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead Key: IGNITE-5968 URL:

[jira] [Created] (IGNITE-5965) Ignite Basic: Flaky failure of GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology

Ivan Rakov created IGNITE-5965: -- Summary: Ignite Basic: Flaky failure of GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology Key: IGNITE-5965 URL:

[jira] [Created] (IGNITE-5964) test fail: TcpClientDiscoverySpiSelfTest (disconnectLatch timeout)

Konstantin Dudkov created IGNITE-5964: - Summary: test fail: TcpClientDiscoverySpiSelfTest (disconnectLatch timeout) Key: IGNITE-5964 URL: https://issues.apache.org/jira/browse/IGNITE-5964

IgniteUtils#currentTimeMillis

Hello, Igniters. I found unusual implementation of IgniteUtils#currentTimeMillis function. Method is not simple proxy to System.currentTimeMillis Instead it read static variable which updated by dedicated thread:

[jira] [Created] (IGNITE-5966) IgniteCache#get() fails with "Requesting mapping from grid failed" when deserialising binary object loaded from CacheJdbcPojoStoreFactory

Alexey Kukushkin created IGNITE-5966: Summary: IgniteCache#get() fails with "Requesting mapping from grid failed" when deserialising binary object loaded from CacheJdbcPojoStoreFactory Key: IGNITE-5966 URL:

[jira] [Created] (IGNITE-5970) Ignite Binary Objects Simple Mapper Basic: Flaky failure of org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest#testConcurrentDeploymentWithDelegatingClassloader

Ivan Rakov created IGNITE-5970: -- Summary: Ignite Binary Objects Simple Mapper Basic: Flaky failure of org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest#testConcurrentDeploymentWithDelegatingClassloader Key: IGNITE-5970

[jira] [Created] (IGNITE-5974) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSemaphore

Eduard Shangareev created IGNITE-5974: - Summary: [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSemaphore Key: IGNITE-5974 URL: https://issues.apache.org/jira/browse/IGNITE-5974

[jira] [Created] (IGNITE-5973) [Test Failed] GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe

Eduard Shangareev created IGNITE-5973: - Summary: [Test Failed] GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe Key: IGNITE-5973 URL:

[jira] [Created] (IGNITE-5975) [Test Failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreSingleNodeFailure

Eduard Shangareev created IGNITE-5975: - Summary: [Test Failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreSingleNodeFailure Key: IGNITE-5975 URL:

[jira] [Created] (IGNITE-5976) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testReentrantLock

Eduard Shangareev created IGNITE-5976: - Summary: [Test Failed] IgniteClientDiscoveryDataStructuresTest.testReentrantLock Key: IGNITE-5976 URL: https://issues.apache.org/jira/browse/IGNITE-5976

[GitHub] ignite pull request #2381: IGNITE-5732 Provide API to test compatibility wit...

Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/2381 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #2410: IGNITE-5732 Provide API to test compatibility wit...

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/2410 IGNITE-5732 Provide API to test compatibility with old releases You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite

[jira] [Created] (IGNITE-5971) Ignite Continuous Query 2: Flaky failure of #testMultiThreadedFailover

Ivan Rakov created IGNITE-5971: -- Summary: Ignite Continuous Query 2: Flaky failure of #testMultiThreadedFailover Key: IGNITE-5971 URL: https://issues.apache.org/jira/browse/IGNITE-5971 Project: Ignite

[jira] [Created] (IGNITE-5972) [Test Failed] IgniteCountDownLatchAbstractSelfTest.testLatchBroadcast

Eduard Shangareev created IGNITE-5972: - Summary: [Test Failed] IgniteCountDownLatchAbstractSelfTest.testLatchBroadcast Key: IGNITE-5972 URL: https://issues.apache.org/jira/browse/IGNITE-5972

Re: IgniteUtils#currentTimeMillis

Addition to my previous message: 1. IgniteUtils#currentTimeMillis used in current master to check transaction timeout: https://github.com/apache/ignite/blob/master/modules/ core/src/main/java/org/apache/ignite/internal/processors/cache/transactions/ IgniteTxAdapter.java#L664 2. According to jdk

[jira] [Created] (IGNITE-5977) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSequence

Eduard Shangareev created IGNITE-5977: - Summary: [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSequence Key: IGNITE-5977 URL: https://issues.apache.org/jira/browse/IGNITE-5977