[jira] [Created] (IGNITE-3187) IGFS: Print acceptable IGFS endpoints to the console on node start.
Vladimir Ozerov created IGNITE-3187: --- Summary: IGFS: Print acceptable IGFS endpoints to the console on node start. Key: IGNITE-3187 URL: https://issues.apache.org/jira/browse/IGNITE-3187 Project: Ignite Issue Type: Improvement Components: hadoop, IGFS Affects Versions: 1.6 Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 1.7 *Problem* When user starts a node with IGFS, he need to know it's endpoint to be used in URI's (e.g. "igfs://igfs@"). There are non-trivial rules no how the scheme is formed, and sometime it is difficult to understand which scheme to use. *Solution* Let's print acceptable schemes to the console on node start. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] ignite pull request: Ignite 2969
GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/749 Ignite 2969 You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-2969 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/749.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #749 commit 92229d2a6c6ef86772a62cb52b3aa07a55c99d89 Author: sboikov Date: 2016-01-13T05:56:34Z ignite-2359 Added locking for files used by MarshallerContextImpl. (cherry picked from commit 1d8c4e2) commit 2e4ce585d5f54502c6511d3425b1cd5fbf0a7f4f Author: Ignite Teamcity Date: 2016-01-13T10:37:33Z 1.5.4-SNAPSHOT commit 6e5f9f0c7d4c86773b1f0cd5c5a673acb58c86c2 Author: Denis Magda Date: 2016-01-13T11:42:27Z Changed year to 2016 in Copyrights commit 02dbcfd8ed2701a4f415c8871d0b8fd08bfa0583 Author: Alexey Goncharuk Date: 2016-01-13T13:47:32Z IGNITE-2365 - Notify policy if swap or offheap is enabled and rebalanced entry was not preloaded. IGNITE-2099 - Fixing custom collections. This closes #396 commit 86c2ba2a601e82b824cf17422683e5398a4d8c7d Author: sboikov Date: 2016-01-13T15:40:08Z ignite-2350 Pass update notifier flag in discovery data (all cluster nodes will have the same notifier status as first cluster node) (cherry picked from commit 7175a42) commit e1a494df400fc37ca04e8d88d1cf20bca02607b4 Author: sboikov Date: 2016-01-14T11:16:33Z Renamed fields to change fields write order (to preserve backward compatibility). (cherry picked from commit 2a4adf5) commit 09f978234b6062afa1e1658d5a6439365a856aca Author: sboikov Date: 2016-01-14T11:42:44Z Merge remote-tracking branch 'origin/ignite-1.5.4' into ignite-1.5.4 commit 30043e7892d0b52dc851ce5ec79c7eb3b7cc44fb Author: Denis Magda Date: 2016-01-14T13:02:50Z Added release notes commit cc3db35925698f1670a8bf1c6a1830c0c9b51290 Author: vershov Date: 2016-01-14T14:21:56Z IGNITE-2032 Unwind undeploys in preloader - Fixes #369. Signed-off-by: Alexey Goncharuk commit a5c85ca7749ae90af2e4a29e2162713b480e40fa Author: Valentin Kulichenko Date: 2016-01-15T06:58:41Z Update notifier fixes commit 8f32a29c5a7b28b7e1173582f4c7cef5b6d73b27 Author: Ignite Teamcity Date: 2016-01-15T11:00:29Z 1.5.4-SNAPSHOT commit 6482dc80bf9cdf7aa4f592d9266c6745211b1c4c Author: sboikov Date: 2016-01-15T12:15:02Z ignite-2386 Fixed DiscoverManager to do not increase minor topology version if exchange is not triggered. (cherry picked from commit d881417) commit 4ba6574dfa8077f8de23c8c2663826f81c7fd187 Author: sboikov Date: 2016-01-18T15:15:04Z ignite-1811 Optimized cache 'get' on affinity node. (cherry picked from commit 83b2bf5e1f287dc83343945b0e47b83ee7724a8e) Conflicts: modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridPartitionedGetFuture.java modules/core/src/test/java/org/apache/ignite/internal/processors/cache/IgniteCacheStoreCollectionTest.java commit 4b31f4e66c15003cee866a6e5660257346c16c1c Author: sboikov Date: 2016-01-18T15:05:37Z ignite-1811 Optimized cache 'get' on affinity node. (cherry picked from commit 83b2bf5) commit 1cf14fcff58c51a628df6309f05be7f0b840d5f8 Author: Pavel Tupitsyn Date: 2015-12-30T10:51:32Z IGNITE-2228: .NET: Compute futures could be cancelled. commit 2f292788cde807d5f1c80cf9fcb8b29cd4e5ee35 Author: Pavel Tupitsyn Date: 2016-01-18T10:01:43Z IGNITE-2228: Platform compute futures cancellation support. This closes #394. commit 1f5b4a3c478cdf4049af9600c7abe588c3d226fc Author: vozerov-gridgain Date: 2016-01-18T14:24:18Z .NET: IgniteFutureCancelledException is marked as serializable. commit 03148776476f21e542640c204fc97508cde916fc Author: nikolay_tikhonov Date: 2016-01-18T17:41:53Z IGNITE-2384 Fixed "Notification missed in continuous query". commit 612bcb6b4011f99d98c39196173ce7fa60862394 Author: sboikov Date: 2016-01-19T12:30:53Z ignite-1.5.4 Pass currently written message class to MessageWriter. commit 5ba47a03411f507d9db661f83b8fe487b77bec1a Author: Pavel Tupitsyn Date: 2016-01-20T10:48:41Z IGNITE-2414 .NET: TestWithExpiryPolicy is split into two parts: one is fine, another one is muted due to IGNITE-1423. commit bfaf1a634b82bf2666c79bb8f54ce71797d9a778 Author: Denis Magda Date: 2016-01-20T10:48:47Z Fixed queryEntities initialization from a default config commit d0e763cbfbf7f915c942b90901678eba4abde138 Author: Anton Vinogradov Date: 2016-01-20T11:51:36Z G-10964 commit 6577f1145eb67e505d69314250534f3b51ae2780 Author: Alexey Kuznetsov Date: 2016-01-20T14:42:04Z Fixed Visor tasks (cherry picked from commit c77fc84). commit e0ae5248064e22cc0537f22fc5
[GitHub] ignite pull request: IGNITE-2899 BinaryObject is deserialized befo...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/593 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] ignite pull request: IGNITE-3182 Compute jobs execute on client no...
GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/748 IGNITE-3182 Compute jobs execute on client nodes You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-3182 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/748.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #748 commit 25ae4aa997e2dc68f16b1cf236ce7c8d5939f87f Author: Pavel Tupitsyn Date: 2016-05-23T15:14:43Z IGNITE-3182 Compute jobs execute on client nodes commit add05af2e33cf48d7e5963ef9643f011bcd155e6 Author: Pavel Tupitsyn Date: 2016-05-23T15:21:15Z wip commit 349c6f102bcb51aee1714077120142b326f5f87b Author: Pavel Tupitsyn Date: 2016-05-23T15:26:28Z Refactor default prj check --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (IGNITE-3186) [Test] org.apache.ignite.internal.processors.igfs.IgfsProcessorValidationSelfTest#testInvalidEndpointTcpPort fails on master
Ivan Veselovsky created IGNITE-3186: --- Summary: [Test] org.apache.ignite.internal.processors.igfs.IgfsProcessorValidationSelfTest#testInvalidEndpointTcpPort fails on master Key: IGNITE-3186 URL: https://issues.apache.org/jira/browse/IGNITE-3186 Project: Ignite Issue Type: Bug Components: IGFS Reporter: Ivan Veselovsky Assignee: Ivan Veselovsky There is no such problem in 1.6 release, test only fails on master branch . Root cause is that an SPI now does not allow to start one instance more than once. Test does 3 checks, but uses one configuration instance for all them. First check passes, than the 2nd attempts to start the node, but unexpected error happens when an already started Spi is attempted to start. Caused by: class org.apache.ignite.IgniteCheckedException: SPI has already been started (always create new configuration instance for each starting Ignite instances) [spi=TcpCommunicationSpi [connectGate=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$ConnectGateway@ceb47b, srvLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$2@2aaf7a7, locAddr=127.0.0.1, locHost=localhost/127.0.0.1, locPort=45050, locPortRange=100, shmemPort=48100, directBuf=true, directSndBuf=false, idleConnTimeout=3, connTimeout=5000, maxConnTimeout=60, reconCnt=10, sockSndBuf=32768, sockRcvBuf=32768, msgQueueLimit=1024, slowClientQueueLimit=0, nioSrvr=null, shmemSrv=IpcSharedMemoryServerEndpoint [port=48100, tokDirPath=ipc/shmem, size=262144, tokDir=/mnt/tc_disk/temp/buildTmp/ignite/work/ipc/shmem/10fe89ee-1969-4aab-b91c-bb415b45c001-15910, locNodeId=10fe89ee-1969-4aab-b91c-bb415b45c001, gridName=g1, omitOutOfResourcesWarn=true, pid=15910, closed=true], tcpNoDelay=true, ackSndThreshold=16, unackedMsgsBufSize=0, sockWriteTimeout=2000, lsnr=null, boundTcpPort=-1, boundTcpShmemPort=48100, selectorsCnt=4, addrRslvr=null, rcvdMsgsCnt=0, sentMsgsCnt=0, rcvdBytesCnt=0, sentBytesCnt=0, ctxInitLatch=java.util.concurrent.CountDownLatch@2668f64f[Count = 0], stopping=true, metricsLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$3@3502d03c]] at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:956) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1736) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1589) at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:569) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:516) at org.apache.ignite.Ignition.start(Ignition.java:322) ... 11 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3185) Hadoop: Improve Hadoop JAR search logic.
Vladimir Ozerov created IGNITE-3185:
---
Summary: Hadoop: Improve Hadoop JAR search logic.
Key: IGNITE-3185
URL: https://issues.apache.org/jira/browse/IGNITE-3185
Project: Ignite
Issue Type: Bug
Components: hadoop
Affects Versions: 1.5.0.final
Reporter: Vladimir Ozerov
Assignee: Ivan Veselovsky
Fix For: 1.7
*Problem*
Currently our {{HadoopClassLoader}} is trying to find common/hdfs/mapred JARs
automatically if {{HADOOP_HOME}} is set. However, it checks only for standard
Apache Hadoop distribution paths (/share/hadoop/*). For other distributions
(CDH, HDP), user has to bother with additional env variables manually.
*Solution*
Try to search for the following folders as well:
$HADOOP_HOME/hadoop
$HADOOP_HOME/hadoop-hdfs
$HADOOP_HOME/hadoop-mapreduce
If all these folders are found, then this is either HDP or CDH deployment and
we can create the classpath without additional env vars.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Implementing Decimals for C++
Hi Igniters, Currently, I'm working on implementation of analogue of BigDecimal for C++ so that we would be able to support SQL_NUMERIC type for ODBC [1]. I've taken implementation of the BigDecimal class in Java as the base for the C++ implementation. Now I'm wondering, could we have any legal (copyright) issues if we include my code into Apache Ignite? What are your thoughts guys? [1] - https://issues.apache.org/jira/browse/IGNITE-2879 Best Regards, Igor
[jira] [Created] (IGNITE-3184) Hadoop: HADOOP_HOME should not be required if all other environment variables are set.
Vladimir Ozerov created IGNITE-3184: --- Summary: Hadoop: HADOOP_HOME should not be required if all other environment variables are set. Key: IGNITE-3184 URL: https://issues.apache.org/jira/browse/IGNITE-3184 Project: Ignite Issue Type: Bug Components: hadoop Affects Versions: 1.5.0.final Reporter: Vladimir Ozerov Assignee: Ivan Veselovsky Fix For: 1.7 *Problem* Ignite internals require three pieces to create correct Hadoop classpath: 1) Path to common JARs; 2) Path to HDFS JARs; 3) Path map-reduce JARs. These three paths could be set with environment variables HADOOP_COMMON_HOME, HADOOP_HDFS_HOME and HADOOP_MAPRED_HOME respectively. When all of them are set, HADOOP_HOME is no longer needed, but we will throw an exception in this case. We should not do that. *Solution* Throw exception only in case we cannot resolve any of these paths. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] ignite pull request: 7.5.23
GitHub user isuntsov-gridgain opened a pull request: https://github.com/apache/ignite/pull/747 7.5.23 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite gridgain-7.5.23 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/747.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #747 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] ignite pull request: IGNITE-2744 : unwindEvicts() usage optimizati...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/647 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] ignite pull request: IGNITE-1690 testing.
GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/746 IGNITE-1690 testing. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ilantukh/ignite ignite-1690 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/746.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #746 commit 6ac70e7ad68e19ab870b00c545da325c4c0fb638 Author: Ilya Lantukh Date: 2016-05-23T13:16:24Z ignite-1690 : Prepared for testing. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (IGNITE-3183) ScanQuery and localEntries are ignored keepBinary flag in OFFHEAP_TIERED mode
Nikolay Tikhonov created IGNITE-3183:
Summary: ScanQuery and localEntries are ignored keepBinary flag in
OFFHEAP_TIERED mode
Key: IGNITE-3183
URL: https://issues.apache.org/jira/browse/IGNITE-3183
Project: Ignite
Issue Type: Bug
Components: cache, important
Affects Versions: 1.6
Reporter: Nikolay Tikhonov
{{ScanQuery}} and {{localEntries}} method returns iterator which contains
deserialized entries but they have been called with withKeepBinary flag.
Reproducible test attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] ignite pull request: IGNITE-2888
GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/745 IGNITE-2888 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ilantukh/ignite ignite-2888 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/745.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #745 commit a8e48f074c37f1d0ed4c2c9775b658aea7b3c85f Author: Ilya Lantukh Date: 2016-05-23T11:58:59Z ignite-2888 : Extended ConcurrentEvictionConsistencyTest to test different cache configurations. commit 5311fecea91cba4c2e235356338f23f03c7a2674 Author: Ilya Lantukh Date: 2016-05-23T12:14:36Z ignite-2888 : Disabled skipping of removed entries during unlock. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Deadlock detection usage
Dmitry, In this case "blocked" means that transaction can't be rolled back while deadlock detection isn't completed. As soon as detection completes transaction can be rolled back and, for example, retried. So in cases when deadlock detection is switched off transactions will be just rolled back immediately with TransactionTimeoutException, while with deadlock detection they will be blocked during deadlock detection procedure execution. On Mon, May 23, 2016 at 12:30 AM, Dmitriy Setrakyan wrote: > Andrey, > > Can you tell me what transaction is being blocked? If it is the transaction > in deadlock, then I think it should not matter, as it is blocked anyway. > > D. > > On Sun, May 22, 2016 at 2:11 PM, Andrey Gura wrote: > > > Dmitry, > > > > Do you think that we should configure deadlock detection using cache > > configuration? > > > > User should have possibility to have control over this process because it > > blocks transaction until detection completion. > > > > You are right. Deadlock detection starts after transaction timeout and > > lists transactions and keys involved into deadlock in exception message. > > > > > > On Fri, May 20, 2016 at 3:16 AM, Dmitriy Setrakyan < > dsetrak...@apache.org> > > wrote: > > > > > Andrey, > > > > > > Why are we using system properties for the deadlock detection > > > configuration? Also, why would a user want to interrupt the deadlock > > > detection process? > > > > > > To my knowledge, the deadlock detection process should run after > > > transaction has timed out and should include the deadlocked keys into > the > > > timeout exception message. Am I wrong? > > > > > > D. > > > > > > On Wed, May 18, 2016 at 9:38 AM, Andrey Gura > wrote: > > > > > > > Deadlock detection is multi step procedure where steps amount depends > > on > > > > amount of nodes in cluster, keys and transactions that involved into > > > > deadlock. Deadlock detection initiator is a node on whicn transaction > > was > > > > started and timeouted. So this node tries to untangle deadlock step > by > > > step > > > > where each step it is usually request to remote node. So onle > > > > request/response cycle is an iteration. > > > > > > > > Amount of keys, transactions and nodes may be too big. Moreover, > > > > transaction timeout does not mean that deadlock actually exists. So > > user > > > > can limit amount of iterations that deadlock detection performs using > > > > IGNITE_TX_DEADLOCK_DETECTION_MAX_ITERS system property. User also can > > > > switch off deadlock detection using non positive value for this > > property. > > > > > > > > IGNITE_TX_DEADLOCK_DETECTION_TIMEOUT allows to inerrupt deadlock > > > detection > > > > process after specified amount of time. It is another way to limit > time > > > of > > > > execution of deadlock detection process. > > > > > > > > > > > > > > > > On Tue, May 17, 2016 at 10:51 AM, Denis Magda > > > wrote: > > > > > > > > > Andrey, perfect! Thanks a lot for the explanation. > > > > > > > > > > I’ve created a documentation for this functionality and added it to > > 1.6 > > > > > version of readme.io > > > > > > > > > > > > > > > > > > > > http://apacheignite.gridgain.org/v1.6/docs/transactions#deadlock-detection-in-pessimistic-transactions > > > > > > > > > > Please feel free to improve it if needed. > > > > > > > > > > However, I would add more technical details on how the deadlock > > > detection > > > > > procedure works because presently it’s not clear why user need to > > > modify > > > > > these properties - IGNITE_TX_DEADLOCK_DETECTION_MAX_ITERS and > > > > > IGNITE_TX_DEADLOCK_DETECTION_TIMEOUT. > > > > > > > > > > Could you elaborate on the procedure more technically so that its > > clear > > > > > why these properties are needed? > > > > > > > > > > — > > > > > Denis > > > > > > > > > > On May 16, 2016, at 3:47 PM, Andrey Gura > wrote: > > > > > > > > > > Hi, > > > > > > > > > > There is no example how to use it. It just works :) > > > > > > > > > > For now deadlock detection supported only by pessimistic > transactions > > > > with > > > > > timeout. Near cache isn't supported. > > > > > > > > > > User should just start some pessimistic transactions with timeout > and > > > if > > > > > timeout expired then deadlock detection will try to find deadlock. > > > > > TransactionTimeoutException will be thrown and returned to user as > > > cause > > > > > of CacheException regardless of deadlock. But if deadlock detected > > then > > > > > cause of this TransactionTimeoutException will be > > > > > TransactionDeadlockException (at least for one transaction involved > > > into > > > > > deadlock). TransactionDeadlockException contains message like this: > > > > > > > > > > Deadlock detected: > > > > > > > > > > K1: TX1 holds lock, TX2 waits lock. > > > > > K2: TX2 holds lock, TX1 waits lock. > > > > > > > > > > Transactions: > > > > > > > > > > TX1 [txId=GridCacheVersion [topVer=74882201, time=1463402200675, > > > > > order=1463402198603, nodeOrder=
[GitHub] ignite pull request: IGNITE-2865 Continuous query event passed to ...
GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/744 IGNITE-2865 Continuous query event passed to filter should be immutale for users. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2865 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/744.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #744 commit b9feb2900ee2660685710b17503b774765e7bdae Author: tledkov-gridgain Date: 2016-05-20T14:10:13Z IGNITE-2865 Continuous query event passed to filter should be immutable for users. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] ignite pull request: IGNITE-2865 Continuous query event passed to ...
Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/742 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (IGNITE-3182) Compute jobs execute on client nodes
Pavel Tupitsyn created IGNITE-3182: -- Summary: Compute jobs execute on client nodes Key: IGNITE-3182 URL: https://issues.apache.org/jira/browse/IGNITE-3182 Project: Ignite Issue Type: Bug Affects Versions: 1.6 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 1.7 * One server node, one client node, Broadcast from client node results in both nodes executing the closure * Need to check the behavior with 2 servers, 2 clients, broadcast from server and client -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] ignite pull request: Ignite 3164
GitHub user ntikhonov opened a pull request: https://github.com/apache/ignite/pull/743 Ignite 3164 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3164 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/743.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #743 commit b5f594124dbdc75525bdd2c92fc49b9e126e60ab Author: ashutak Date: 2016-05-18T17:47:26Z ignite-3056: Service implementation class is required even if it's not expected to be deployed on current node (fixed) commit c9416ed9b58bbb2287e896cc5860177939c4b3ed Author: nikolay_tikhonov Date: 2016-05-20T09:54:55Z Fixed IGNITE-3004 "Implement config variations test for ContinuousQueries" commit 1ebbd57b74eef1abeb99fa9427667da17db9d01a Author: sboikov Date: 2016-05-23T06:52:43Z ignite-2528 Removed cache blocking operations from kernal write lock. This closes #730 (cherry picked from commit f83a5f7) commit 40a27e714d0bf62a26a35c90c68a020dbf0256c7 Author: sboikov Date: 2016-05-23T04:28:55Z IGNITE-3175 BigDecimal fields are not supported if query is executed from IgniteRDD (cherry picked from commit f2b390a) commit bed9b5958bb741fd72ba438b42cfec4b088528f1 Author: nikolay_tikhonov Date: 2016-05-19T16:58:03Z IGNITE-3164 Temp. commit 12076ebbec5fd2166512281d13e8dd5ff1884cdd Author: nikolay_tikhonov Date: 2016-05-23T09:14:11Z IGNITE-3164 Implemented withSendValueToBackup behaviour for invoke functionality. commit 519c3340a40c0e368edc3003632377455d4c5b64 Author: nikolay_tikhonov Date: 2016-05-23T09:28:56Z IGNITE-3164 WIP. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [RESULT] [VOTE] Apache Ignite 1.6.0 Release (RC1)
Ignite 1.6.0 successfuly released to https://dist.apache.org/repos/dist/release/ignite/1.6.0/ Maven repository and site also updated. On Sat, May 21, 2016 at 6:47 PM, Anton Vinogradov wrote: > Hello! > > Apache Ignite 1.6.0 release (RC1) has been accepted. > > 9 "+1" votes received. > > Here are the votes received: > > - Sergi Vladykin (binding) > - Semyon Boikov (binding) > - Denis Magda (binding) > - Vladimir Ozerov (binding) > - Anton Vinogradov (binding) > - Nikolay Tikhonov (binding) > - Valentin Kulichenko (binding) > - Gianfranco Murador (binding) > - Alexey Kuznetsov > > Here is the link to vote thread - > > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-6-0-RC1-td8992.html > > Ignite 1.6.0 will be released soon. > > Thanks! >
[GitHub] ignite pull request: IGNITE-2865 Continuous query event passed to ...
GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/742 IGNITE-2865 Continuous query event passed to filter should be immutable for users. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2865 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/742.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #742 commit 171b82901f1b25c62f998e5b9b0d0480f7c8079f Author: tledkov-gridgain Date: 2016-05-20T14:10:13Z IGNITE-2865 Continuous query event passed to filter should be immutable for users. commit cd130bc91715cddcc28605be184557a25992ed9b Author: tledkov-gridgain Date: 2016-05-20T14:30:43Z IGNITE-2865 - fix javadoc --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] ignite pull request: IGNITE-3175 BigDecimal fields are not support...
Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/736 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
