date:20161201

[jira] [Resolved] (IGNITE-4314) Cache.clear should not destroy offheap map

2016-12-01 Thread Semen Boikov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov resolved IGNITE-4314.
--
Resolution: Fixed
  Assignee: (was: Semen Boikov)

Fixed, merged in master.

> Cache.clear should not destroy offheap map
> --
>
> Key: IGNITE-4314
> URL: https://issues.apache.org/jira/browse/IGNITE-4314
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Semen Boikov
> Fix For: 1.9
>
>
> Currently when offheap is enabled then cache.clear() operations fully 
> destroys offheap map (GridCacheClearAllRunnable calls 
> GridCacheSwapManager.clearOffHeap). This is not correct since there can be 
> entry referenceing cleared memory, it seems offheap should be cleared in the 
> same way as swap using offheap keys iterator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4058) Divide JVM_OPTS in yardstick properies file

2016-12-01 Thread Oleg Ostanin (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleg Ostanin reassigned IGNITE-4058:


Assignee: Oleg Ostanin

> Divide JVM_OPTS in yardstick properies file
> ---
>
> Key: IGNITE-4058
> URL: https://issues.apache.org/jira/browse/IGNITE-4058
> Project: Ignite
>  Issue Type: Task
>  Components: yardstick
>Affects Versions: 1.7
>Reporter: Sergey Kozlov
>Assignee: Oleg Ostanin
>
> Yardstick properties file has only JVM_OPTS parameter applied to both server 
> and driver nodes. But due logic of some load tests and benchmarks we need to 
> pass different parameters for servers and drivers line heap size (-Xmx, 
> -Xms). I suggest to introduce DRIVER_JVM_OPTS and SERVER_JVM_OPTS. JVM_OPTS 
> should be included into both new parameters and becomes the parameter of 
> general JVM options.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-3443) Implement collecting what SQL statements executed on cluster and their metrics.

2016-12-01 Thread Alexey Kuznetsov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov closed IGNITE-3443.


> Implement collecting what SQL statements executed on cluster and their 
> metrics.
> ---
>
> Key: IGNITE-3443
> URL: https://issues.apache.org/jira/browse/IGNITE-3443
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 1.8
>
>
> We could collect last 1000 (maybe configurable) sql statements with per  
> statement statistics: count, min time, max time, avg time,
> May be execution plan (explain) ?
> ---
> Proposed API changes:
> So, I introduced interface org.apache.ignite.cache.query.QueryDetailsMetrics 
> with metrics:
> {code}
> /**
>  * Query metrics aggregated by query type and its textual representation.
>  */
> public interface QueryDetailsMetrics {
> /**
>  * @return Query type.
>  */
> public String getQueryType();
> /**
>  * @return Textual representation of query.
>  */
> public String getQuery();
> /**
>  * @return Cache where query was executed.
>  */
> public String getCache();
> /**
>  * Gets total number execution of query.
>  *
>  * @return Number of executions.
>  */
> public int getExecutions();
> /**
>  * Gets number of completed execution of query.
>  *
>  * @return Number of completed executions.
>  */
> public int getCompletions();
> /**
>  * Gets number of times a query execution failed.
>  *
>  * @return Number of times a query execution failed.
>  */
> public int getFailures();
> /**
>  * Gets minimum execution time of query.
>  *
>  * @return Minimum execution time of query.
>  */
> public long getMinimumTime();
> /**
>  * Gets maximum execution time of query.
>  *
>  * @return Maximum execution time of query.
>  */
> public long getMaximumTime();
> /**
>  * Gets average execution time of query.
>  *
>  * @return Average execution time of query.
>  */
> public double getAverageTime();
> /**
>  * Gets total time of all query executions.
>  *
>  * @return Total time of all query executions.
>  */
> public long getTotalTime();
> /**
>  * Gets latest query start time.
>  *
>  * @return Latest time query was stared.
>  */
> public long getLastStartTime();
> }
> {code}
> And added method on org.apache.ignite.IgniteCache:
> {code}
> /**
>  * Gets query metrics details.
>  *
>  * @return Metrics.
>  */
> public Collection queryMetricsHistory();
> {code}
> And also I added new property on 
> org.apache.ignite.configuration.CacheConfiguration:
> {code}
> /**
>  * Gets size of queries metrics history that will be stored in memory for 
> monitoring purposes.
>  * If {@code 0} then history will not be collected.
>  * Note, Larger number may lead to higher memory consumption.
>  *
>  * @return Maximum number of query metrics that will be stored in memory.
>  */
> public int getQueryMetricsHistorySize() {
> return qryMetricsHistSz;
> }
> /**
>  * Sets size of queries metrics history that will be stored in memory for 
> monitoring purposes.
>  *
>  * @param qryMetricsHistSz Maximum number of latest queries metrics that will 
> be stored in memory.
>  * @return {@code this} for chaining.
>  */
> public CacheConfiguration setQueryMetricsHistorySize(int 
> qryMetricsHistSz) {
> this.qryMetricsHistSz = qryMetricsHistSz;
> return this;
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4336) Manual rebalance can't be requested twice

2016-12-01 Thread Ilya Lantukh (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15713255#comment-15713255
 ] 

Ilya Lantukh commented on IGNITE-4336:
--

Tests passed, please review.

> Manual rebalance can't be requested twice
> -
>
> Key: IGNITE-4336
> URL: https://issues.apache.org/jira/browse/IGNITE-4336
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Dmitriy Setrakyan
>Assignee: Ilya Lantukh
> Fix For: 2.0
>
>
> Manual rebalancing with ignite.rebalance().get() immediately returns on 
> second try without requesting rebalancing. The reason is that the future that 
> was created for the first rebalance, is reused for the consecutive attempts. 
> We must have a new future for every rebalance attempt.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1443) CPP: Implement cache continuous queries.

2016-12-01 Thread Igor Sapego (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712751#comment-15712751
 ] 

Igor Sapego commented on IGNITE-1443:
-

Refactored {{HandleRegistry}} and {{SharedPointer}} and used them in code to 
guarantee that ContinuousQuery handle is unique.

> CPP: Implement cache continuous queries.
> 
>
> Key: IGNITE-1443
> URL: https://issues.apache.org/jira/browse/IGNITE-1443
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>  Labels: cpp, important, roadmap
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4355) Eliminate map threads pauses during startup

2016-12-01 Thread Ivan Veselovsky (JIRA)

Ivan Veselovsky created IGNITE-4355:
---

 Summary: Eliminate map threads pauses during startup
 Key: IGNITE-4355
 URL: https://issues.apache.org/jira/browse/IGNITE-4355
 Project: Ignite
  Issue Type: Sub-task
Reporter: Ivan Veselovsky
Assignee: Ivan Veselovsky


Pauses in all Map threads but one are observed in the beginning . This is 
caused by waiting on future.get()  in 
HadoopV2Job.getTaskContext(HadoopTaskInfo) .

{code}
 at sun.misc.Unsafe.park(boolean, long)
 at java.util.concurrent.locks.LockSupport.park(Object)
 at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt()
 at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(int)
 at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(int)
 at org.apache.ignite.internal.util.future.GridFutureAdapter.get0(boolean)
 at org.apache.ignite.internal.util.future.GridFutureAdapter.get()
 at 
org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2Job.getTaskContext(HadoopTaskInfo)
 at 
org.apache.ignite.internal.processors.hadoop.shuffle.HadoopShuffleJob.(Object,
 IgniteLogger, HadoopJob, GridUnsafeMemory, int, int[], int)
 at 
org.apache.ignite.internal.processors.hadoop.shuffle.HadoopShuffle.newJob(HadoopJobId)
 at 
org.apache.ignite.internal.processors.hadoop.shuffle.HadoopShuffle.job(HadoopJobId)
 at 
org.apache.ignite.internal.processors.hadoop.shuffle.HadoopShuffle.output(HadoopTaskContext)
 at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopEmbeddedTaskExecutor$1.createOutput(HadoopTaskContext)
 at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask.createOutputInternal(HadoopTaskContext)
 at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask.runTask(HadoopPerformanceCounter)
 at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask.call0()
 at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask$1.call()
 at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask$1.call()
 at 
org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2TaskContext.runAsJobOwner(Callable)
 at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask.call()
 at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopRunnableTask.call()
 at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopExecutorService$2.body()
 at org.apache.ignite.internal.util.worker.GridWorker.run()
 at java.lang.Thread.run()
{code}

while the working thread initializes the context:
{code}
Java Monitor Wait
 at java.lang.Object.wait(long)
 at java.lang.Thread.join(long)
 at java.lang.Thread.join()
 at org.apache.hadoop.util.Shell.joinThread(Thread)
 at org.apache.hadoop.util.Shell.runCommand()
 at org.apache.hadoop.util.Shell.run()
 at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute()
 at org.apache.hadoop.util.Shell.isSetsidSupported()
 at org.apache.hadoop.util.Shell.()
 at org.apache.hadoop.util.StringUtils.()
 at 
org.apache.hadoop.security.SecurityUtil.getAuthenticationMethod(Configuration)
 at org.apache.hadoop.security.UserGroupInformation.initialize(Configuration, 
boolean)
 at org.apache.hadoop.security.UserGroupInformation.ensureInitialized()
 at 
org.apache.hadoop.security.UserGroupInformation.loginUserFromSubject(Subject)
 at org.apache.hadoop.security.UserGroupInformation.getLoginUser()
 at org.apache.hadoop.security.UserGroupInformation.getCurrentUser()
 at org.apache.hadoop.mapreduce.task.JobContextImpl.(Configuration, JobID)
 at org.apache.hadoop.mapred.JobContextImpl.(JobConf, JobID, Progressable)
 at org.apache.hadoop.mapred.JobContextImpl.(JobConf, JobID)
 at 
org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2TaskContext.(HadoopTaskInfo,
 HadoopJob, HadoopJobId, UUID, DataInput)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Constructor, 
Object[])
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(Object[])
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Object[])
 at java.lang.reflect.Constructor.newInstance(Object[])
 at 
org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2Job.getTaskContext(HadoopTaskInfo)
 at 
org.apache.ignite.internal.processors.hadoop.shuffle.HadoopShuffleJob.(Object,
 IgniteLogger, HadoopJob, GridUnsafeMemory, int, int[], int)
 at 
org.apache.ignite.internal.processors.hadoop.shuffle.HadoopShuffle.newJob(HadoopJobId)
 at 
org.apache.ignite.internal.processors.hadoop.shuffle.HadoopShuffle.job(HadoopJobId)
 at 
org.apache.ignite.internal.processors.hadoop.shuffle.HadoopShuffle.output(HadoopTaskContext)
 at 
org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopEmbeddedTaskExecutor$1.createOutput(HadoopTaskContext)
 at

[jira] [Commented] (IGNITE-4045) .NET: Support DML API

2016-12-01 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712549#comment-15712549
 ] 

ASF GitHub Bot commented on IGNITE-4045:


GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/1309

