Hello everyone

[suhd]

Hi,
I  want to join the project.


thank you

Re: request an access to jira project

[Oleg Ostanin]

And again thank you!

Best regards
Oleg

On Fri, Dec 2, 2016 at 8:35 AM, Dmitriy Setrakyan 
wrote:

> Done. Feel free to assign the ticket to yourself.
>
> On Fri, Dec 2, 2016 at 8:26 AM, Oleg Ostanin 
> wrote:
>
> > Thank you!
> >
> > My username is oleg-ostanin.
> >
> > Best regards
> > Oleg
> >
> > On Fri, Dec 2, 2016 at 6:37 AM, Dmitriy Setrakyan  >
> > wrote:
> >
> > > Oleg,
> > >
> > > Welcome to the Ignite community!
> > >
> > > You should just register for Apache Jira here:
> > > https://issues.apache.org/jira/secure/Signup!default.jspa
> > >
> > > Once you do, please let us know your login name, so we can add you as a
> > > contributor to the project. This way you will be able to assign tickets
> > to
> > > yourself.
> > >
> > > D.
> > >
> > > On Thu, Dec 1, 2016 at 6:41 PM, Oleg Ostanin 
> > > wrote:
> > >
> > > > Hello Ignite community!
> > > > My name is Oleg and I want to contribute to Apache Ignite. I want to
> > > > start with this issue - IGNITE-4058.
> > > > Please, provide me access to jira project, my username oleg-ostanin.
> > > > Thanks.
> > > >
> > >
> >
>

Re: request an access to jira project

[Dmitriy Setrakyan]

Done. Feel free to assign the ticket to yourself.

On Fri, Dec 2, 2016 at 8:26 AM, Oleg Ostanin  wrote:

> Thank you!
>
> My username is oleg-ostanin.
>
> Best regards
> Oleg
>
> On Fri, Dec 2, 2016 at 6:37 AM, Dmitriy Setrakyan 
> wrote:
>
> > Oleg,
> >
> > Welcome to the Ignite community!
> >
> > You should just register for Apache Jira here:
> > https://issues.apache.org/jira/secure/Signup!default.jspa
> >
> > Once you do, please let us know your login name, so we can add you as a
> > contributor to the project. This way you will be able to assign tickets
> to
> > yourself.
> >
> > D.
> >
> > On Thu, Dec 1, 2016 at 6:41 PM, Oleg Ostanin 
> > wrote:
> >
> > > Hello Ignite community!
> > > My name is Oleg and I want to contribute to Apache Ignite. I want to
> > > start with this issue - IGNITE-4058.
> > > Please, provide me access to jira project, my username oleg-ostanin.
> > > Thanks.
> > >
> >
>

Re: request an access to jira project

[Oleg Ostanin]

Thank you!

My username is oleg-ostanin.

Best regards
Oleg

On Fri, Dec 2, 2016 at 6:37 AM, Dmitriy Setrakyan 
wrote:

> Oleg,
>
> Welcome to the Ignite community!
>
> You should just register for Apache Jira here:
> https://issues.apache.org/jira/secure/Signup!default.jspa
>
> Once you do, please let us know your login name, so we can add you as a
> contributor to the project. This way you will be able to assign tickets to
> yourself.
>
> D.
>
> On Thu, Dec 1, 2016 at 6:41 PM, Oleg Ostanin 
> wrote:
>
> > Hello Ignite community!
> > My name is Oleg and I want to contribute to Apache Ignite. I want to
> > start with this issue - IGNITE-4058.
> > Please, provide me access to jira project, my username oleg-ostanin.
> > Thanks.
> >
>

Re: request an access to jira project

[Dmitriy Setrakyan]

Oleg,

Welcome to the Ignite community!

You should just register for Apache Jira here:
https://issues.apache.org/jira/secure/Signup!default.jspa

Once you do, please let us know your login name, so we can add you as a
contributor to the project. This way you will be able to assign tickets to
yourself.

D.

On Thu, Dec 1, 2016 at 6:41 PM, Oleg Ostanin  wrote:

> Hello Ignite community!
> My name is Oleg and I want to contribute to Apache Ignite. I want to
> start with this issue - IGNITE-4058.
> Please, provide me access to jira project, my username oleg-ostanin.
> Thanks.
>

Re: In-Memory SQL Grid

[Denis Magda]

Igniters,

I’ve finished reworking, enhancing and expanding our SQL Grid documentation 
preparing it to 1.8 release. 

If you recall, before it was a single page documentation and now it’s a big 
section that contains, I hope, all the valuable knowledge we can share with 
Ignite users. Just open the main page 
(https://apacheignite.readme.io/docs/sql-grid 
) and see what we have there. The 
only thing that is still missing is a “Distributed DML” documentation that will 
be made public once 1.8 gets released.

