[GitHub] ignite pull request #2425: IGNITE-5097 BinaryMarshaller should write ints in...

2017-08-09 Thread daradurvs
GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/2425 IGNITE-5097 BinaryMarshaller should write ints in "varint" encoding where it makes sense You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-6002) Make log message more pretty when instance name is null

2017-08-09 Thread Kousuke Saruta (JIRA)
Kousuke Saruta created IGNITE-6002: -- Summary: Make log message more pretty when instance name is null Key: IGNITE-6002 URL: https://issues.apache.org/jira/browse/IGNITE-6002 Project: Ignite

[GitHub] ignite pull request #2418: [IGNITE-6002] Make log message more pretty when i...

2017-08-09 Thread sarutak
GitHub user sarutak opened a pull request: https://github.com/apache/ignite/pull/2418 [IGNITE-6002] Make log message more pretty when instance name is null When instance name is null, log message containing "null" is shown like as follows. ``` [09-08-2017

[GitHub] ignite pull request #2202: IGNITE-5076: improved multi-threaded start of nod...

2017-08-09 Thread sk0x50
Github user sk0x50 closed the pull request at: https://github.com/apache/ignite/pull/2202 --- 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 #2194: IGNITE-5076: improved multi-threaded start of nod...

2017-08-09 Thread sk0x50
Github user sk0x50 closed the pull request at: https://github.com/apache/ignite/pull/2194 --- 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 #2259: Ignite 5562 Assertions in TCP discovery SPI when ...

2017-08-09 Thread sk0x50
Github user sk0x50 closed the pull request at: https://github.com/apache/ignite/pull/2259 --- 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-6003) Detecting low memory on ignite node startup

2017-08-09 Thread Sergey Chugunov (JIRA)
Sergey Chugunov created IGNITE-6003: --- Summary: Detecting low memory on ignite node startup Key: IGNITE-6003 URL: https://issues.apache.org/jira/browse/IGNITE-6003 Project: Ignite Issue

[jira] [Created] (IGNITE-6004) SQL: add "inlineSize" to QuerySqlField annotation

2017-08-09 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-6004: --- Summary: SQL: add "inlineSize" to QuerySqlField annotation Key: IGNITE-6004 URL: https://issues.apache.org/jira/browse/IGNITE-6004 Project: Ignite

Re: IGNITE-5994: IgniteInternalCache.invokeAsync().get() can return null

2017-08-09 Thread Yakov Zhdanov
Replied in ticket. Also posting here. Currently invokeAsync() is defined as public IgniteFuture invokeAsync(.). If we need EntryProcessorResult to be returned from Future then it should be public IgniteFuture invokeAsync(.). I am not sure why we have this

[GitHub] ignite pull request #2414: IGNITE-5993

2017-08-09 Thread devozerov
Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/2414 --- 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

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

2017-08-09 Thread Sergey Chugunov
Folks, I filed a ticket [1] to address the concern of starting too many nodes. Please review it. [1] https://issues.apache.org/jira/browse/IGNITE-6003 Thanks, Sergey. On Mon, Aug 7, 2017 at 12:53 PM, Sergey Chugunov wrote: > Dmitriy, > > When Ignite node "allocates

[GitHub] ignite pull request #2384: IGNITE-5897: Fix session init/end logic. This fix...

2017-08-09 Thread nizhikov
Github user nizhikov closed the pull request at: https://github.com/apache/ignite/pull/2384 --- 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

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Yakov Zhdanov
Nickolay, IgniteUtils#currentTimeMillis() is some kind of an old heritage. I guess nobody remembers when this method has been introduced. I agree that we can use System.currentTimeMillis(). I would suggest you file a ticket and replace this method calls with System.currentTimeMillis(). Sounds

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