IGNITE-4045 .NET: Support DML API



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-4045

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1309.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 #1309


commit 23a8b92720ff192143451f1498d40cba57e23a3d
Author: Pavel Tupitsyn 
Date:   2016-11-30T14:33:53Z

QueryField.IsKeyField

commit 4c2d2c835924fa3b0be4328b602376ce5a3cfd2a
Author: Pavel Tupitsyn 
Date:   2016-11-30T14:42:14Z

Update isKey from attributes

commit 4633b0faa87c73998e38d840c5927782abe77c72
Author: Pavel Tupitsyn 
Date:   2016-11-30T15:41:09Z

wip

commit 4e5a97bdb68c7d7afcca78008a9fa58ce782a877
Author: Pavel Tupitsyn 
Date:   2016-11-30T15:44:19Z

Propagate keyFields to Java

commit a25ccaf6a1e3729dd62449dfe2be8ca13778e9fd
Author: Pavel Tupitsyn 
Date:   2016-11-30T15:45:47Z

wip

commit 3ebcd29d204a60ce7696f7c76ebf93f73353b078
Author: Pavel Tupitsyn 
Date:   2016-11-30T15:47:04Z

Propagate keyFields from Java

commit 82c1ff0c45bf9cc30b54fe42c1ca017ffe21ad7a
Author: Pavel Tupitsyn 
Date:   2016-11-30T15:55:49Z

fix read

commit 03e77d927ef1d906bb87d64251709283f1d35458
Author: Pavel Tupitsyn 
Date:   2016-11-30T15:59:34Z

wip

commit 0982aafda6e9e68feb0b15438eca6d6b55f4dfa1
Author: Pavel Tupitsyn 
Date:   2016-11-30T16:02:02Z

XSD schema

commit de5ef0d531fb4b5b1aa7761925e3f206c9d50816
Author: Pavel Tupitsyn 
Date:   2016-11-30T16:07:51Z

Fix non-deterministic XML serialization order

commit f2410ee6789985f8721df08db4b00bb0aed89b36
Author: Pavel Tupitsyn 
Date:   2016-12-01T08:51:56Z

wip

commit a19a9766631054e588fd4c5d966f6ea58426f04d
Author: Pavel Tupitsyn 
Date:   2016-12-01T08:52:34Z

wip

commit 939a6dd62ed869ae3850b587e872cfd621bc9243
Author: Pavel Tupitsyn 
Date:   2016-12-01T08:53:01Z

wip

commit ba75336fd7dbdb6c82f90c8d2342fac9f9e0503e
Author: Pavel Tupitsyn 
Date:   2016-12-01T08:53:48Z

wip

commit 67857f2c8586cdc386025df87587a4238105a7ac
Author: Pavel Tupitsyn 
Date:   2016-12-01T08:55:22Z

Move tests to a separate class

commit 3c0e599619ac16638035fa899b6d23cfe10da26e
Author: Pavel Tupitsyn 
Date:   2016-12-01T09:29:49Z

wip

commit 86a7ef8cf94d8066e0dc4a5d307ca40397ecf64c
Author: Pavel Tupitsyn 
Date:   2016-12-01T09:39:06Z

wip

commit 9e07ad47b677f31a7e5f187cbf08ff23cdf9f72b
Author: Pavel Tupitsyn 
Date:   2016-12-01T09:40:39Z

wip

commit 409c8190a4bf36a5b8a443cbce4bbe7776f3a96e
Author: Pavel Tupitsyn 
Date:   2016-12-01T09:44:40Z

wip

commit 3b7f6bb3adaed05751024a5ddf1c5274b09c11a5
Author: Pavel Tupitsyn 
Date:   2016-12-01T09:50:22Z

wip

commit 031bed2f0aa6e0353bcfb035224382f3f37f2d2d
Author: Pavel Tupitsyn 
Date:   2016-12-01T09:52:07Z

wip

commit 9877456c993e0d5fd1429b2fd65c0dce40f22294
Author: Pavel Tupitsyn 
Date:   2016-12-01T09:58:04Z

wip

commit 66bd614c1b936408411bffa455c0768c9e156766
Author: Pavel Tupitsyn 
Date:   2016-12-01T09:59:20Z

wip

commit c9fc24d3399257e733c53294ed97cce18dcfd1f3
Author: Pavel Tupitsyn 
Date:   2016-12-01T10:02:12Z

cleanup

commit c87dd8fdb394e32aa16ea7be786dad98e2cba6cb
Author: Pavel Tupitsyn 
Date:   2016-12-01T10:09:14Z

Fix config

commit c3e48413dbd6b6400df368d988ea4ab1f0574bab
Author: Pavel Tupitsyn 
Date:   2016-12-01T10:15:42Z

Insert works, but deserialization fails

commit 03e39149ac5516b914ba483e2fdf60a2de74fbb2
Author: Pavel Tupitsyn 
Date:   2016-12-01T10:18:10Z

Deserialization actually works!

commit 986414a11e265f0311531a22cd58d2dd4d614177
Author: Pavel Tupitsyn 
Date:   2016-12-01T10:23:44Z

Tests work!

commit b64e4db4bfed8130c5a704b3115519479fd0bda5
Author: Pavel Tupitsyn 
Date:   2016-12-01T11:18:43Z

TestInvalidCompositeKey done

commit c81732ae4c82f78f4c197e22ca2e783564f6b2b7
Author: Pavel

[jira] [Commented] (IGNITE-4346) DML and PHP PDO: double field is converted to bigdecimal

2016-12-01 Thread Alexander Paschenko (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712380#comment-15712380
 ] 

Alexander Paschenko commented on IGNITE-4346:
-

I assume tomorrow.