Sergi and other SQL committers & contributes I would encourage you looking over 
the changed documentation and provide or alter it if I’m wrong somewhere.

—
Denis 

> On Nov 23, 2016, at 5:16 PM, Dmitriy Setrakyan  wrote:
> 
> I like SQL Grid, seems consistent. I think that DML support is huge for the
> project!
> 
> D.
> 
> On Wed, Nov 23, 2016 at 12:08 PM, Denis Magda  wrote:
> 
>> Community,
>> 
>> Frankly speaking, Ignite’s SQL support goes far beyond the notion of Data
>> Grid starting from Apache Ignite 1.8.
>> SQL in Ignite is no longer about distributed ANSI-99 SELECT queries only.
>> 
>> It will be about the ability to connect to an Ignite Cluster not only from
>> Java, .NET and C++ sides, that have their own SQL APIs, but, in general,
>> from your favorite programming language or analytical tool by the usage of
>> Ignite’s JDBC and ODBC drivers.
>> 
>> Even after you’re connected to the cluster from JDBC or ODBC side you’re
>> no longer limited by distributed SQL queries. You can freely and easily
>> modify the data with INSERT, UPDATE and DELETE statements thanks to
>> comprehensive DML supported contributed by Alexander Paschenko in version
>> 1.8.  To prove this, Igor Sapego issued a guide <
>> https://apacheignite.readme.io/docs/pdo-interoperability> on how to start
>> working with an Ignite cluster from PHP side which doesn’t have its own API
>> implementation on Ignite side.
>> 
>> At all, all this means that SQL features set deserved its own component
>> which I propose to call In-Memory SQL Grid to conform the naming of the
>> rest of big components like Data Grid, Compute Grid, Service Grid.
>> 
>> I’ve already started reworking our documentation and will spend some time
>> by enriching and expanding it. However, this is a starting point:
>> https://apacheignite.readme.io/docs/sql-grid > io/docs/sql-grid>
>> 
>> Feel free to share your thoughts regarding the naming or content of the
>> doc in general.
>> 
>> —
>> Denis
>> 
>> [1] https://apacheignite.readme.io/docs/sql-grid

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