2017-08-09 Thread Yakov Zhdanov
Sergey, ticket looks good to me (https://issues.apache.org/ jira/browse/IGNITE-6003). --Yakov

[jira] [Created] (IGNITE-6005) [Test failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe

2017-08-09 Thread Eduard Shangareev (JIRA)
Eduard Shangareev created IGNITE-6005: - Summary: [Test failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe Key: IGNITE-6005 URL:

[GitHub] ignite pull request #2419: IGNITE-5452 GridTimeoutProcessor can hang on stop

2017-08-09 Thread dmekhanikov
GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/2419 IGNITE-5452 GridTimeoutProcessor can hang on stop Created for testing You can merge this pull request into a Git repository by running: $ git pull

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Vladimir Ozerov
Java could do some heavy stuff when doing currentTimeMillis, depending on the platform or vendor. I remember I saw some articles about performance issues caused by currentTimeMillis (something about high contention on certain OS configuration). So I do not see a reason why we should remove it. It

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Dmitry Pavlov
It seems System.currentTimeMillis () is now in intrinsic list. This means on modern JVMs performance penalty will not be so significiant. Nickolay, could you please raise standalone ticket for U.currentTimeMillis () ? Could you also please check if system.nanoTime / system.currentTimeMs can fix

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Dmitry Pavlov
Vladimir, could we check it using benchmarks? Internet contains a lot of articles about this issue. But do we know if it is still actual for new VMs? ср, 9 авг. 2017 г. в 14:50, Dmitry Pavlov : > It seems System.currentTimeMillis () is now in intrinsic list. This means >

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Vladimir Ozerov
You cannot check it with benchmarks, because behavior of this method will vary between different JVMs, OSes and hardware. It can be different even with the same OS depending on it's settings. Again - let's just avoid unnecessary work. There is nothing wrong with U.currentTimeMillis() at the

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Николай Ижиков
Hello, Dima. > Nickolay, could you please raise standalone ticket for U.currentTimeMillis () ? Yes, I can. > https://issues.apache.org/jira/browse/IGNITE-5963 I will try to make quick fix for issue without change Ignite core code. So fix will not depend to U.currentTimeMillis() implementation.

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Николай Ижиков
Vladimir, > There is nothing wrong with U.currentTimeMillis() at the moment. I think we can't rely on the return value for time measurement. Is it true? Is it OK for you? It very counterintuitive for me as newcomer. 2017-08-09 14:55 GMT+03:00 Vladimir Ozerov : > You

[jira] [Created] (IGNITE-6006) IgniteCacheGetRestartTest fails sometimes on TC

2017-08-09 Thread Ilya Lantukh (JIRA)
Ilya Lantukh created IGNITE-6006: Summary: IgniteCacheGetRestartTest fails sometimes on TC Key: IGNITE-6006 URL: https://issues.apache.org/jira/browse/IGNITE-6006 Project: Ignite Issue Type:

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Dmitriy Setrakyan
On Wed, Aug 9, 2017 at 4:59 AM, Николай Ижиков wrote: > Vladimir, > > > There is nothing wrong with U.currentTimeMillis() at the > moment. > > I think we can't rely on the return value for time measurement. > Is it true? Is it OK for you? > > It very counterintuitive for

[jira] [Created] (IGNITE-6007) GridCacheBinaryObjectMetadataExchangeMultinodeTest.testSequentialUpdatesNoConflicts fails sometimes

2017-08-09 Thread Ilya Lantukh (JIRA)
Ilya Lantukh created IGNITE-6007: Summary: GridCacheBinaryObjectMetadataExchangeMultinodeTest.testSequentialUpdatesNoConflicts fails sometimes Key: IGNITE-6007 URL:

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Dmitry Pavlov
+1 to Nikolay, this is very often question from newcomers. It is not clear that current* method may return outdated value from some moment in past. Nikolay, how long outdated value can be returned by method? ср, 9 авг. 2017 г. в 15:00, Николай Ижиков : > Vladimir, > > >

[jira] [Created] (IGNITE-6008) CacheRemoveAllSelfTest.testRemoveAll fails sometimes

2017-08-09 Thread Ilya Lantukh (JIRA)
Ilya Lantukh created IGNITE-6008: Summary: CacheRemoveAllSelfTest.testRemoveAll fails sometimes Key: IGNITE-6008 URL: https://issues.apache.org/jira/browse/IGNITE-6008 Project: Ignite Issue

[jira] [Created] (IGNITE-6009) CacheExamplesSelfTest.testCacheSemaphoreExample fails sometimes due to timeout

2017-08-09 Thread Ilya Lantukh (JIRA)
Ilya Lantukh created IGNITE-6009: Summary: CacheExamplesSelfTest.testCacheSemaphoreExample fails sometimes due to timeout Key: IGNITE-6009 URL: https://issues.apache.org/jira/browse/IGNITE-6009

[jira] [Created] (IGNITE-6010) ZookeeperIpFinderTest.testFourNodesKillRestartZookeeper fails sometimes

2017-08-09 Thread Ilya Lantukh (JIRA)
Ilya Lantukh created IGNITE-6010: Summary: ZookeeperIpFinderTest.testFourNodesKillRestartZookeeper fails sometimes Key: IGNITE-6010 URL: https://issues.apache.org/jira/browse/IGNITE-6010 Project:

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Vladimir Ozerov
Guys, Are you really suggesting change the product for newcomer needs? This is not an argument for the change. Can someone explain me what is currently broken from product's perspective? Yes, we can get stale values for some time, we know that. Does it break something? On Wed, Aug 9, 2017 at

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Николай Ижиков
Vladimir, As far as I can understand behaviour of U.currentTimeMillis() breaks transaction timeout test: https://issues.apache.org/jira/browse/IGNITE-5963 IgniteOptimisticTxSuspendResumeTest#testTxTimeoutOnSuspend : ``` final Transaction tx = ignite.transactions().txStart(OPTIMISTIC,

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Vladimir Ozerov
I would propose to either increase TX_TIMEOUT or sleep multiplier to make test more reliable. On Wed, Aug 9, 2017 at 3:32 PM, Николай Ижиков wrote: > Vladimir, > > As far as I can understand behaviour of U.currentTimeMillis() breaks > transaction timeout test: > >

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Dmitriy Setrakyan
On Wed, Aug 9, 2017 at 5:32 AM, Николай Ижиков wrote: > Vladimir, > > As far as I can understand behaviour of U.currentTimeMillis() breaks > transaction timeout test: > So, if you change the call to System.currentTimeMillis(), the test passes?

[jira] [Created] (IGNITE-6011) EntryProcessor can make data inconsistent if fails on TX cache.

2017-08-09 Thread Andrew Mashenkov (JIRA)
Andrew Mashenkov created IGNITE-6011: Summary: EntryProcessor can make data inconsistent if fails on TX cache. Key: IGNITE-6011 URL: https://issues.apache.org/jira/browse/IGNITE-6011 Project:

[GitHub] ignite pull request #2420: IGNITE-6004 SQL: add "inlineSize" to QuerySqlFiel...

2017-08-09 Thread tledkov-gridgain
GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2420 IGNITE-6004 SQL: add "inlineSize" to QuerySqlField annotation You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Николай Ижиков
Dmitry, > So, if you change the call to System.currentTimeMillis(), the test passes? Yes > I would propose to either increase TX_TIMEOUT or sleep multiplier to make test more reliable. Yes, I fix test in that way. For me the goal of this discussion is to understand reasons to keep current

[GitHub] ignite pull request #2072: ignite-5097-dotnet-integration

2017-08-09 Thread daradurvs
Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/2072 --- 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 #1533: IGNITE-3422 No way to control object initializati...

2017-08-09 Thread daradurvs
Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/1533 --- 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 #1902: IGNITE-5097 BinaryMarshaller should write ints in...

2017-08-09 Thread daradurvs
Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/1902 --- 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

Hibernate dialect for Ignite

2017-08-09 Thread Dmitriy Setrakyan
Igniters, Given that we have a very rich SQL support starting with version 2.1, does it make sense to create an Ignite SQL dialect for Hibernate? https://docs.jboss.org/hibernate/orm/3.6/reference/en-US/html/session-configuration.html#configuration-optional-dialects D.

Re: Data compression in Ignite 2.0

2017-08-09 Thread Vyacheslav Daradur
Vladimir, thank you for detailed explanation. I think I've understanded the main idea of described storage compression. I'll join the new discussion after researching of given material and comlpetion of varint-optimization [1]. [1] https://issues.apache.org/jira/browse/IGNITE-5097 2017-08-02

[GitHub] ignite pull request #2366: IGNITE-5882 Duplicated dependency in pom.xml of c...

2017-08-09 Thread daradurvs
Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/2366 --- 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 #2342: for-dotNET-tests-ignite-5712

2017-08-09 Thread daradurvs
Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/2342 --- 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 #1652: IGNITE-3682 GridFunc: move all inner anonymous cl...

2017-08-09 Thread daradurvs
Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/1652 --- 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

Re: release procedure

2017-08-09 Thread Konstantin Boudnik
There's also #4: - providing an official environment, comprised of the toolchain, compilers, libs, etc,. The same environment (read "a container") could be used by an individual developer, RM, and/or in CI system for builds, tests, etc. And then you can have #3 pretty much for free! We are doing

[jira] [Created] (IGNITE-6015) Test fail in Ignite Cache 2: GridCachePartitionedGetAndTransformStoreSelfTest.testGetAndTransform

2017-08-09 Thread Dmitriy Govorukhin (JIRA)
Dmitriy Govorukhin created IGNITE-6015: -- Summary: Test fail in Ignite Cache 2: GridCachePartitionedGetAndTransformStoreSelfTest.testGetAndTransform Key: IGNITE-6015 URL:

Re: Data compression in Ignite

2017-08-09 Thread Ivan Rakov
+1 for per-page approach (2). I'm not sure if dictionary-based encoding within page is really efficient. Compression quality grows with increasing size of sample (it's pageSize in our case - not so big), and we can't encode "words" on the border of two entries. Also, we'll have to

[jira] [Created] (IGNITE-6016) Get rid of checking topology hash in ackTopology

2017-08-09 Thread Ivan Rakov (JIRA)
Ivan Rakov created IGNITE-6016: -- Summary: Get rid of checking topology hash in ackTopology Key: IGNITE-6016 URL: https://issues.apache.org/jira/browse/IGNITE-6016 Project: Ignite Issue Type:

[GitHub] ignite pull request #2422: IGNITE-5963: Add additional check to Thread.sleep...

2017-08-09 Thread nizhikov
GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/2422 IGNITE-5963: Add additional check to Thread.sleep to make test correc… …t in all cases. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2424: IGNITE-6016 Get rid of checking topology hash in ...

2017-08-09 Thread glukos
GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2424 IGNITE-6016 Get rid of checking topology hash in ackTopology You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6016

[jira] [Created] (IGNITE-6018) Introduce WAL backward compatibility for new DataPage insert/update records

2017-08-09 Thread Pavel Kovalenko (JIRA)
Pavel Kovalenko created IGNITE-6018: --- Summary: Introduce WAL backward compatibility for new DataPage insert/update records Key: IGNITE-6018 URL: https://issues.apache.org/jira/browse/IGNITE-6018

[GitHub] ignite pull request #2423: IGNITE-5943

2017-08-09 Thread EdShangGG
GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/2423 IGNITE-5943 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGNITE-5943 Alternatively you can review and apply these

[jira] [Created] (IGNITE-6017) Ignite IGFS: IgfsStreamsSelfTest#testCreateFileFragmented fails

2017-08-09 Thread Pavel Kovalenko (JIRA)
Pavel Kovalenko created IGNITE-6017: --- Summary: Ignite IGFS: IgfsStreamsSelfTest#testCreateFileFragmented fails Key: IGNITE-6017 URL: https://issues.apache.org/jira/browse/IGNITE-6017 Project:

Re: Resurrect FairAffinityFunction

2017-08-09 Thread Valentin Kulichenko
As far as I know, all logical caches with the same affinity function and node filter will end up in the same group. If that's the case, I like the idea. This is exactly what I was looking for. -Val On Wed, Aug 9, 2017 at 8:18 AM, Evgenii Zhuravlev wrote: > Dmitriy, >

Re: Cluster auto activation design proposal

2017-08-09 Thread Denis Magda
Sergey, That’s the only concern I have: * 5. User takes out nodes from cluster (e.g. for maintenance purposes): no rebalance happens until user recreates BLT on new cluster topology.* What if a node is crashed (or some other kind of outage) in the middle of the night and the user has to be

Re: Zeppelin, MyBatis and Vert.x update to AI 2.1

2017-08-09 Thread Denis Magda
Roman, thanks! Andrey, will you be able to complete it this week? — Denis > On Aug 3, 2017, at 7:14 AM, Andrey Gura wrote: > > Hi, > > I'll do it soon. But there is problem with Zeppelin because CI should > be configured on local machine. So I need more time than usually

Re: Ignite.close(), G.stop(name, true). Change flag cancel to false

2017-08-09 Thread Denis Magda
I’m totally for the replacement of ‘crashed’ with ‘stopped’. As for the waiting of the checkpointing completion I would NOT do it the default behavior and would rather check the ‘cancel’ flag to make a decision. If the ‘cancel’ is ‘true’ (which is default) then we’re not going to wait for the

[GitHub] ignite pull request #2383: IGNITE-5912: Redis EXPIRE/PEXPIRE commands.

2017-08-09 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2383 --- 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

IGNITE-5714 Context switching for pessimistic transactions

2017-08-09 Thread ALEKSEY KUZNETSOV
Hi, Igntrs! Currently we have context switching implemented for optimistic transactions : https://issues.apache.org/jira/browse/IGNITE-5712. So, the next step is to implement it for pessimistic transactions : https://issues.apache.org/jira/browse/IGNITE-5714 The problem with them lies in

[jira] [Created] (IGNITE-6013) Web agent: refactor processing response from cluster

2017-08-09 Thread Alexey Kuznetsov (JIRA)
Alexey Kuznetsov created IGNITE-6013: Summary: Web agent: refactor processing response from cluster Key: IGNITE-6013 URL: https://issues.apache.org/jira/browse/IGNITE-6013 Project: Ignite

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Vladimir Ozerov
Yakov, For example: http://pzemtsov.github.io/2017/07/23/the-slow-currenttimemillis.html >>> We’ve learned that the slow execution of currentTimeMillis() was caused by two factors: >>> - JVM using gettimeofday() instead of clock_gettime() >>> - gettimeofday() being very slow if HPET time source

[jira] [Created] (IGNITE-6014) Add transaction prepare and commit markers to WAL

2017-08-09 Thread Alexey Goncharuk (JIRA)
Alexey Goncharuk created IGNITE-6014: Summary: Add transaction prepare and commit markers to WAL Key: IGNITE-6014 URL: https://issues.apache.org/jira/browse/IGNITE-6014 Project: Ignite

Re: Data compression in Ignite

2017-08-09 Thread Dmitriy Setrakyan
Vova, I do not understand how (2) will help us reduce the size of the serialized object. It sounds like we need to serialize an object the way we do today, and then compress it when it arrives to the server side and gets stored in some page. This looks like a double whammy. I do not understand

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Alexey Kuznetsov
Nikolay, As far as I understand U.currentTimeMillis() should be used where time is not a major value (metrics for example). But in test with transaction (that you are mentioned) we should use System.currentTimeMillis(). In general we should think about U.currentTimeMillis() and avoid it usage

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Yakov Zhdanov
As Dmitry P mentioned System.currentTimeMillis() is JVM intrinsic. Moreover, there is a daemon thread that updates the internal value which will not be needed after the change. If we remove U.currentTimeMillis() code will become more clear and consistent. Why we think that we can implement this

Re: Resurrect FairAffinityFunction

2017-08-09 Thread ezhuravl
Folks, I've started working on a https://issues.apache.org/jira/browse/IGNITE-5836 ticket and found that the recently added feature with cacheGroups doing pretty much the same that was described in this issue. CacheGroup guarantees that all caches within a group have same assignments since they

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Evgeniy Stanilovskiy
I assume that Vladimir mention this mesurements: https://shipilev.net/blog/2014/nanotrusting-nanotime/ can we simple measure with JMH x86 and arm our realization vs system call? As Dmitry P mentioned System.currentTimeMillis() is JVM intrinsic. Moreover, there is a daemon thread that updates

[jira] [Created] (IGNITE-6012) Improve GridJettyRestHandler.processRequest()

2017-08-09 Thread Alexey Kuznetsov (JIRA)
Alexey Kuznetsov created IGNITE-6012: Summary: Improve GridJettyRestHandler.processRequest() Key: IGNITE-6012 URL: https://issues.apache.org/jira/browse/IGNITE-6012 Project: Ignite Issue

[GitHub] ignite pull request #2421: IGNITE-5995: ODBC: Fix for SQLGetData

2017-08-09 Thread isapego
GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2421 IGNITE-5995: ODBC: Fix for SQLGetData You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5995 Alternatively you

Re: Add isPrimary() and isBackup() methods on CacheQueryEntryEvent

2017-08-09 Thread Kozlov Maxim
Igniters, What do you think about the new API? > 3 авг. 2017 г., в 15:56, Kozlov Maxim написал(а): > > Guys, > > I'm sorry for the misunderstanding, I was tired at the end of the day :-) > In the process of working on the task, I had to add 2 methods to the public >

Data compression in Ignite

2017-08-09 Thread Vladimir Ozerov
Igniters, I had several private talks with Igniters about data compression and would like to share the summary with ... Igniters :-) Currently all Ignite's data is uncompressed. It leads to excessive network traffic, GC pressure and disk IO (in case of persistence). Most modern databases are

[GitHub] ignite pull request #2387: IGNITE-5736 Add test of backward-compatibility

2017-08-09 Thread daradurvs
Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/2387 --- 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

Re: IgniteUtils#currentTimeMillis

2017-08-09 Thread Vladimir Ozerov
In short, the reason is avoiding potential performance problems. On Wed, Aug 9, 2017 at 3:49 PM, Николай Ижиков wrote: > Dmitry, > > > So, if you change the call to System.currentTimeMillis(), the test > passes? > > Yes > > > I would propose to either increase TX_TIMEOUT

Re: Resurrect FairAffinityFunction

2017-08-09 Thread Dmitriy Setrakyan
On Wed, Aug 9, 2017 at 6:28 AM, ezhuravl wrote: > Folks, > > I've started working on a https://issues.apache.org/ > jira/browse/IGNITE-5836 > ticket and found that the recently added feature with cacheGroups doing > pretty much the same that was described in this issue.

Re: Data compression in Ignite

2017-08-09 Thread Yakov Zhdanov
Agree, I like 2 best of all. --Yakov

Re: Resurrect FairAffinityFunction

2017-08-09 Thread Evgenii Zhuravlev
Dmitriy, Yes, you're right. Moreover, it looks like a good practice to combine caches that will be used for collocated JOINs in one group since it reduces overall overhead. I think it's not a problem to add this restriction to the SQL JOIN level if we will decide to use this solution. Evgenii