> DML and PHP PDO: double field is converted to bigdecimal
> 
>
> Key: IGNITE-4346
> URL: https://issues.apache.org/jira/browse/IGNITE-4346
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Alexander Paschenko
>Priority: Blocker
> Fix For: 1.8
>
> Attachments: default-config.xml, dsn_configuration.png, insert.php, 
> update.php
>
>
> I've set up PHP PDO and ODBC environment according to the following 
> documentation
> https://apacheignite-mix.readme.io/docs/php-pdo
> In particular:
> - The ODBC driver was built from the latest 1.8 sources located in ignite-1.8 
> branch. 
> - The DSN configuration is shown in the attached screenshot name 
> "dsn_configuration"
> - Ignite's cluster configuration is attached as well.
> To reproduce the issue do the following:
> - start a node using attached default-config.xml
> - execute insert.php. There won't be any error.
> - execute update.php and you'll get the error with the stack trace below
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
> DML
>  statement [qry=UPDATE Person SET salary = 42000.0 WHERE salary > 5.0, 
> param
> s=[]]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.execut
> eQuery(GridQueryProcessor.java:1800)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryT
> woStep(GridQueryProcessor.java:810)
> ... 13 more
> Caused by: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException:
>  Failed to execute DML statement [qry=UPDATE Person SET salary = 42000.0 
> WHERE s
> alary > 5.0, params=[]]
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.query
> TwoStep(IgniteH2Indexing.java:1270)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.appl
> yx(GridQueryProcessor.java:812)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.appl
> yx(GridQueryProcessor.java:810)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOu
> tClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.execut
> eQuery(GridQueryProcessor.java:1777)
> ... 14 more
> Caused by: class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicChecke
> dException: Failed to locally write to cache (all transaction entries will be 
> in
> validated, however there was a window when entries for this transaction were 
> vis
> ible to others): GridNearTxLocal [mappings=IgniteTxMappingsSingleImpl 
> [mapping=G
> ridDistributedTxMapping [entries=[IgniteTxEntry [key=KeyCacheObjectImpl 
> [val=777
> , hasValBytes=false], cacheId=1215863053, partId=-1, txKey=IgniteTxKey 
> [key=KeyC
> acheObjectImpl [val=777, hasValBytes=false], cacheId=1215863053], 
> val=[op=TRANSF
> ORM, val=null], prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryPr
> ocessorsCol=[IgniteBiTuple 
> [val1=org.apache.ignite.internal.processors.query.h2.
> DmlStatementsProcessor$ModifyingEntryProcessor@1f2f10da, 
> val2=[Ljava.lang.Object
> ;@2bfa5294]], ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null,
>  dhtVer=GridCacheVersion [topVer=92027384, time=1480547401695, 
> order=14805473813
> 93, nodeOrder=1], filters=[], filtersPassed=false, filtersSet=true, 
> entry=GridDh
> tColocatedCacheEntry [super=GridDhtCacheEntry [rdrs=[], 
> locPart=GridDhtLocalPart
> ition [id=777, 
> map=org.apache.ignite.internal.processors.cache.GridCacheConcurre
> ntMapImpl@24c94530, rmvQueue=GridCircularBuffer [sizeMask=255, idxGen=0], 
> cntr=1
> , shouldBeRenting=false, state=OWNING, reservations=0, empty=false, 
> createTime=1
> 1/30/2016 15:09:45], super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [k
> ey=KeyCacheObjectImpl [val=777, hasValBytes=false], val=Person 
> [idHash=659295625
> , hash=-322179972, resume=Secret Service agent, firstName=James, 
> lastName=Bond,
> salary=65000.0], startVer=1480547381389, ver=GridCacheVersion 
> [topVer=92027384,
> time=1480547394518, order=1480547381390, nodeOrder=1], hash=777, 
> extras=GridCach
> eMvccEntryExtras [mvcc=GridCacheMvcc [locs=[GridCacheMvccCandidate 
> [nodeId=08b20
> b4b-3ca6-4c05-aa9d-4219cbc3f3f5, ver=GridCacheVersion [topVer=92027384, 
> time=148
> 0547401693, order=1480547381392, nodeOrder=1], timeout=0, ts=1480547401693, 
> thre
> adId=57, id=3, topVer=AffinityTopologyVersion [topVer=1, minorTopVer=0], 
> reentry
> =null, otherNodeId=08b20b4b-3ca6-4c05-aa9d-4219cbc3f3f5, 
>

[jira] [Assigned] (IGNITE-4353) Parent Cassandra module deployed on maven repository

2016-12-01 Thread Sergey Kozlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Kozlov reassigned IGNITE-4353:
-

Assignee: Sergey Kozlov  (was: Anton Vinogradov)

> Parent Cassandra module deployed on maven repository
> 
>
> Key: IGNITE-4353
> URL: https://issues.apache.org/jira/browse/IGNITE-4353
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
> Fix For: 1.8
>
>
> {{ignite-cassandra}} module deployed on maven repository though has no binary 
> artifacts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-4353) Parent Cassandra module deployed on maven repository

2016-12-01 Thread Sergey Kozlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Kozlov closed IGNITE-4353.
-

Fixed

> Parent Cassandra module deployed on maven repository
> 
>
> Key: IGNITE-4353
> URL: https://issues.apache.org/jira/browse/IGNITE-4353
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
> Fix For: 1.8
>
>
> {{ignite-cassandra}} module deployed on maven repository though has no binary 
> artifacts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-4346) DML and PHP PDO: double field is converted to bigdecimal

2016-12-01 Thread Alexander Paschenko (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711133#comment-15711133
 ] 

Alexander Paschenko edited comment on IGNITE-4346 at 12/1/16 3:29 PM:
--

Allora, signori, rilassatevi per favore: I'm sure this is fixed by IGNITE-4340. 
Igor, please try to reproduce everything described by Denis on branch 
ignite-4340.


was (Author: al.psc):
Allora, signori, rilassatevi per favore: I'm sure this is fixed by IGNITE-4340. 
Igor, please try to reproduce everything described by Denis on branch 
ignite-4340 (prof. repo of course).

> DML and PHP PDO: double field is converted to bigdecimal
> 
>
> Key: IGNITE-4346
> URL: https://issues.apache.org/jira/browse/IGNITE-4346
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Alexander Paschenko
>Priority: Blocker
> Fix For: 1.8
>
> Attachments: default-config.xml, dsn_configuration.png, insert.php, 
> update.php
>
>
> I've set up PHP PDO and ODBC environment according to the following 
> documentation
> https://apacheignite-mix.readme.io/docs/php-pdo
> In particular:
> - The ODBC driver was built from the latest 1.8 sources located in ignite-1.8 
> branch. 
> - The DSN configuration is shown in the attached screenshot name 
> "dsn_configuration"
> - Ignite's cluster configuration is attached as well.
> To reproduce the issue do the following:
> - start a node using attached default-config.xml
> - execute insert.php. There won't be any error.
> - execute update.php and you'll get the error with the stack trace below
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
> DML
>  statement [qry=UPDATE Person SET salary = 42000.0 WHERE salary > 5.0, 
> param
> s=[]]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.execut
> eQuery(GridQueryProcessor.java:1800)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryT
> woStep(GridQueryProcessor.java:810)
> ... 13 more
> Caused by: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException:
>  Failed to execute DML statement [qry=UPDATE Person SET salary = 42000.0 
> WHERE s
> alary > 5.0, params=[]]
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.query
> TwoStep(IgniteH2Indexing.java:1270)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.appl
> yx(GridQueryProcessor.java:812)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.appl
> yx(GridQueryProcessor.java:810)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOu
> tClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.execut
> eQuery(GridQueryProcessor.java:1777)
> ... 14 more
> Caused by: class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicChecke
> dException: Failed to locally write to cache (all transaction entries will be 
> in
> validated, however there was a window when entries for this transaction were 
> vis
> ible to others): GridNearTxLocal [mappings=IgniteTxMappingsSingleImpl 
> [mapping=G
> ridDistributedTxMapping [entries=[IgniteTxEntry [key=KeyCacheObjectImpl 
> [val=777
> , hasValBytes=false], cacheId=1215863053, partId=-1, txKey=IgniteTxKey 
> [key=KeyC
> acheObjectImpl [val=777, hasValBytes=false], cacheId=1215863053], 
> val=[op=TRANSF
> ORM, val=null], prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryPr
> ocessorsCol=[IgniteBiTuple 
> [val1=org.apache.ignite.internal.processors.query.h2.
> DmlStatementsProcessor$ModifyingEntryProcessor@1f2f10da, 
> val2=[Ljava.lang.Object
> ;@2bfa5294]], ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null,
>  dhtVer=GridCacheVersion [topVer=92027384, time=1480547401695, 
> order=14805473813
> 93, nodeOrder=1], filters=[], filtersPassed=false, filtersSet=true, 
> entry=GridDh
> tColocatedCacheEntry [super=GridDhtCacheEntry [rdrs=[], 
> locPart=GridDhtLocalPart
> ition [id=777, 
> map=org.apache.ignite.internal.processors.cache.GridCacheConcurre
> ntMapImpl@24c94530, rmvQueue=GridCircularBuffer [sizeMask=255, idxGen=0], 
> cntr=1
> , shouldBeRenting=false, state=OWNING, reservations=0, empty=false, 
> createTime=1
> 1/30/2016 15:09:45], super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [k
> ey=KeyCacheObjectImpl [val=777, hasValBytes=false], val=Person 
> [idHash=659295625
> , hash=-322179972, resume=Secret Service agent, firstName=James, 
> lastName=Bond,
> salary=65000.0], startVer=1480547381389, ver=GridCacheVersion 
> [topVer=92027384,
> time=1480547394518, order=1480547381390, nodeOrder=1], hash=777, 
> extras=GridCach
> eMvccEntryExtras

[jira] [Updated] (IGNITE-4354) DML: BinaryObjectBuilder does not sort fields in some cases

2016-12-01 Thread Pavel Tupitsyn (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-4354:
---
Fix Version/s: (was: 1.8)
   2.0

> DML: BinaryObjectBuilder does not sort fields in some cases
> ---
>
> Key: IGNITE-4354
> URL: https://issues.apache.org/jira/browse/IGNITE-4354
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>  Labels: DML
> Fix For: 2.0
>
>
> One of the setField methods uses TreeMap<> to sort fields, depending on 
> BinaryUtils.FIELDS_SORTED_ORDER.
> However, there are other places where assignedVals is initialized (setField, 
> removeField) which are not updated to use TreeMap.
> Make sure to put this logic in one place.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4354) DML: BinaryObjectBuilder does not sort fields in some cases

2016-12-01 Thread Pavel Tupitsyn (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-4354:
---
Priority: Critical  (was: Major)

> DML: BinaryObjectBuilder does not sort fields in some cases
> ---
>
> Key: IGNITE-4354
> URL: https://issues.apache.org/jira/browse/IGNITE-4354
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Priority: Critical
>  Labels: DML
> Fix For: 2.0
>
>
> One of the setField methods uses TreeMap<> to sort fields, depending on 
> BinaryUtils.FIELDS_SORTED_ORDER.
> However, there are other places where assignedVals is initialized (setField, 
> removeField) which are not updated to use TreeMap.
> Make sure to put this logic in one place.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4345) incorrect/outdated info on site

2016-12-01 Thread Denis Magda (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712235#comment-15712235
 ] 

Denis Magda commented on IGNITE-4345:
-

In addition, please provide the latest valid links for Docker and Cloud images 
so that I can update them on the site
https://ignite.apache.org/download.cgi#docker

> incorrect/outdated info on site
> ---
>
> Key: IGNITE-4345
> URL: https://issues.apache.org/jira/browse/IGNITE-4345
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Reporter: Sergey Korzhevsky
>Assignee: Nikolay Tikhonov
>Priority: Critical
> Fix For: 1.8
>
>
> Old/icorrect info on the site.
> 1) http://ignite.apache.org/download.cgi#docker
>a) "guide" link points to 1.5 version
>b) "docker repository" is a broken link, should be 
> https://hub.docker.com/u/apacheignite/
> i guess.
> 2) https://apacheignite.readme.io/v1.7/docs/docker-deployment
> IGNITE_CONFIG "example url"'s file (https://raw.githubusercontent.com/
> bob/master/ignite-cfg.xml) does not exists.
> I think, it may be pointed to the some file in the current github repo. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4354) DML: BinaryObjectBuilder does not sort fields in some cases

2016-12-01 Thread Pavel Tupitsyn (JIRA)

Pavel Tupitsyn created IGNITE-4354:
--

 Summary: DML: BinaryObjectBuilder does not sort fields in some 
cases
 Key: IGNITE-4354
 URL: https://issues.apache.org/jira/browse/IGNITE-4354
 Project: Ignite
  Issue Type: Bug
  Components: SQL
Affects Versions: 1.8
Reporter: Pavel Tupitsyn
 Fix For: 1.8


One of the setField methods uses TreeMap<> to sort fields, depending on 
BinaryUtils.FIELDS_SORTED_ORDER.

However, there are other places where assignedVals is initialized (setField, 
removeField) which are not updated to use TreeMap.

Make sure to put this logic in one place.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4345) incorrect/outdated info on site

2016-12-01 Thread Denis Magda (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712229#comment-15712229
 ] 

Denis Magda commented on IGNITE-4345:
-

[~ntikhonov],

The documentation is still hard coded to specific versions. For instance, I see 
the following in the shell commands.

{code}
# Pull ignite version 1.7.0
sudo docker pull apacheignite/ignite:1.7.0
{code}

{code}
# Run ignite version 1.4.0
sudo docker run -it --net=host 
-e "CONFIG_URI=$CONFIG_URI" 
[-e "OPTION_LIBS=$OPTION_LIBS"]
[-e "JVM_OPTS=$JVM_OPTS"]
...
apacheignite/ignite:1.4.0 
{code}

Let's use something like {ignite-version} instead of 1.4.0 or 1.7.0 to avoid 
documentation updates every time a new version gets released.

Next, as for AWS and GCE, I would move it to its own documentation pages and 
clean on out outdated reference to the images. As an example, GCE section 
refers to this old image 
(https://storage.googleapis.com/ignite-media/ignite-google-image-1.0.0.tar.gz) 
which even doesn't exist any longer.

I would modify both AWS and GCE in such a way when there is no need to paste 
the links to images but rather would provide instruction on how to look for a 
gridgain image on a cloud environment using its internal search capabilities.

> incorrect/outdated info on site
> ---
>
> Key: IGNITE-4345
> URL: https://issues.apache.org/jira/browse/IGNITE-4345
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Reporter: Sergey Korzhevsky
>Assignee: Nikolay Tikhonov
>Priority: Critical
> Fix For: 1.8
>
>
> Old/icorrect info on the site.
> 1) http://ignite.apache.org/download.cgi#docker
>a) "guide" link points to 1.5 version
>b) "docker repository" is a broken link, should be 
> https://hub.docker.com/u/apacheignite/
> i guess.
> 2) https://apacheignite.readme.io/v1.7/docs/docker-deployment
> IGNITE_CONFIG "example url"'s file (https://raw.githubusercontent.com/
> bob/master/ignite-cfg.xml) does not exists.
> I think, it may be pointed to the some file in the current github repo. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4346) DML and PHP PDO: double field is converted to bigdecimal

2016-12-01 Thread Denis Magda (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712204#comment-15712204
 ] 

Denis Magda commented on IGNITE-4346:
-

When IGNITE-4340 is expected to be merged in 1.8 branch?

> DML and PHP PDO: double field is converted to bigdecimal
> 
>
> Key: IGNITE-4346
> URL: https://issues.apache.org/jira/browse/IGNITE-4346
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Alexander Paschenko
>Priority: Blocker
> Fix For: 1.8
>
> Attachments: default-config.xml, dsn_configuration.png, insert.php, 
> update.php
>
>
> I've set up PHP PDO and ODBC environment according to the following 
> documentation
> https://apacheignite-mix.readme.io/docs/php-pdo
> In particular:
> - The ODBC driver was built from the latest 1.8 sources located in ignite-1.8 
> branch. 
> - The DSN configuration is shown in the attached screenshot name 
> "dsn_configuration"
> - Ignite's cluster configuration is attached as well.
> To reproduce the issue do the following:
> - start a node using attached default-config.xml
> - execute insert.php. There won't be any error.
> - execute update.php and you'll get the error with the stack trace below
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
> DML
>  statement [qry=UPDATE Person SET salary = 42000.0 WHERE salary > 5.0, 
> param
> s=[]]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.execut
> eQuery(GridQueryProcessor.java:1800)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryT
> woStep(GridQueryProcessor.java:810)
> ... 13 more
> Caused by: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException:
>  Failed to execute DML statement [qry=UPDATE Person SET salary = 42000.0 
> WHERE s
> alary > 5.0, params=[]]
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.query
> TwoStep(IgniteH2Indexing.java:1270)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.appl
> yx(GridQueryProcessor.java:812)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.appl
> yx(GridQueryProcessor.java:810)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOu
> tClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.execut
> eQuery(GridQueryProcessor.java:1777)
> ... 14 more
> Caused by: class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicChecke
> dException: Failed to locally write to cache (all transaction entries will be 
> in
> validated, however there was a window when entries for this transaction were 
> vis
> ible to others): GridNearTxLocal [mappings=IgniteTxMappingsSingleImpl 
> [mapping=G
> ridDistributedTxMapping [entries=[IgniteTxEntry [key=KeyCacheObjectImpl 
> [val=777
> , hasValBytes=false], cacheId=1215863053, partId=-1, txKey=IgniteTxKey 
> [key=KeyC
> acheObjectImpl [val=777, hasValBytes=false], cacheId=1215863053], 
> val=[op=TRANSF
> ORM, val=null], prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryPr
> ocessorsCol=[IgniteBiTuple 
> [val1=org.apache.ignite.internal.processors.query.h2.
> DmlStatementsProcessor$ModifyingEntryProcessor@1f2f10da, 
> val2=[Ljava.lang.Object
> ;@2bfa5294]], ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null,
>  dhtVer=GridCacheVersion [topVer=92027384, time=1480547401695, 
> order=14805473813
> 93, nodeOrder=1], filters=[], filtersPassed=false, filtersSet=true, 
> entry=GridDh
> tColocatedCacheEntry [super=GridDhtCacheEntry [rdrs=[], 
> locPart=GridDhtLocalPart
> ition [id=777, 
> map=org.apache.ignite.internal.processors.cache.GridCacheConcurre
> ntMapImpl@24c94530, rmvQueue=GridCircularBuffer [sizeMask=255, idxGen=0], 
> cntr=1
> , shouldBeRenting=false, state=OWNING, reservations=0, empty=false, 
> createTime=1
> 1/30/2016 15:09:45], super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [k
> ey=KeyCacheObjectImpl [val=777, hasValBytes=false], val=Person 
> [idHash=659295625
> , hash=-322179972, resume=Secret Service agent, firstName=James, 
> lastName=Bond,
> salary=65000.0], startVer=1480547381389, ver=GridCacheVersion 
> [topVer=92027384,
> time=1480547394518, order=1480547381390, nodeOrder=1], hash=777, 
> extras=GridCach
> eMvccEntryExtras [mvcc=GridCacheMvcc [locs=[GridCacheMvccCandidate 
> [nodeId=08b20
> b4b-3ca6-4c05-aa9d-4219cbc3f3f5, ver=GridCacheVersion [topVer=92027384, 
> time=148
> 0547401693, order=1480547381392, nodeOrder=1], timeout=0, ts=1480547401693, 
> thre
> adId=57, id=3, topVer=AffinityTopologyVersion [topVer=1, minorTopVer=0], 
> reentry
> =null, otherNodeId=08b20b4b-3ca6-4c05-aa9d-4219cbc3f3f5,

[jira] [Commented] (IGNITE-4167) Add an option to avoid printing out sensitive data into logs

2016-12-01 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712139#comment-15712139
 ] 

ASF GitHub Bot commented on IGNITE-4167:


GitHub user akuramshingg opened a pull request:

https://github.com/apache/ignite/pull/1308

IGNITE-4167



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4167

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1308.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 #1308


commit 38d1d0491ab9e6858a58b90d0e5d892d9fc0e284
Author: Igor Sapego 
Date:   2016-09-26T08:04:56Z

IGNITE-3876: ODBC: Better handling of NULL values for output parameters. 
This closes #1099.

commit 548fe6a3fe4d38caebe3b45366f3e812b035d006
Author: tledkov-gridgain 
Date:   2016-09-26T09:05:07Z

IGNITE-: IGFS: Now it is possible to use ATOMIC cache for data blocks 
when fragmentizer it disabled. This closes #1108.

commit 8032fc2c8a7cf9f404eb75c65164bb2900aab79d
Author: vozerov-gridgain 
Date:   2016-09-26T09:31:30Z

IGNITE-3912: Hadoop: Implemented new class loading architecture for 
embedded execution mode.

commit 33a6878eccd60f86648067901613b713ef3bb71f
Author: Pavel Tupitsyn 
Date:   2016-09-26T11:56:51Z

IGNITE-3491 .NET: Allow type name without assembly for type properties in 
app.config

commit 4f9ac81c5d88f333d9aec78cc480230c48fd88f2
Author: Pavel Tupitsyn 
Date:   2016-09-26T12:06:34Z

Merge remote-tracking branch 'remotes/community/ignite-1.6.9' into 
ignite-1.7.2

commit a4a933eb708dadb6b67f6c062db32ffeef819184
Author: Igor Sapego 
Date:   2016-09-26T14:41:57Z

IGNITE-3883: ODBC: Implemented data-at-execution dialog. This closes #1073.

commit 350e84656686eb81f8e12d569783db9914ca5a37
Author: Pavel Tupitsyn 
Date:   2016-09-26T16:55:27Z

IGNITE-3956 .NET: Fix cache creation in LINQPad examples
This closes #1116

commit bbc97580492609e2e4fc3d92b08b4740b984d78f
Author: isapego 
Date:   2016-09-26T17:17:43Z

Merge branch 'ignite-1.6.9' into ignite-1.7.2

commit 6a41dc92da124a921b304392e922886c30597037
Author: Saikat Maitra 
Date:   2016-09-26T22:28:51Z

IGNITE-3807 IgniteSpiContext registers message listeners incorrectly

commit 5ff9e5e8c95ea0fe37d281a7ff46e148469f952a
Author: Saikat Maitra 
Date:   2016-09-26T22:28:51Z

IGNITE-3807 IgniteSpiContext registers message listeners incorrectly

commit 97bfee4dff807e3049b61fa473472a8395cdcb6a
Author: vozerov-gridgain 
Date:   2016-09-27T07:06:48Z

Fixing RAT.

commit 0dac458d2aa36b03986412726bd607877e53aa4f
Author: vozerov-gridgain 
Date:   2016-09-27T07:07:03Z

Merge remote-tracking branch 'upstream/ignite-1.6.9' into ignite-1.6.9

commit 68b0bcd83c295ce540aa9d9d0910abcf671671df
Author: Pavel Tupitsyn 
Date:   2016-09-27T09:08:46Z

IGNITE-3970 .NET: Fix Cyrillic 'C' letters in code

commit 41df266a232afd86ade91c5e18f082206913007c
Author: Pavel Tupitsyn 
Date:   2016-09-27T09:14:01Z

Merge remote-tracking branch 'remotes/community/ignite-1.6.9' into 
ignite-1.7.2

commit 48d4a9252536dd82811a10327b2df6ddbd1ff13a
Author: Alexey Kuznetsov 
Date:   2016-09-27T10:03:36Z

Web console beta-4.

commit 29acb33293c3d3130e16b7ff4d6b7ae260b7b78b
Author: Alexey Kuznetsov 
Date:   2016-09-27T10:15:38Z

Fixed typos.

commit 3f62596ec33026fb6104f7ed33979a0df46c5789
Author: Alexey Kuznetsov 
Date:   2016-09-27T10:19:00Z

Merge ignite-1.6.9 into ignite-1.7.2.

commit c2a3f11ca14cf9f9cf5bd2d6e2a87764f7cda5a7
Author: Andrey Martianov 
Date:   2016-09-20T14:41:49Z

ignite-3621 Use single ttl cleanup worker thread for all caches

(cherry picked from commit 1bc6058)

commit 39fc5477c19cbe2b2116aaf575a2d0a9c9a618b1
Author: tledkov-gridgain 
Date:   2016-09-27T11:48:18Z

IGNITE-3639: IGFS: Removed BufferedOutputStream from 
LocalIgfsSecondaryFileSystem because it doesn't give any performance benefit.

commit 5cffd3c3d6cb006e3745c314d6f85a066e6a0f06
Author: vozerov-gridgain 
Date:   2016-09-27T12:13:21Z

IGNITE-3661: First attempt to move ignored and flaky tests into a single 
suite. Applied to web-session module.

commit c8dc92ecc8a5d76e68d2d75f12158e0a581a0326
Author: sboikov 
Date:   2016-09-27T12:17:05Z

ignite-3973 In

[jira] [Resolved] (IGNITE-4353) Parent Cassandra module deployed on maven repository

2016-12-01 Thread Anton Vinogradov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov resolved IGNITE-4353.
--
Resolution: Fixed
  Assignee: Anton Vinogradov

> Parent Cassandra module deployed on maven repository
> 
>
> Key: IGNITE-4353
> URL: https://issues.apache.org/jira/browse/IGNITE-4353
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Anton Vinogradov
> Fix For: 1.8
>
>
> {{ignite-cassandra}} module deployed on maven repository though has no binary 
> artifacts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-4344) Client node allocates off heap memories for caches

2016-12-01 Thread Semen Boikov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov resolved IGNITE-4344.
--
Resolution: Fixed

Fixed to do not create offheap map on non-affinity nodes.

> Client node allocates off heap memories for caches
> --
>
> Key: IGNITE-4344
> URL: https://issues.apache.org/jira/browse/IGNITE-4344
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6, 1.7
>Reporter: Nikolay Tikhonov
>Assignee: Semen Boikov
> Fix For: 1.9
>
> Attachments: OffHeapClientTest.patch
>
>
> Client node should not allocate memories. Test attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4344) Client node allocates off heap memories for caches

2016-12-01 Thread Semen Boikov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov updated IGNITE-4344:
-
Assignee: (was: Semen Boikov)

> Client node allocates off heap memories for caches
> --
>
> Key: IGNITE-4344
> URL: https://issues.apache.org/jira/browse/IGNITE-4344
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6, 1.7
>Reporter: Nikolay Tikhonov
> Fix For: 1.9
>
> Attachments: OffHeapClientTest.patch
>
>
> Client node should not allocate memories. Test attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4345) incorrect/outdated info on site

2016-12-01 Thread Nikolay Tikhonov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712114#comment-15712114
 ] 

Nikolay Tikhonov commented on IGNITE-4345:
--

Yes. The documentation has been obsolete for version 1.7. I've updated, please 
look at it.

[~dmagda]
1) No, this parameter not needed.
2) AWS and GCE deployments based on docker and they start docker container. All 
parameters desribed for docker deployment also apply to AWS and GCE. But we can 
create for them separate pages. Do you think that this more appropriate?

> incorrect/outdated info on site
> ---
>
> Key: IGNITE-4345
> URL: https://issues.apache.org/jira/browse/IGNITE-4345
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Reporter: Sergey Korzhevsky
>Assignee: Nikolay Tikhonov
>Priority: Critical
> Fix For: 1.8
>
>
> Old/icorrect info on the site.
> 1) http://ignite.apache.org/download.cgi#docker
>a) "guide" link points to 1.5 version
>b) "docker repository" is a broken link, should be 
> https://hub.docker.com/u/apacheignite/
> i guess.
> 2) https://apacheignite.readme.io/v1.7/docs/docker-deployment
> IGNITE_CONFIG "example url"'s file (https://raw.githubusercontent.com/
> bob/master/ignite-cfg.xml) does not exists.
> I think, it may be pointed to the some file in the current github repo. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4353) Parent Cassandra module deployed on maven repository

2016-12-01 Thread Sergey Kozlov (JIRA)

Sergey Kozlov created IGNITE-4353:
-

 Summary: Parent Cassandra module deployed on maven repository
 Key: IGNITE-4353
 URL: https://issues.apache.org/jira/browse/IGNITE-4353
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 1.8


{{ignite-cassandra}} module deployed on maven repository though has no binary 
artifacts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4352) Update failed tests

2016-12-01 Thread Semen Boikov (JIRA)

Semen Boikov created IGNITE-4352:


 Summary: Update failed tests 
 Key: IGNITE-4352
 URL: https://issues.apache.org/jira/browse/IGNITE-4352
 Project: Ignite
  Issue Type: Task
  Components: general
Reporter: Denis Kholodov






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4111) Communication fails to send message if target node did not finish join process

2016-12-01 Thread Alexandr Kuramshin (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711951#comment-15711951
 ] 

Alexandr Kuramshin commented on IGNITE-4111:


https://github.com/apache/ignite/pull/1307

> Communication fails to send message if target node did not finish join process
> --
>
> Key: IGNITE-4111
> URL: https://issues.apache.org/jira/browse/IGNITE-4111
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Semen Boikov
>Assignee: Semen Boikov
> Fix For: 2.0
>
> Attachments: test onFirstMessage hang.log
>
>
> Currently this scenario is possible:
> - joining node sent join request and waits for 
> TcpDiscoveryNodeAddFinishedMessage inside ServerImpl.joinTopology
> - others nodes already see this node and can send messages to it (for example 
> try to run compute job on this node)
> - joining node can not receive message: TcpCommunicationSpi will hang inside 
> 'onFirstMessage' on 'getSpiContext' call, so sending node will get error 
> trying to establish connection
> Possible fix: if in onFirstMessage() spi context is not available, then 
> TcpCommunicationSpi  should send special response which indicates that this 
> node is not ready yet, and sender should retry after some time.
> Also need check internal code for places where message can be unnecessarily 
> sent to node: one such place is 
> GridCachePartitionExchangeManager.refreshPartitions - message is sent to all 
> known nodes, but here we can filter by node order / finished exchage version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4111) Communication fails to send message if target node did not finish join process

2016-12-01 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711949#comment-15711949
 ] 

ASF GitHub Bot commented on IGNITE-4111:


GitHub user akuramshingg opened a pull request:

https://github.com/apache/ignite/pull/1307

IGNITE-4111



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4111

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1307.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 #1307






> Communication fails to send message if target node did not finish join process
> --
>
> Key: IGNITE-4111
> URL: https://issues.apache.org/jira/browse/IGNITE-4111
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Semen Boikov
>Assignee: Semen Boikov
> Fix For: 2.0
>
> Attachments: test onFirstMessage hang.log
>
>
> Currently this scenario is possible:
> - joining node sent join request and waits for 
> TcpDiscoveryNodeAddFinishedMessage inside ServerImpl.joinTopology
> - others nodes already see this node and can send messages to it (for example 
> try to run compute job on this node)
> - joining node can not receive message: TcpCommunicationSpi will hang inside 
> 'onFirstMessage' on 'getSpiContext' call, so sending node will get error 
> trying to establish connection
> Possible fix: if in onFirstMessage() spi context is not available, then 
> TcpCommunicationSpi  should send special response which indicates that this 
> node is not ready yet, and sender should retry after some time.
> Also need check internal code for places where message can be unnecessarily 
> sent to node: one such place is 
> GridCachePartitionExchangeManager.refreshPartitions - message is sent to all 
> known nodes, but here we can filter by node order / finished exchage version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4336) Manual rebalance can't be requested twice

2016-12-01 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711877#comment-15711877
 ] 

ASF GitHub Bot commented on IGNITE-4336:


GitHub user ilantukh opened a pull request:

https://github.com/apache/ignite/pull/1306

IGNITE-4336 : Fixed rebalance future.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ilantukh/ignite ignite-4336

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1306.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 #1306


commit 20a1cfaf0d400a57f3a281bf8a4af1801a12243c
Author: Ilya Lantukh 
Date:   2016-12-01T12:44:39Z

ignite-4336 : Fixed rebalance future.




> Manual rebalance can't be requested twice
> -
>
> Key: IGNITE-4336
> URL: https://issues.apache.org/jira/browse/IGNITE-4336
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Dmitriy Setrakyan
>Assignee: Ilya Lantukh
> Fix For: 2.0
>
>
> Manual rebalancing with ignite.rebalance().get() immediately returns on 
> second try without requesting rebalancing. The reason is that the future that 
> was created for the first rebalance, is reused for the consecutive attempts. 
> We must have a new future for every rebalance attempt.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4351) .NET: Use BinaryArrayIdentityResolver by default

2016-12-01 Thread Pavel Tupitsyn (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-4351:
---
Labels: .NET breaking-api  (was: .NET Breaking-Change)

> .NET: Use BinaryArrayIdentityResolver by default
> 
>
> Key: IGNITE-4351
> URL: https://issues.apache.org/jira/browse/IGNITE-4351
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>  Labels: .NET, breaking-api
> Fix For: 2.0
>
>
> Current legacy behavior calculates hash codes by calling 
> Object.GetHashCode(), but equality comparison is performed by comparing byte 
> arrays in binary form, which is inconsistent and can lead to unexpected 
> behavior with user-defined keys.
> In 2.0 we should replace default behavior with ArrayResolver so that Equals 
> and GetHashCode are consistent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4351) .NET: Use BinaryArrayIdentityResolver by default

2016-12-01 Thread Pavel Tupitsyn (JIRA)

Pavel Tupitsyn created IGNITE-4351:
--

 Summary: .NET: Use BinaryArrayIdentityResolver by default
 Key: IGNITE-4351
 URL: https://issues.apache.org/jira/browse/IGNITE-4351
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
 Fix For: 2.0


Current legacy behavior calculates hash codes by calling Object.GetHashCode(), 
but equality comparison is performed by comparing byte arrays in binary form, 
which is inconsistent and can lead to unexpected behavior with user-defined 
keys.

In 2.0 we should replace default behavior with ArrayResolver so that Equals and 
GetHashCode are consistent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-4045) .NET: Support DML API