[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 

[GitHub] ignite pull request #1309: IGNITE-4045 .NET: Support DML API

[ptupitsyn]

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 Tupitsyn 
Date:   2016-12-01T11:34:56Z

wip TestBinaryMode




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this 

Re: Apache Ignite 1.8 Release

[Igor Sapego]

Denis,

I've took a look on the first issue [1], and it seems like it was already
resolved
by another fix made by Alexander.

For the second issue [2] I have raised a PR.

[1] - https://issues.apache.org/jira/browse/IGNITE-4346
[2] - https://issues.apache.org/jira/browse/IGNITE-4347

Best Regards,
Igor

On Thu, Dec 1, 2016 at 2:52 AM, Denis Magda  wrote:

> I’ve faced with two more issues while was working with Ignite from PHP PDO
> side.
>
> The first one is related to DML.
> DML and PHP PDO: double field is converted to bigdecimal <
> https://issues.apache.org/jira/browse/IGNITE-4346>
>
> Alexander P. and Igor S. please pull together and fix this issue before
> 1.8 is sent for vote.
>
> The second issue is related to ODBC and affects the usability only. Igor
> S., please try to address it as a part of 1.8 as well.
> ODBC: NPE when cache name is different from the one configured in DSN <
> https://issues.apache.org/jira/browse/IGNITE-4347>
>
> —
> Denis
>
> > On Nov 30, 2016, at 12:01 PM, Sergey Kozlov 
> wrote:
> >
> > Hi
> >
> > Update for DML testing:
> >
> > IGNITE-4342 DML: clear() on atomic cache causes the exception from
> previous
> > failed DML statement 
> >
> >
> >
> > On Wed, Nov 30, 2016 at 10:18 PM, Denis Magda  wrote:
> >
> >> Vladimir,
> >>
> >> Please add to the release notes information regarding this feature
> >> https://issues.apache.org/jira/browse/IGNITE-2310 <
> >> https://issues.apache.org/jira/browse/IGNITE-2310>
> >>
> >> Essentially, it allows locking a partition while a remote computation is
> >> being executed on a node. I’ve already documented the feature here.
> >> http://apacheignite.gridgain.org/v1.7/docs/collocate-
> >> compute-and-data#affinity-call-and-run-methods <
> >> http://apacheignite.gridgain.org/v1.7/docs/collocate-
> >> compute-and-data#affinity-call-and-run-methods>
> >>
> >> —
> >> Denis
> >>
> >>> On Nov 25, 2016, at 4:08 AM, Vladimir Ozerov 
> >> wrote:
> >>>
> >>> Folks,
> >>>
> >>> I need to create RELEASE NOTES. Please advise which notable tickets you
> >>> completed as a part of 1.8 release.
> >>>
> >>> Vladimir.
> >>>
> >>> On Fri, Nov 25, 2016 at 2:58 PM, Sergey Kozlov 
> >> wrote:
> >>>
>  Hi
> 
>  Could someone explain why Cassandra module splitted into three parts
> in
>  optional directory for binary fabric build? At the moment I see
> >> following
>  unclear points
>  1. ignite-cassandra directory contains README.txt only
>  2. Does ignite-cassandra-serializers depend on ignite-cassandra-store?
> >> In
>  that case why do not make one module?
> 
> 
> 
>  On Fri, Nov 25, 2016 at 2:37 PM, Alexander Paschenko <
>  alexander.a.pasche...@gmail.com> wrote:
> 
> > IGNITE-4303 is most likely fixed by IGNITE-4280 fix (already merged
> in
> > 1.8 branch).
> >
> > Meanwhile everything SQL/DML related seems to be in pull
> > requests/reviewed/fixed/merged (no issues unapproached/not fixed).
> >
> > - Alex
> >
> >
> >
> > 2016-11-24 22:59 GMT+03:00 Sergey Kozlov :
> >> Hi
> >>
> >> I found two issues for 1.8:
> >> IGNITE-4304 ClusterTopologyCheckedException: Failed to send message
> > because
> >> node left grid 
> >> IGNITE-4303 CacheClientBinaryQueryExample returns wrong result
> >> 
> >>
> >> Could someone experienced take a look?
> >>
> >> On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov <
>  voze...@gridgain.com>
> >> wrote:
> >>
> >>> Folks,
> >>>
> >>> DML is merged to ignite-1.8, but according to JIRA reports several
> > problems
> >>> with it were revealed. I propose to focus on DML finalization in
> > ignite-1.8
> >>> branch, and minimize other merges to it, targeting them for the
> next
> >>> release (1.9, 2.0?).
> >>>
> >>> Any objections?
> >>>
> >>> Vladimir.
> >>>
> >>> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego  >
> > wrote:
> >>>
>  Denis,
> 
>  I've raised PRs and Vladimir has merged them into ignite-1.8. But
>  now
> > we
>  have some
>  failing ODBC tests in the branch. I'm currently working on them.
>  There
> >>> is a
>  ticket for
>  that which you can track [1]. I'll add all my findings there.
> 
>  [1] https://issues.apache.org/jira/browse/IGNITE-4288
> 
>  Best Regards,
>  Igor
> 
>  On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda 
> > wrote:
> 
> > Alexander,
> >
> > Awesome news, thanks for making this happen!
> >
> > 

request an access to jira project

[Oleg Ostanin]

Hello Ignite community!
My name is Oleg and I want to contribute to Apache Ignite. I want to
start with this issue - IGNITE-4058.
Please, provide me access to jira project, my username oleg-ostanin.
Thanks.

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

[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)

[GitHub] ignite pull request #1308: IGNITE-4167

[akuramshingg]

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 TcpDiscoveryMulticastIpFinder.requestAddresses wait full 
timeout for remote addresses

commit 82b44fe7e495b418bc4463036f4a6b7169bac6d6
Author: sboikov 
Date:   2016-09-27T12:17:54Z

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

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

[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

[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)

[GitHub] ignite pull request #1306: IGNITE-4336 : Fixed rebalance future.

[ilantukh]

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.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[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)

[GitHub] ignite pull request #1259: ignite-4111

[akuramshingg]

Github user akuramshingg closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1305: IGNITE-4347: Fixed NPE.

[isapego]

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.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[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)

Re: Talking to Ignite From PHP

[Igor Sapego]

Cool, thanks! I'll take a look on the issues.

Best Regards,
Igor

On Thu, Dec 1, 2016 at 3:04 AM, Denis Magda  wrote:

> Igor,
>
> Finally, I could set up the PHP PDO environment and execute the queries,
> provided in the guidance [1].
>
> However, I’ve faced with a couple of the issue that should be addressed as
> a part of 1.8
> https://issues.apache.org/jira/browse/IGNITE-4347 <
> https://issues.apache.org/jira/browse/IGNITE-4347>
> https://issues.apache.org/jira/browse/IGNITE-4346 <
> https://issues.apache.org/jira/browse/IGNITE-4346>
>
> Regardless of that, I’ve improved the documentation and adjusted the code
> snippets in such a way that everything works fine even with those two bugs.
>
> I think we’re done with this documentation. Thanks you a lot for its
> preparation!
>
> [1] https://apacheignite-mix.readme.io/v1.7/docs/php-pdo <
> https://apacheignite-mix.readme.io/v1.7/docs/php-pdo>
>
> —
> Denis
>
> > On Nov 28, 2016, at 10:29 AM, Igor Sapego  wrote:
> >
> > Denis,
> >
> > yes.
> >
> > Best Regards,
> > Igor
> >
> > On Mon, Nov 28, 2016 at 8:26 PM, Denis Magda > wrote:
> >
> >> Igor,
> >>
> >> Has everything been merged into 1.8? Can I start checking PHP/PDO guide?
> >>
> >> —
> >> Denis
> >>
> >>> On Nov 11, 2016, at 3:52 AM, Igor Sapego  wrote:
> >>>
> >>> Denis,
> >>>
> >>> I'm ready to merge it as soon as the 1.8 branch is ready. Once it ready
> >> I'm
> >>> and DML is merged to it, I'm going to merge 1.8 to my branch. After
> that
> >> I
> >>> believe there is going to be some kind of testing from my side and
> review
> >>> from the community side and then I'll merge it to 1.8 once my
> >> contribution
> >>> is accepted. I believe everything from my side is not going to take
> more
> >> than
> >>> few hours, so it all depends on when 1.8 branch is ready and how long
> >> review
> >>> is going to take.
> >>>
> >>>
> >>> Best Regards,
> >>> Igor
> >>>
> >>> On Thu, Nov 10, 2016 at 11:06 PM, Denis Magda  >> >> wrote:
> >>> Igor,
> >>>
> >>> I didn’t manage to merge the branches. There were conflicts that I
> >> couldn’t resolve properly on my side.
> >>>
> >>> Please let me know once everything gets merged into 1.8 branch so that
> I
> >> can go through the guide from the beginning till the end. Do you think
> it
> >> can be done by next Monday?
> >>>
> >>> In the meanwhile, I do like the documentation in its present state and
> >> left a couple of minor comments in the related ticket
> >>> https://issues.apache.org/jira/browse/IGNITE-3921 <
> https://issues.apache.org/jira/browse/IGNITE-3921> <
> >> https://issues.apache.org/jira/browse/IGNITE-3921 <
> https://issues.apache.org/jira/browse/IGNITE-3921>>
> >>>
> >>> —
> >>> Denis
> >>>
>  On Nov 3, 2016, at 5:46 AM, Igor Sapego    >> isap...@gridgain.com >> wrote:
> 
>  Denis,
> 
>  It seems like someone have deleted branch ignite-3910 or maybe I just
> >> forgot to push it
>  to remote repository. However, I've pushed it now. Check it please.
> 
>  Thanks for your contribution to the documentation and pointing out
> what
> >> can be further
>  improved. I'm already working on it.
> 
>  Best Regards,
>  Igor
> 
>  On Thu, Nov 3, 2016 at 1:51 AM, Denis Magda  
> >> >> wrote:
>  Igor,
> 
>  I can’t find branch ignite-3910. Most likely you keep the changes on
> >> the other one. Please double check.
> 
>  In any case, I succeeded with some of the steps from the documentation
> >> and updated it making clearer.
>  http://apacheignite.gridgain.org/v1.7/docs/pdo-interoperability <
> http://apacheignite.gridgain.org/v1.7/docs/pdo-interoperability> <
> >> http://apacheignite.gridgain.org/v1.7/docs/pdo-interoperability <
> http://apacheignite.gridgain.org/v1.7/docs/pdo-interoperability>>
> 
>  Please apply my latest notes related to the documentation.
>  https://issues.apache.org/jira/browse/IGNITE-3921 <
> https://issues.apache.org/jira/browse/IGNITE-3921> <
> >> https://issues.apache.org/jira/browse/IGNITE-3921 <
> https://issues.apache.org/jira/browse/IGNITE-3921>>
> 
>  Let me know as soon as the documentation is refined. I’ll keep at the
> >> installation and testing of PHP + Ignite scenario.
> 
>  —
>  Denis
> 
> > On Nov 2, 2016, at 4:38 AM, Igor Sapego    >> isap...@gridgain.com >> wrote:
> >
> > Denis,
> >
> > I believe that you should switch to DML branch (ignite-2294),
> > and then merge ignite-3910 into it.
> >
> > That should be enough. Please let me 

[GitHub] ignite pull request #1304: IGNITE-4343 DmlStatementsProcessor - entry proces...

[alexpaschenko]

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




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---