2016-12-01 Thread Pavel Tupitsyn (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711741#comment-15711741
 ] 

Pavel Tupitsyn edited comment on IGNITE-4045 at 12/1/16 12:24 PM:
--

Another thing to be ported to .NET is BinaryIdentityResolver interface 
(BinaryTypeConfiguration.BinaryIdentityResolver).

For now we should provide mapping to two default implementations: 
BinaryArrayIdentityResolver, BinaryFieldIdentityResolver


was (Author: ptupitsyn):
Another thing to be ported to .NET is BinaryIdentityResolver interface 
(BinaryTypeConfiguration.BinaryIdentityResolver).

> .NET: Support DML API
> -
>
> Key: IGNITE-4045
> URL: https://issues.apache.org/jira/browse/IGNITE-4045
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
>  Labels: roadmap
> Fix For: 2.0
>
>
> Ignite's Java component will provide support for DML soon (IGNITE-2294). At 
> she same time DML will be supported at the level of ODBC and JDBC drivers.
> As the next step we should include the similar functionality into Ignite.NET 
> by doing the following:
> - Implement DML API;
> - Enhance {{QueryExample.cs}} by doing INSERTs instead of cache.puts and 
> adding UPDATE and DELETE operation examples.
> - Add documentation to Ignite.NET readme.io covering the feature. Most like 
> most of the content can be take from the general documentation when this 
> ticket IGNITE-4018 is ready 
> (https://apacheignite.readme.io/docs/distributed-dml).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4140) KafkaStreamer should use tuple extractor instead of decoders

2016-12-01 Thread Anton Vinogradov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711788#comment-15711788
 ] 

Anton Vinogradov commented on IGNITE-4140:
--

1) [~vkulichenko], what do you think? 
Seems, we just need to replace old streamed with new one?

2) http://reviews.ignite.apache.org/ignite/view
Brief instructions:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ReviewWithUpsource


> KafkaStreamer should use tuple extractor instead of decoders
> 
>
> Key: IGNITE-4140
> URL: https://issues.apache.org/jira/browse/IGNITE-4140
> Project: Ignite
>  Issue Type: Improvement
>  Components: streaming
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Anil
>  Labels: patch-available
> Fix For: 2.0
>
>
> Current design of {{KafkaStreamer}} looks incorrect to me. In particular, it 
> extends {{StreamAdapter}}, but ignores tuple extractors provided there and 
> uses native Kafka decoders instead. This for example makes impossible to 
> produce several entries from one message, like it can be done via 
> {{StreamMultipleTupleExtractor}} in other streamers.
> To fix this, we should:
> # Declare the {{KafkaStreamer}} like this:
> {code}
> KafkaStreamer extends StreamAdapter, 
> K, V>
> {code}
> # Remove {{keyDecoder}} and {{valDecoder}} in favor of tuple extractors.
> # Instead of doing {{getStreamer().addData(...)}} directly, call 
> {{addMessage(...)}} method providing the raw message consumed from Kafka 
> ({{MessageAndMetadata}}). This method will make sure that 
> configured extractor is invoked and that all entries are added to 
> {{IgniteDataStreamer}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4347) ODBC: NPE when cache name is different from the one configured in DSN

2016-12-01 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711783#comment-15711783
 ] 

ASF GitHub Bot commented on IGNITE-4347:


GitHub user isapego opened a pull request:

https://github.com/apache/ignite/pull/1305

IGNITE-4347: Fixed NPE.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/isapego/ignite ignite-4347

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1305.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 #1305


commit 6633904bc28b8d47b16588b1a3dff84922c21efb
Author: Igor Sapego 
Date:   2016-12-01T11:55:42Z

IGNITE-4347: Fixed NPE.




> ODBC: NPE when cache name is different from the one configured in DSN
> -
>
> Key: IGNITE-4347
> URL: https://issues.apache.org/jira/browse/IGNITE-4347
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Reporter: Denis Magda
>Assignee: Igor Sapego
>Priority: Critical
> Fix For: 1.8
>
> Attachments: exception.png
>
>
> The following query was executed from PHP PDO side
> {code}
> $dbs = $dbh->prepare('INSERT INTO Person (_key, firstName, lastName, resume, 
> salary) 
> VALUES (?, ?, ?, ?, ?)');
> {code}
> The cache name in Spring XML configuration was "Person" while the DSN was 
> configured to use "PersonCache" as a default cache name.
> As a result, I was getting NPE shown in the attached screenshot. Only after I 
> sorted out the root cause of the NPE referring to the source code I could 
> finally fix the issue.
> Let's provide more meaningful explanation rather than throwing NPE saying 
> something like "The cache named {cache_name} has not been found. Make sure 
> that ODBC connection string or DSN is configured properly."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4346) DML and PHP PDO: double field is converted to bigdecimal

2016-12-01 Thread Alexander Paschenko (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711755#comment-15711755
 ] 

Alexander Paschenko commented on IGNITE-4346:
-

Just as expected. Thanks Igor. [~dmagda] I suggest that we close this as a 
duplicate to IGNITE-4340.

> DML and PHP PDO: double field is converted to bigdecimal
> 
>
> Key: IGNITE-4346
> URL: https://issues.apache.org/jira/browse/IGNITE-4346
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Alexander Paschenko
>Priority: Blocker
> Fix For: 1.8
>
> Attachments: default-config.xml, dsn_configuration.png, insert.php, 
> update.php
>
>
> I've set up PHP PDO and ODBC environment according to the following 
> documentation
> https://apacheignite-mix.readme.io/docs/php-pdo
> In particular:
> - The ODBC driver was built from the latest 1.8 sources located in ignite-1.8 
> branch. 
> - The DSN configuration is shown in the attached screenshot name 
> "dsn_configuration"
> - Ignite's cluster configuration is attached as well.
> To reproduce the issue do the following:
> - start a node using attached default-config.xml
> - execute insert.php. There won't be any error.
> - execute update.php and you'll get the error with the stack trace below
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
> DML
>  statement [qry=UPDATE Person SET salary = 42000.0 WHERE salary > 5.0, 
> param
> s=[]]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.execut
> eQuery(GridQueryProcessor.java:1800)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryT
> woStep(GridQueryProcessor.java:810)
> ... 13 more
> Caused by: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException:
>  Failed to execute DML statement [qry=UPDATE Person SET salary = 42000.0 
> WHERE s
> alary > 5.0, params=[]]
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.query
> TwoStep(IgniteH2Indexing.java:1270)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.appl
> yx(GridQueryProcessor.java:812)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.appl
> yx(GridQueryProcessor.java:810)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOu
> tClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.execut
> eQuery(GridQueryProcessor.java:1777)
> ... 14 more
> Caused by: class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicChecke
> dException: Failed to locally write to cache (all transaction entries will be 
> in
> validated, however there was a window when entries for this transaction were 
> vis
> ible to others): GridNearTxLocal [mappings=IgniteTxMappingsSingleImpl 
> [mapping=G
> ridDistributedTxMapping [entries=[IgniteTxEntry [key=KeyCacheObjectImpl 
> [val=777
> , hasValBytes=false], cacheId=1215863053, partId=-1, txKey=IgniteTxKey 
> [key=KeyC
> acheObjectImpl [val=777, hasValBytes=false], cacheId=1215863053], 
> val=[op=TRANSF
> ORM, val=null], prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryPr
> ocessorsCol=[IgniteBiTuple 
> [val1=org.apache.ignite.internal.processors.query.h2.
> DmlStatementsProcessor$ModifyingEntryProcessor@1f2f10da, 
> val2=[Ljava.lang.Object
> ;@2bfa5294]], ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null,
>  dhtVer=GridCacheVersion [topVer=92027384, time=1480547401695, 
> order=14805473813
> 93, nodeOrder=1], filters=[], filtersPassed=false, filtersSet=true, 
> entry=GridDh
> tColocatedCacheEntry [super=GridDhtCacheEntry [rdrs=[], 
> locPart=GridDhtLocalPart
> ition [id=777, 
> map=org.apache.ignite.internal.processors.cache.GridCacheConcurre
> ntMapImpl@24c94530, rmvQueue=GridCircularBuffer [sizeMask=255, idxGen=0], 
> cntr=1
> , shouldBeRenting=false, state=OWNING, reservations=0, empty=false, 
> createTime=1
> 1/30/2016 15:09:45], super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [k
> ey=KeyCacheObjectImpl [val=777, hasValBytes=false], val=Person 
> [idHash=659295625
> , hash=-322179972, resume=Secret Service agent, firstName=James, 
> lastName=Bond,
> salary=65000.0], startVer=1480547381389, ver=GridCacheVersion 
> [topVer=92027384,
> time=1480547394518, order=1480547381390, nodeOrder=1], hash=777, 
> extras=GridCach
> eMvccEntryExtras [mvcc=GridCacheMvcc [locs=[GridCacheMvccCandidate 
> [nodeId=08b20
> b4b-3ca6-4c05-aa9d-4219cbc3f3f5, ver=GridCacheVersion [topVer=92027384, 
> time=148
> 0547401693, order=1480547381392, nodeOrder=1], timeout=0, ts=1480547401693, 
> thre
> adId=57, id=3, topVer=AffinityTopologyVersion [topVer=1, minorTopVer=0], 
> reentry

[jira] [Commented] (IGNITE-4346) DML and PHP PDO: double field is converted to bigdecimal

2016-12-01 Thread Igor Sapego (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711751#comment-15711751
 ] 

Igor Sapego commented on IGNITE-4346:
-

Denis, Alexander,

I've tried to reproduce the issue on the ignite-4340 and it can't be reproduced 
on this branch.

> DML and PHP PDO: double field is converted to bigdecimal
> 
>
> Key: IGNITE-4346
> URL: https://issues.apache.org/jira/browse/IGNITE-4346
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Igor Sapego
>Priority: Blocker
> Fix For: 1.8
>
> Attachments: default-config.xml, dsn_configuration.png, insert.php, 
> update.php
>
>
> I've set up PHP PDO and ODBC environment according to the following 
> documentation
> https://apacheignite-mix.readme.io/docs/php-pdo
> In particular:
> - The ODBC driver was built from the latest 1.8 sources located in ignite-1.8 
> branch. 
> - The DSN configuration is shown in the attached screenshot name 
> "dsn_configuration"
> - Ignite's cluster configuration is attached as well.
> To reproduce the issue do the following:
> - start a node using attached default-config.xml
> - execute insert.php. There won't be any error.
> - execute update.php and you'll get the error with the stack trace below
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
> DML
>  statement [qry=UPDATE Person SET salary = 42000.0 WHERE salary > 5.0, 
> param
> s=[]]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.execut
> eQuery(GridQueryProcessor.java:1800)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryT
> woStep(GridQueryProcessor.java:810)
> ... 13 more
> Caused by: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException:
>  Failed to execute DML statement [qry=UPDATE Person SET salary = 42000.0 
> WHERE s
> alary > 5.0, params=[]]
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.query
> TwoStep(IgniteH2Indexing.java:1270)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.appl
> yx(GridQueryProcessor.java:812)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.appl
> yx(GridQueryProcessor.java:810)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOu
> tClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.execut
> eQuery(GridQueryProcessor.java:1777)
> ... 14 more
> Caused by: class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicChecke
> dException: Failed to locally write to cache (all transaction entries will be 
> in
> validated, however there was a window when entries for this transaction were 
> vis
> ible to others): GridNearTxLocal [mappings=IgniteTxMappingsSingleImpl 
> [mapping=G
> ridDistributedTxMapping [entries=[IgniteTxEntry [key=KeyCacheObjectImpl 
> [val=777
> , hasValBytes=false], cacheId=1215863053, partId=-1, txKey=IgniteTxKey 
> [key=KeyC
> acheObjectImpl [val=777, hasValBytes=false], cacheId=1215863053], 
> val=[op=TRANSF
> ORM, val=null], prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryPr
> ocessorsCol=[IgniteBiTuple 
> [val1=org.apache.ignite.internal.processors.query.h2.
> DmlStatementsProcessor$ModifyingEntryProcessor@1f2f10da, 
> val2=[Ljava.lang.Object
> ;@2bfa5294]], ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null,
>  dhtVer=GridCacheVersion [topVer=92027384, time=1480547401695, 
> order=14805473813
> 93, nodeOrder=1], filters=[], filtersPassed=false, filtersSet=true, 
> entry=GridDh
> tColocatedCacheEntry [super=GridDhtCacheEntry [rdrs=[], 
> locPart=GridDhtLocalPart
> ition [id=777, 
> map=org.apache.ignite.internal.processors.cache.GridCacheConcurre
> ntMapImpl@24c94530, rmvQueue=GridCircularBuffer [sizeMask=255, idxGen=0], 
> cntr=1
> , shouldBeRenting=false, state=OWNING, reservations=0, empty=false, 
> createTime=1
> 1/30/2016 15:09:45], super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [k
> ey=KeyCacheObjectImpl [val=777, hasValBytes=false], val=Person 
> [idHash=659295625
> , hash=-322179972, resume=Secret Service agent, firstName=James, 
> lastName=Bond,
> salary=65000.0], startVer=1480547381389, ver=GridCacheVersion 
> [topVer=92027384,
> time=1480547394518, order=1480547381390, nodeOrder=1], hash=777, 
> extras=GridCach
> eMvccEntryExtras [mvcc=GridCacheMvcc [locs=[GridCacheMvccCandidate 
> [nodeId=08b20
> b4b-3ca6-4c05-aa9d-4219cbc3f3f5, ver=GridCacheVersion [topVer=92027384, 
> time=148
> 0547401693, order=1480547381392, nodeOrder=1], timeout=0, ts=1480547401693, 
> thre
> adId=57, id=3, topVer=AffinityTopologyVersion [topVer=1, minorTopVer=0], 
> reentry
> =null,

[jira] [Comment Edited] (IGNITE-4045) .NET: Support DML API

2016-12-01 Thread Pavel Tupitsyn (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711741#comment-15711741
 ] 

Pavel Tupitsyn edited comment on IGNITE-4045 at 12/1/16 11:42 AM:
--

Another thing to be ported to .NET is BinaryIdentityResolver interface 
(BinaryTypeConfiguration.BinaryIdentityResolver).


was (Author: ptupitsyn):
Another thing to be ported to .NET is BinaryIdentityResolver interface.

> .NET: Support DML API
> -
>
> Key: IGNITE-4045
> URL: https://issues.apache.org/jira/browse/IGNITE-4045
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
>  Labels: roadmap
> Fix For: 2.0
>
>
> Ignite's Java component will provide support for DML soon (IGNITE-2294). At 
> she same time DML will be supported at the level of ODBC and JDBC drivers.
> As the next step we should include the similar functionality into Ignite.NET 
> by doing the following:
> - Implement DML API;
> - Enhance {{QueryExample.cs}} by doing INSERTs instead of cache.puts and 
> adding UPDATE and DELETE operation examples.
> - Add documentation to Ignite.NET readme.io covering the feature. Most like 
> most of the content can be take from the general documentation when this 
> ticket IGNITE-4018 is ready 
> (https://apacheignite.readme.io/docs/distributed-dml).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4045) .NET: Support DML API

2016-12-01 Thread Pavel Tupitsyn (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711741#comment-15711741
 ] 

Pavel Tupitsyn commented on IGNITE-4045:


Another thing to be ported to .NET is BinaryIdentityResolver interface.

> .NET: Support DML API
> -
>
> Key: IGNITE-4045
> URL: https://issues.apache.org/jira/browse/IGNITE-4045
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
>  Labels: roadmap
> Fix For: 2.0
>
>
> Ignite's Java component will provide support for DML soon (IGNITE-2294). At 
> she same time DML will be supported at the level of ODBC and JDBC drivers.
> As the next step we should include the similar functionality into Ignite.NET 
> by doing the following:
> - Implement DML API;
> - Enhance {{QueryExample.cs}} by doing INSERTs instead of cache.puts and 
> adding UPDATE and DELETE operation examples.
> - Add documentation to Ignite.NET readme.io covering the feature. Most like 
> most of the content can be take from the general documentation when this 
> ticket IGNITE-4018 is ready 
> (https://apacheignite.readme.io/docs/distributed-dml).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-4342) DML: clear() on atomic cache causes the exception from previous failed DML statement

2016-12-01 Thread Alexander Paschenko (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Paschenko resolved IGNITE-4342.
-
Resolution: Duplicate

> DML: clear() on atomic cache causes the exception from previous failed DML 
> statement
> 
>
> Key: IGNITE-4342
> URL: https://issues.apache.org/jira/browse/IGNITE-4342
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
> Attachments: IGNITE-4342.zip
>
>
> 0. Extact the attachment into {{examples}} directory
> 1. Start {{ExtSqlExampleNodeStartup}}
> 2. Start {{ExtSqlAtomicExample}}. It fails:
> {noformat}
> [17:22:23,763][INFO ][main][GridDiscoveryManager] Topology snapshot [ver=6, 
> servers=1, clients=1, CPUs=8, heap=2.0GB]
> The cache size atomic-part-full-sync: 0
> Preloading ... 
> The cache size atomic-part-full-sync: 1000
> Update failed
> Clear cache atomic-part-full-sync
> [17:22:25,207][ERROR][mgmt-#60%null%][GridTaskWorker] Failed to obtain remote 
> job result policy for result from ComputeTask.result(..) method (will fail 
> the whole task): GridJobResultImpl 
> [job=o.a.i.i.processors.cache.GridCacheAdapter$GlobalClearAllJob@5dca5ddf, 
> sib=GridJobSiblingImpl 
> [sesId=3fe2d95b851-3bc6c31d-7339-434a-b0cd-2edda611fc19, 
> jobId=4fe2d95b851-3bc6c31d-7339-434a-b0cd-2edda611fc19, 
> nodeId=87311db5-3911-41f6-ac47-e739031a91dd, isJobDone=false], 
> jobCtx=GridJobContextImpl 
> [jobId=4fe2d95b851-3bc6c31d-7339-434a-b0cd-2edda611fc19, timeoutObj=null, 
> attrs={}], node=TcpDiscoveryNode [id=87311db5-3911-41f6-ac47-e739031a91dd, 
> addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 172.22.222.137, 172.25.4.107], 
> sockAddrs=[/172.22.222.137:47500, /172.25.4.107:47500, /127.0.0.1:47500, 
> /0:0:0:0:0:0:0:1:47500], discPort=47500, order=1, intOrder=1, 
> lastExchangeTime=1480515743167, loc=false, ver=1.8.0#20161128-sha1:a53fd38c, 
> isClient=false], ex=class o.a.i.compute.ComputeUserUndeclaredException: 
> Failed to execute job due to unexpected runtime exception 
> [jobId=4fe2d95b851-3bc6c31d-7339-434a-b0cd-2edda611fc19, 
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl 
> [taskName=o.a.i.i.processors.cache.GridCacheAdapter$ClearTask, 
> dep=LocalDeployment [super=GridDeployment [ts=1480515673415, depMode=SHARED, 
> clsLdr=sun.misc.Launcher$AppClassLoader@2e5f8245, 
> clsLdrId=ef34c95b851-87311db5-3911-41f6-ac47-e739031a91dd, userVer=0, 
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false, 
> undeployed=false, usage=0]], 
> taskClsName=o.a.i.i.processors.cache.GridCacheAdapter$ClearTask, 
> sesId=3fe2d95b851-3bc6c31d-7339-434a-b0cd-2edda611fc19, 
> startTime=1480515745181, endTime=9223372036854775807, 
> taskNodeId=3bc6c31d-7339-434a-b0cd-2edda611fc19, 
> clsLdr=sun.misc.Launcher$AppClassLoader@2e5f8245, closed=false, cpSpi=null, 
> failSpi=null, loadSpi=null, usage=1, fullSup=false, internal=true, 
> subjId=3bc6c31d-7339-434a-b0cd-2edda611fc19, mapFut=IgniteFuture 
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1480515745181, 
> endTime=0, ignoreInterrupts=false, state=INIT]]], 
> jobId=4fe2d95b851-3bc6c31d-7339-434a-b0cd-2edda611fc19]], hasRes=true, 
> isCancelled=false, isOccupied=true]
> class org.apache.ignite.IgniteException: Remote job threw exception.
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$ClearTask.result(GridCacheAdapter.java:6800)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1030)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1023)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6596)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:1023)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:841)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
>   at 
>

[jira] [Commented] (IGNITE-4342) DML: clear() on atomic cache causes the exception from previous failed DML statement

2016-12-01 Thread Alexander Paschenko (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711703#comment-15711703
 ] 

Alexander Paschenko commented on IGNITE-4342:
-

Judging by this,

{noformat}
Caused by: java.lang.ClassCastException: java.lang.Integer cannot be cast to 
java.lang.Long
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$RowDescriptor.wrap(IgniteH2Indexing.java:2960)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:316)
at org.h2.index.BaseIndex.compareRows(BaseIndex.java:295)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:202)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:48)
at 
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1401)
at 
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1397)
at 
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2153)
at 
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.updateUnderRoot(GridOffHeapSnapTreeMap.java:2085)
at 
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.update(GridOffHeapSnapTreeMap.java:1966)
at 
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.remove(GridOffHeapSnapTreeMap.java:1935)
at 
org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.remove(GridOffHeapSnapTreeMap.java:108)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.remove(GridH2TreeIndex.java:367)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.doUpdate(GridH2Table.java:594)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:495)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.remove(IgniteH2Indexing.java:666)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.remove(GridQueryProcessor.java:1056)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.remove(GridCacheQueryManager.java:456)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.clearIndex(GridCacheMapEntry.java:4039)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.clear(GridCacheMapEntry.java:2816)
at 
org.apache.ignite.internal.processors.cache.GridCacheClearAllRunnable.clearEntry(GridCacheClearAllRunnable.java:145)
at 
org.apache.ignite.internal.processors.cache.GridCacheClearAllRunnable.run(GridCacheClearAllRunnable.java:96)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.clearLocally(GridCacheAdapter.java:1141)
at 
org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.clearLocally(GridCacheProxyImpl.java:1048)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter$GlobalClearAllJob.localExecute(GridCacheAdapter.java:5461)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter$TopologyVersionAwareJob.execute(GridCacheAdapter.java:6473)
at 
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:556)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6564)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:550)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:479)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1114)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1894)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}

it's IGNITE-4340 again. Example does not fail on it. Closing as duplicate.

> DML: clear() on atomic cache causes the

[jira] [Assigned] (IGNITE-4342) DML: clear() on atomic cache causes the exception from previous failed DML statement

2016-12-01 Thread Alexander Paschenko (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Paschenko reassigned IGNITE-4342:
---

Assignee: Alexander Paschenko

> DML: clear() on atomic cache causes the exception from previous failed DML 
> statement
> 
>
> Key: IGNITE-4342
> URL: https://issues.apache.org/jira/browse/IGNITE-4342
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
> Attachments: IGNITE-4342.zip
>
>
> 0. Extact the attachment into {{examples}} directory
> 1. Start {{ExtSqlExampleNodeStartup}}
> 2. Start {{ExtSqlAtomicExample}}. It fails:
> {noformat}
> [17:22:23,763][INFO ][main][GridDiscoveryManager] Topology snapshot [ver=6, 
> servers=1, clients=1, CPUs=8, heap=2.0GB]
> The cache size atomic-part-full-sync: 0
> Preloading ... 
> The cache size atomic-part-full-sync: 1000
> Update failed
> Clear cache atomic-part-full-sync
> [17:22:25,207][ERROR][mgmt-#60%null%][GridTaskWorker] Failed to obtain remote 
> job result policy for result from ComputeTask.result(..) method (will fail 
> the whole task): GridJobResultImpl 
> [job=o.a.i.i.processors.cache.GridCacheAdapter$GlobalClearAllJob@5dca5ddf, 
> sib=GridJobSiblingImpl 
> [sesId=3fe2d95b851-3bc6c31d-7339-434a-b0cd-2edda611fc19, 
> jobId=4fe2d95b851-3bc6c31d-7339-434a-b0cd-2edda611fc19, 
> nodeId=87311db5-3911-41f6-ac47-e739031a91dd, isJobDone=false], 
> jobCtx=GridJobContextImpl 
> [jobId=4fe2d95b851-3bc6c31d-7339-434a-b0cd-2edda611fc19, timeoutObj=null, 
> attrs={}], node=TcpDiscoveryNode [id=87311db5-3911-41f6-ac47-e739031a91dd, 
> addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 172.22.222.137, 172.25.4.107], 
> sockAddrs=[/172.22.222.137:47500, /172.25.4.107:47500, /127.0.0.1:47500, 
> /0:0:0:0:0:0:0:1:47500], discPort=47500, order=1, intOrder=1, 
> lastExchangeTime=1480515743167, loc=false, ver=1.8.0#20161128-sha1:a53fd38c, 
> isClient=false], ex=class o.a.i.compute.ComputeUserUndeclaredException: 
> Failed to execute job due to unexpected runtime exception 
> [jobId=4fe2d95b851-3bc6c31d-7339-434a-b0cd-2edda611fc19, 
> ses=GridJobSessionImpl [ses=GridTaskSessionImpl 
> [taskName=o.a.i.i.processors.cache.GridCacheAdapter$ClearTask, 
> dep=LocalDeployment [super=GridDeployment [ts=1480515673415, depMode=SHARED, 
> clsLdr=sun.misc.Launcher$AppClassLoader@2e5f8245, 
> clsLdrId=ef34c95b851-87311db5-3911-41f6-ac47-e739031a91dd, userVer=0, 
> loc=true, sampleClsName=java.lang.String, pendingUndeploy=false, 
> undeployed=false, usage=0]], 
> taskClsName=o.a.i.i.processors.cache.GridCacheAdapter$ClearTask, 
> sesId=3fe2d95b851-3bc6c31d-7339-434a-b0cd-2edda611fc19, 
> startTime=1480515745181, endTime=9223372036854775807, 
> taskNodeId=3bc6c31d-7339-434a-b0cd-2edda611fc19, 
> clsLdr=sun.misc.Launcher$AppClassLoader@2e5f8245, closed=false, cpSpi=null, 
> failSpi=null, loadSpi=null, usage=1, fullSup=false, internal=true, 
> subjId=3bc6c31d-7339-434a-b0cd-2edda611fc19, mapFut=IgniteFuture 
> [orig=GridFutureAdapter [resFlag=0, res=null, startTime=1480515745181, 
> endTime=0, ignoreInterrupts=false, state=INIT]]], 
> jobId=4fe2d95b851-3bc6c31d-7339-434a-b0cd-2edda611fc19]], hasRes=true, 
> isCancelled=false, isOccupied=true]
> class org.apache.ignite.IgniteException: Remote job threw exception.
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$ClearTask.result(GridCacheAdapter.java:6800)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1030)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1023)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6596)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:1023)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:841)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
>   at 
>

[jira] [Assigned] (IGNITE-4346) DML and PHP PDO: double field is converted to bigdecimal

2016-12-01 Thread Igor Sapego (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Igor Sapego reassigned IGNITE-4346:
---

Assignee: Igor Sapego  (was: Alexander Paschenko)

> DML and PHP PDO: double field is converted to bigdecimal
> 
>
> Key: IGNITE-4346
> URL: https://issues.apache.org/jira/browse/IGNITE-4346
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Igor Sapego
>Priority: Blocker
> Fix For: 1.8
>
> Attachments: default-config.xml, dsn_configuration.png, insert.php, 
> update.php
>
>
> I've set up PHP PDO and ODBC environment according to the following 
> documentation
> https://apacheignite-mix.readme.io/docs/php-pdo
> In particular:
> - The ODBC driver was built from the latest 1.8 sources located in ignite-1.8 
> branch. 
> - The DSN configuration is shown in the attached screenshot name 
> "dsn_configuration"
> - Ignite's cluster configuration is attached as well.
> To reproduce the issue do the following:
> - start a node using attached default-config.xml
> - execute insert.php. There won't be any error.
> - execute update.php and you'll get the error with the stack trace below
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
> DML
>  statement [qry=UPDATE Person SET salary = 42000.0 WHERE salary > 5.0, 
> param
> s=[]]
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.execut
> eQuery(GridQueryProcessor.java:1800)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryT
> woStep(GridQueryProcessor.java:810)
> ... 13 more
> Caused by: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException:
>  Failed to execute DML statement [qry=UPDATE Person SET salary = 42000.0 
> WHERE s
> alary > 5.0, params=[]]
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.query
> TwoStep(IgniteH2Indexing.java:1270)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.appl
> yx(GridQueryProcessor.java:812)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.appl
> yx(GridQueryProcessor.java:810)
> at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOu
> tClosureX.java:36)
> at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.execut
> eQuery(GridQueryProcessor.java:1777)
> ... 14 more
> Caused by: class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicChecke
> dException: Failed to locally write to cache (all transaction entries will be 
> in
> validated, however there was a window when entries for this transaction were 
> vis
> ible to others): GridNearTxLocal [mappings=IgniteTxMappingsSingleImpl 
> [mapping=G
> ridDistributedTxMapping [entries=[IgniteTxEntry [key=KeyCacheObjectImpl 
> [val=777
> , hasValBytes=false], cacheId=1215863053, partId=-1, txKey=IgniteTxKey 
> [key=KeyC
> acheObjectImpl [val=777, hasValBytes=false], cacheId=1215863053], 
> val=[op=TRANSF
> ORM, val=null], prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryPr
> ocessorsCol=[IgniteBiTuple 
> [val1=org.apache.ignite.internal.processors.query.h2.
> DmlStatementsProcessor$ModifyingEntryProcessor@1f2f10da, 
> val2=[Ljava.lang.Object
> ;@2bfa5294]], ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null,
>  dhtVer=GridCacheVersion [topVer=92027384, time=1480547401695, 
> order=14805473813
> 93, nodeOrder=1], filters=[], filtersPassed=false, filtersSet=true, 
> entry=GridDh
> tColocatedCacheEntry [super=GridDhtCacheEntry [rdrs=[], 
> locPart=GridDhtLocalPart
> ition [id=777, 
> map=org.apache.ignite.internal.processors.cache.GridCacheConcurre
> ntMapImpl@24c94530, rmvQueue=GridCircularBuffer [sizeMask=255, idxGen=0], 
> cntr=1
> , shouldBeRenting=false, state=OWNING, reservations=0, empty=false, 
> createTime=1
> 1/30/2016 15:09:45], super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [k
> ey=KeyCacheObjectImpl [val=777, hasValBytes=false], val=Person 
> [idHash=659295625
> , hash=-322179972, resume=Secret Service agent, firstName=James, 
> lastName=Bond,
> salary=65000.0], startVer=1480547381389, ver=GridCacheVersion 
> [topVer=92027384,
> time=1480547394518, order=1480547381390, nodeOrder=1], hash=777, 
> extras=GridCach
> eMvccEntryExtras [mvcc=GridCacheMvcc [locs=[GridCacheMvccCandidate 
> [nodeId=08b20
> b4b-3ca6-4c05-aa9d-4219cbc3f3f5, ver=GridCacheVersion [topVer=92027384, 
> time=148
> 0547401693, order=1480547381392, nodeOrder=1], timeout=0, ts=1480547401693, 
> thre
> adId=57, id=3, topVer=AffinityTopologyVersion [topVer=1, minorTopVer=0], 
> reentry
> =null, otherNodeId=08b20b4b-3ca6-4c05-aa9d-4219cbc3f3f5, 
> otherVer=GridCacheVersi
> on

[jira] [Created] (IGNITE-4350) Cache JDBC POJO store: improve default data transformation

2016-12-01 Thread Alexey Kuznetsov (JIRA)

Alexey Kuznetsov created IGNITE-4350:


 Summary: Cache JDBC POJO store: improve default data transformation
 Key: IGNITE-4350
 URL: https://issues.apache.org/jira/browse/IGNITE-4350
 Project: Ignite
  Issue Type: Task
  Components: cache
Affects Versions: 1.7
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 1.9


Improve JdbcTypesDefaultTransformer logic in case when in database column 
declared as some TYPE1 and in POJO store same column declared as some TYPE2. We 
could try to handle such cases out of the box.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4343) Check mutable entries for existence properly inside DML entry processors

2016-12-01 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711525#comment-15711525
 ] 

ASF GitHub Bot commented on IGNITE-4343:


GitHub user alexpaschenko opened a pull request:

https://github.com/apache/ignite/pull/1304

IGNITE-4343 DmlStatementsProcessor - entry processors corrections



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4343

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1304.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 #1304


commit 70642dc2795ce42a074472b621bc55e59722f77b
Author: Alexander Paschenko 
Date:   2016-11-30T11:32:05Z

IGNITE-4343 DmlStatementsProcessor - entry processors corrections




> Check mutable entries for existence properly inside DML entry processors
> 
>
> Key: IGNITE-4343
> URL: https://issues.apache.org/jira/browse/IGNITE-4343
> Project: Ignite
>  Issue Type: Improvement
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-3849) Web console: Custom table values does not have autofocus field.

2016-12-01 Thread Vasiliy Sisko (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711518#comment-15711518
 ] 

Vasiliy Sisko commented on IGNITE-3849:
---

Fixed auto focused fields for checkpoint section, failover section, and load 
balancing section of cluster configuration.
Added autofocus on JDBC driver selection on import of domain model.

> Web console: Custom table values does not have autofocus field.
> ---
>
> Key: IGNITE-3849
> URL: https://issues.apache.org/jira/browse/IGNITE-3849
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>
> F.e. Binary types table or cache key configuration table. 
> Add new row. No one field has focus.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4344) Client node allocates off heap memories for caches

2016-12-01 Thread Semen Boikov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov reassigned IGNITE-4344:


Assignee: Semen Boikov

> Client node allocates off heap memories for caches
> --
>
> Key: IGNITE-4344
> URL: https://issues.apache.org/jira/browse/IGNITE-4344
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6, 1.7
>Reporter: Nikolay Tikhonov
>Assignee: Semen Boikov
> Fix For: 1.9
>
> Attachments: OffHeapClientTest.patch
>
>
> Client node should not allocate memories. Test attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-4314) Cache.clear should not destroy offheap map

2016-12-01 Thread Semen Boikov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov reassigned IGNITE-4314:


Assignee: Semen Boikov

> Cache.clear should not destroy offheap map
> --
>
> Key: IGNITE-4314
> URL: https://issues.apache.org/jira/browse/IGNITE-4314
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Semen Boikov
>Assignee: Semen Boikov
> Fix For: 1.9
>
>
> Currently when offheap is enabled then cache.clear() operations fully 
> destroys offheap map (GridCacheClearAllRunnable calls 
> GridCacheSwapManager.clearOffHeap). This is not correct since there can be 
> entry referenceing cleared memory, it seems offheap should be cleared in the 
> same way as swap using offheap keys iterator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4157) Use discovery custom messages instead of marshaller cache

2016-12-01 Thread Sergey Chugunov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711292#comment-15711292
 ] 

Sergey Chugunov commented on IGNITE-4157:
-

Marshaller mapping exchange was rewritten to work synchronously: when some node 
wants to add new mapping it gets blocked until grid accepts the mapping or 
rejects it.

> Use discovery custom messages instead of marshaller cache
> -
>
> Key: IGNITE-4157
> URL: https://issues.apache.org/jira/browse/IGNITE-4157
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Sergey Chugunov
> Fix For: 2.0
>
>
> Currently we use system caches for keeping classname to class ID mapping and 
> for storing binary metadata
> This has several serious disadvantages:
> 1) We need to introduce at least two additional thread pools for each of 
> these caches
> 2) Since cache operations require stable topology, registering a class ID or 
> updating metadata inside a transaction or another cache operation is tricky 
> and deadlock-prone.
> 3) It may be beneficial in some cases to have nodes with no caches at all, 
> currently this is impossible because system caches are always present.
> 4) Reading binary metadata leads to huge local contention, caching metadata 
> values in a local map doubles memory consumption
> I suggest we use discovery custom events for these purposes. Each node will 
> have a corresponding local map (state) which will be updated inside custom 
> event handler. From the first point of view, this should remove all the 
> disadvantages above.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

46 matches

Mail list logo