Re: Ignite 1.6 release timelines

2016-03-19 Thread Yakov Zhdanov 
Guys,

A lot of time passed since last update to this thread. I want to push this
thread up and I want everybody working on 1.6 tickets to respond here. We
are most of all interested in ODBC and distributed SQL joins. I heard about
some difficulties from Sergi, Artem and Igor while working on these
features, but it seems that we are almost ready to release now, so, guys,
please keep us posted.

Thanks!

--Yakov

2016-02-24 18:12 GMT+03:00 Denis Magda :

> I would add support of the binary mode for distributed data structures and
> atomic references
> https://issues.apache.org/jira/browse/IGNITE-2701
>
> Is anyone interested to pick up this task and implement?
>
> --
> Denis
>
>
> On 2/18/2016 1:36 PM, Vladimir Ozerov wrote:
>
>> I would definitely want to include NuGet and ODBC into upcoming release.
>> Both issues are in review for now. I expect they will be in master in a
>> week or so.
>>
>> LINQ is "nice to have" for me for this release. It changes .NET packaging
>> and moreover must be tested very thoroughly. So it would be cool to
>> include
>> it as well, but I do not think it is a showstopper for 1.6.
>>
>> On Thu, Feb 18, 2016 at 12:47 PM, Pavel Tupitsyn 
>> wrote:
>>
>> There are some important .NET features on review, like LINQ and NuGet:
>>> https://issues.apache.org/jira/browse/IGNITE-1630
>>> https://issues.apache.org/jira/browse/IGNITE-1626
>>>
>>> Vova can clarify which of them are going to be included in 1.6.
>>>
>>> Thanks,
>>>
>>>
>>> On Thu, Feb 18, 2016 at 12:42 PM, Alexey Goncharuk <
>>> alexey.goncha...@gmail.com> wrote:
>>>
>>> Yakov,

 Nothing major from my side is planned for 1.6. There is a ticket
 IGNITE-2610 that I am currently working on (it is almost finished), but
 I
 believe it does not make any restrictions for the schedule.


>>>
>>> --
>>> --
>>> Pavel Tupitsyn
>>> GridGain Systems, Inc.
>>> www.gridgain.com
>>>
>>>
>

Re: Ignite 1.6 release timelines

2016-03-19 Thread Dmitriy Setrakyan 
Thanks Igor!

Is there any update on the non-collocated SQL functionality?

D.

On Thu, Mar 17, 2016 at 7:00 AM, Igor Sapego  wrote:

> Hi,
>
> As for the ODBC there are about 5 left tickets that are currently going
> through review. Except for that there is also such task as implementation
> of "Decimal" type for C++/ODBC but it may take much time to implement
> so this task should not influence on the release date. If I will not make
> it
> in time to include it in the upcoming release we could just release ODBC
> without it.
>
>
> Best Regards,
> Igor
>
> On Thu, Mar 17, 2016 at 12:29 PM, Yakov Zhdanov 
> wrote:
>
> > Guys,
> >
> > A lot of time passed since last update to this thread. I want to push
> this
> > thread up and I want everybody working on 1.6 tickets to respond here. We
> > are most of all interested in ODBC and distributed SQL joins. I heard
> about
> > some difficulties from Sergi, Artem and Igor while working on these
> > features, but it seems that we are almost ready to release now, so, guys,
> > please keep us posted.
> >
> > Thanks!
> >
> > --Yakov
> >
> > 2016-02-24 18:12 GMT+03:00 Denis Magda :
> >
> > > I would add support of the binary mode for distributed data structures
> > and
> > > atomic references
> > > https://issues.apache.org/jira/browse/IGNITE-2701
> > >
> > > Is anyone interested to pick up this task and implement?
> > >
> > > --
> > > Denis
> > >
> > >
> > > On 2/18/2016 1:36 PM, Vladimir Ozerov wrote:
> > >
> > >> I would definitely want to include NuGet and ODBC into upcoming
> release.
> > >> Both issues are in review for now. I expect they will be in master in
> a
> > >> week or so.
> > >>
> > >> LINQ is "nice to have" for me for this release. It changes .NET
> > packaging
> > >> and moreover must be tested very thoroughly. So it would be cool to
> > >> include
> > >> it as well, but I do not think it is a showstopper for 1.6.
> > >>
> > >> On Thu, Feb 18, 2016 at 12:47 PM, Pavel Tupitsyn <
> > ptupit...@gridgain.com>
> > >> wrote:
> > >>
> > >> There are some important .NET features on review, like LINQ and NuGet:
> > >>> https://issues.apache.org/jira/browse/IGNITE-1630
> > >>> https://issues.apache.org/jira/browse/IGNITE-1626
> > >>>
> > >>> Vova can clarify which of them are going to be included in 1.6.
> > >>>
> > >>> Thanks,
> > >>>
> > >>>
> > >>> On Thu, Feb 18, 2016 at 12:42 PM, Alexey Goncharuk <
> > >>> alexey.goncha...@gmail.com> wrote:
> > >>>
> > >>> Yakov,
> > 
> >  Nothing major from my side is planned for 1.6. There is a ticket
> >  IGNITE-2610 that I am currently working on (it is almost finished),
> > but
> >  I
> >  believe it does not make any restrictions for the schedule.
> > 
> > 
> > >>>
> > >>> --
> > >>> --
> > >>> Pavel Tupitsyn
> > >>> GridGain Systems, Inc.
> > >>> www.gridgain.com
> > >>>
> > >>>
> > >
> >
>

Re: Contributions that are waiting for review

2016-03-19 Thread Denis Magda 

Looks great, thanks!

On 3/17/2016 3:55 PM, Anton Vinogradov wrote:

Done,

https://cwiki.apache.org/confluence/display/IGNITE/Issues+waiting+for+review

On Thu, Mar 17, 2016 at 3:46 PM, Denis Magda  wrote:


Pavel, Anton,

Can we simply create a page on Apache wiki that will show a result of the
specific JIRA filter execution? This can be the first improvement we can do
in this direction.

--
Denis


On 3/4/2016 4:14 PM, Anton Vinogradov wrote:


Pavel,
I think that script should be stored inside TeamCity task.



On Fri, Mar 4, 2016 at 3:56 PM, Pavel Tupitsyn 
wrote:

Anton, good idea, the script can be stored in git this way. Dmitriy, what

do you think?

Another question is the email account to send from. Do we have something
suitable already?



On Fri, Mar 4, 2016 at 3:34 PM, Anton Vinogradov <
avinogra...@gridgain.com
wrote:

Folks,

we can create TeamCity task with special trigger (eg. once a day).
This task can contains any script.

On Fri, Mar 4, 2016 at 3:18 PM, Pavel Tupitsyn 
wrote:

Raul, I'm not good with shell scripts. As a .net person I was thinking

about a scheduled C# script on one of our TeamCity win machines, but


Dmitry


prefers Jenkins.


On Fri, Mar 4, 2016 at 2:52 PM, Raul Kripalani 


wrote:
I believe all we need is a shell script in our source tree that

queries

the

JIRA API and produces an output on stdout.

We can then schedule an overnight job with, e.g. a 0 23 * * * cron
expression, and configure the output to be sent to the ML, as


indicated

here: https://wiki.apache.org/general/Jenkins.

@Pavel, would you like to work on the shell script? I can help you
configure the JKS job.

@Dmitriy, can you add both Pavel and me as job admins?




https://wiki.apache.org/general/Jenkins?action=show=Hudson#How_do_I_get_an_account


Cheers,

Re: Contributions that are waiting for review

2016-03-19 Thread Anton Vinogradov 
Done,

https://cwiki.apache.org/confluence/display/IGNITE/Issues+waiting+for+review

On Thu, Mar 17, 2016 at 3:46 PM, Denis Magda  wrote:

> Pavel, Anton,
>
> Can we simply create a page on Apache wiki that will show a result of the
> specific JIRA filter execution? This can be the first improvement we can do
> in this direction.
>
> --
> Denis
>
>
> On 3/4/2016 4:14 PM, Anton Vinogradov wrote:
>
>> Pavel,
>> I think that script should be stored inside TeamCity task.
>>
>>
>>
>> On Fri, Mar 4, 2016 at 3:56 PM, Pavel Tupitsyn 
>> wrote:
>>
>> Anton, good idea, the script can be stored in git this way. Dmitriy, what
>>> do you think?
>>>
>>> Another question is the email account to send from. Do we have something
>>> suitable already?
>>>
>>>
>>>
>>> On Fri, Mar 4, 2016 at 3:34 PM, Anton Vinogradov <
>>> avinogra...@gridgain.com
>>> wrote:
>>>
>>> Folks,

 we can create TeamCity task with special trigger (eg. once a day).
 This task can contains any script.

 On Fri, Mar 4, 2016 at 3:18 PM, Pavel Tupitsyn 
 wrote:

 Raul, I'm not good with shell scripts. As a .net person I was thinking
> about a scheduled C# script on one of our TeamCity win machines, but
>
 Dmitry

> prefers Jenkins.
>
>
> On Fri, Mar 4, 2016 at 2:52 PM, Raul Kripalani 
>
 wrote:
>>>
 I believe all we need is a shell script in our source tree that
>>
> queries
>>>
 the
>
>> JIRA API and produces an output on stdout.
>>
>> We can then schedule an overnight job with, e.g. a 0 23 * * * cron
>> expression, and configure the output to be sent to the ML, as
>>
> indicated
>>>
 here: https://wiki.apache.org/general/Jenkins.
>>
>> @Pavel, would you like to work on the shell script? I can help you
>> configure the JKS job.
>>
>> @Dmitriy, can you add both Pavel and me as job admins?
>>
>>
>>
>>> https://wiki.apache.org/general/Jenkins?action=show=Hudson#How_do_I_get_an_account
>>>
 Cheers,
>>
>>
>

[GitHub] ignite pull request: Ignite 2830

2016-03-19 Thread iveselovskiy 
GitHub user iveselovskiy opened a pull request:

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

Ignite 2830



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

$ git pull https://github.com/iveselovskiy/ignite ignite-2830

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

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


commit a652adec401dc11e6f930fcef9de9b2ee5ecdbb9
Author: iveselovskiy 
Date:   2016-02-10T15:54:36Z

added missing file header to 
org.apache.ignite.hadoop.fs.KerberosHadoopFileSystemFactorySelfTest

commit 48f00cac3ba7668247585ab7c257562951c4f04f
Author: iveselovskiy 
Date:   2016-02-11T10:36:12Z

Merge branch 'master' of https://github.com/apache/ignite

commit a5c5ed4d5bbd61c62acfbb19610aac2f710935cd
Author: iveselovskiy 
Date:   2016-02-15T17:58:10Z

Merge branch 'master' of https://github.com/apache/ignite

commit b81ee18308307dad2416f7635120a387b98bb967
Author: iveselovskiy 
Date:   2016-02-17T18:32:53Z

Merge branch 'master' of https://github.com/apache/ignite

commit 4280cbdeef94a6956ea3ebe1ae389f1db57ed249
Author: iveselovskiy 
Date:   2016-02-18T09:47:12Z

Merge branch 'master' of https://github.com/apache/ignite

commit 754132067d73757f9d362129444b7a6dea3b3f5b
Author: iveselovskiy 
Date:   2016-02-19T13:18:16Z

Merge branch 'master' of https://github.com/apache/ignite

commit cd3a1e02cec00bd089deb3e7cc4c9ec39e7279a7
Author: iveselovskiy 
Date:   2016-02-26T16:24:36Z

Merge branch 'master' of https://github.com/apache/ignite

commit de70be2bc0a6c545428650b1cc09965ac87de8aa
Author: iveselovskiy 
Date:   2016-03-11T09:30:30Z

Merge branch 'master' of https://github.com/apache/ignite

commit 6af5c26f04d2a03795b7c1279dd5532edecc31c4
Author: iveselovskiy 
Date:   2016-03-14T16:47:51Z

Merge branch 'master' of https://github.com/apache/ignite

commit 13a17ba842eb8b2a6820424df8516e0009085387
Author: iveselovskiy 
Date:   2016-03-17T14:35:21Z

Merge branch 'master' of https://github.com/apache/ignite

commit 02b7de94fcf949bfce442b9aa060cfb7d53a1844
Author: iveselovskiy 
Date:   2016-03-18T10:14:41Z

multinode mode added: IgfsMultinodePrimarySelfTest




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

Re: Server node info when client disconnects

2016-03-19 Thread Dmitriy Setrakyan 
cross-sending this to the user list

On Thu, Mar 17, 2016 at 8:39 AM, Alper Tekinalp  wrote:

> Hi.
>
> I have a server and a client. I connect server from client with static
> ip. When server closed I get client node disconnected event. Is there
> easy way that I could know the UUID of the server?
>
> Best regards.
>
> --
> Alper Tekinalp
>
> Software Developer
>
> Evam Stream Analytics
>
> Atatürk Mah.Turgut Özal Bulvarı Gardenya 1 Plaza 42/B K:4 Ataşehir /
> İSTANBUL
>
> Tlf : +90216 688 45 46 Fax : +90216 688 45 47 Gsm:+90 536 222 76 01
>
> www.evam.com
>

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

2016-03-19 Thread Yakov Zhdanov 
Vlad, did you have a chance to review my latest comments?

Thanks!
--
Yakov Zhdanov, Director R
*GridGain Systems*
www.gridgain.com

2016-03-06 12:21 GMT+03:00 Yakov Zhdanov :

> Vlad and all (esp Val and Anton V.),
>
> I reviewed the PR. My comments are in the ticket.
>
> Anton V. there is a question regarding optimized-classnames.properties.
> Can you please respond in ticket?
>
>
> --Yakov
>
> 2016-02-29 16:00 GMT+06:00 Yakov Zhdanov :
>
>> Vlad, that's great! I will take a look this week. Reassigning ticket to
>> myself.
>>
>> --Yakov
>>
>> 2016-02-26 18:37 GMT+03:00 Vladisav Jelisavcic :
>>
>>> Hi,
>>>
>>> i recently implemented distributed ReentrantLock - IGNITE-642,
>>> i made a pull request, so hopefully this could be added to the next
>>> release.
>>>
>>> Best regards,
>>> Vladisav
>>>
>>> On Thu, Feb 18, 2016 at 10:49 AM, Alexey Goncharuk <
>>> alexey.goncha...@gmail.com> wrote:
>>>
>>> > Folks,
>>> >
>>> > The current implementation of IgniteCache.lock(key).lock() has the same
>>> > semantics as the transactional locks - cache topology cannot be changed
>>> > while there exists an ongoing transaction or an explicit lock is held.
>>> The
>>> > restriction for transactions is quite fundamental, the lock() issue
>>> can be
>>> > fixed if we re-implement locking the same way IgniteSemaphore currently
>>> > works.
>>> >
>>> > As for the "Failed to find semaphore with the given name" message, my
>>> first
>>> > guess is that DataStructures were configured with 1 backups which led
>>> to
>>> > the data loss when two nodes were stopped. Mario, can you please
>>> re-test
>>> > your semaphore scenario with 2 backups configured for data structures?
>>> > From my side, I can also take a look at the semaphore issue when I'm
>>> done
>>> > with IGNITE-2610.
>>> >
>>>
>>
>>
>

[GitHub] ignite pull request: GG-11041 - Add ability to unwrap MutableEntry...

2016-03-19 Thread dkarachentsev 
GitHub user dkarachentsev opened a pull request:

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

GG-11041 - Add ability to unwrap MutableEntry passed to entry process…

…or to the same entry as passed to conflict resolver.

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

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

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

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


commit a01e74531be9e4ba80ad1ff2297e2c642912adbe
Author: dkarachentsev 
Date:   2016-03-18T13:58:24Z

GG-11041 - Add ability to unwrap MutableEntry passed to entry processor to 
the same entry as passed to conflict resolver.




---
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-2862) Deployment Ignite in Mesos cluster is failed

2016-03-19 Thread Vasilisa Sidorova (JIRA) 
Vasilisa  Sidorova created IGNITE-2862:
--

 Summary: Deployment Ignite in Mesos cluster is failed
 Key: IGNITE-2862
 URL: https://issues.apache.org/jira/browse/IGNITE-2862
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.5.0.final
Reporter: Vasilisa  Sidorova


-
DESCRIPTION
-
Deployment  Ignite in Mesos cluster by this instruction 
https://apacheignite.readme.io/docs/mesos-deployment is failed 
-
STEPS FOR REPRODUCE
-
# Do items 1-5 from "RUN THE FRAMEWORK VIA MARATHON"   paragraph 
-
ACTUAL RESULT
-
# Ignite nodes didn't start. Only ignition task is running. Look at the 
attached picture "mesos_activetasks.png"
# Stderr log for ignition task get follow exception:
{noformat}
I0318 18:42:08.252142 17138 fetcher.cpp:409] Fetcher Info: 
{"cache_directory":"\/tmp\/mesos\/fetch\/slaves\/20160318-180241-16777343-5050-16554-S0\/root","items":[{"action":"BYPASS_CACHE","uri":{"extract":false,"value":"https:\/\/s3.amazonaws.com\/vasilisk\/m\/ignite-mesos-1.5.0.final.jar"}}],"sandbox_directory":"\/tmp\/mesos\/slaves\/20160318-180241-16777343-5050-16554-S0\/frameworks\/20150603-121744-16842879-5050-6241-\/executors\/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd\/runs\/776db62f-965f-4e9e-950a-4edb67c44667","user":"root"}
I0318 18:42:08.253284 17138 fetcher.cpp:364] Fetching URI 
'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar'
I0318 18:42:08.253298 17138 fetcher.cpp:238] Fetching directly into the sandbox 
directory
I0318 18:42:08.253312 17138 fetcher.cpp:176] Fetching URI 
'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar'
I0318 18:42:08.253325 17138 fetcher.cpp:126] Downloading resource from 
'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar' to 
'/tmp/mesos/slaves/20160318-180241-16777343-5050-16554-S0/frameworks/20150603-121744-16842879-5050-6241-/executors/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd/runs/776db62f-965f-4e9e-950a-4edb67c44667/ignite-mesos-1.5.0.final.jar'
I0318 18:42:12.091784 17138 fetcher.cpp:441] Fetched 
'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar' to 
'/tmp/mesos/slaves/20160318-180241-16777343-5050-16554-S0/frameworks/20150603-121744-16842879-5050-6241-/executors/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd/runs/776db62f-965f-4e9e-950a-4edb67c44667/ignite-mesos-1.5.0.final.jar'
I0318 18:42:12.293658 17142 exec.cpp:132] Version: 0.23.0
I0318 18:42:12.296212 17145 exec.cpp:206] Executor registered on slave 
20160318-180241-16777343-5050-16554-S0
Mar 18, 2016 6:42:12 PM org.apache.ignite.mesos.IgniteFramework main
INFO: Enabling checkpoint for the framework
2016-03-18 18:42:12.495:INFO::main: Logging initialized @151ms
2016-03-18 18:42:22.542:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
2016-03-18 18:42:22.579:INFO:oejs.ServerConnector:main: Started 
ServerConnector@1268c278{HTTP/1.1}{172.17.0.1:48610}
2016-03-18 18:42:22.580:INFO:oejs.Server:main: Started @10235ms
Exception in thread "main" java.lang.RuntimeException: Got unexpected response 
code. Response code: 404
at 
org.apache.ignite.mesos.resource.IgniteProvider.downloadIgnite(IgniteProvider.java:202)
at 
org.apache.ignite.mesos.resource.IgniteProvider.getIgnite(IgniteProvider.java:132)
at 
org.apache.ignite.mesos.resource.ResourceProvider.init(ResourceProvider.java:57)
at org.apache.ignite.mesos.IgniteFramework.main(IgniteFramework.java:77)
{noformat}

-
EXPECTED RESULT
-
Tasks for all 3 nodes are running with ignition task. 
-
ADDITIONAL INFO
-
# File "marathon.json" is attached




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

[GitHub] ignite pull request: ignite-2797 Fixed hanging of transactions wit...

2016-03-19 Thread agura 
GitHub user agura opened a pull request:

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

ignite-2797 Fixed hanging of transactions with timeout



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

$ git pull https://github.com/agura/incubator-ignite ignite-2797-tests-hangs

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

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


commit 2e64d0d7cc51552fffc231cbc850cd615076fb85
Author: vozerov-gridgain 
Date:   2015-12-29T06:31:58Z

IGNITE-2258: IGFS: now default path modes could be optionally disabled 
using FileSystemConfiguration.isInitializeDefaultPathModes() property.

commit 4cd3b3dc2f1fa0f1a9cceb6bf544dd8fb505d7f5
Author: vozerov-gridgain 
Date:   2015-12-29T09:52:00Z

IGNITE-2258: Fixed type on getter/setter.

commit 5d58fcbf40fdb9114e4cbb32b72dd9bce7fa38ca
Author: iveselovskiy 
Date:   2016-01-04T06:47:28Z

IGNITE-2308: Fixed HadoopClassLoader dependency resolution. This closes 
#391.

commit 83a19179cee2bb15adc36c2265dd0a3c794b60bb
Author: vozerov-gridgain 
Date:   2016-01-04T08:14:58Z

IGNITE-2218: Fixed a problem with native Hadoop libraries load. This closes 
#378.

commit 1d7fb5702fa33cf395e797161f3a86a9600921a7
Author: vozerov-gridgain 
Date:   2016-01-05T06:59:31Z

IGNITE-2206: Hadoop file system creation is now abstracted out using 
factory interface.

commit a12ec7d08573d5396654a5ba05bb7d873e4c2677
Author: Ignite Teamcity 
Date:   2016-01-06T10:50:48Z

1.5.2

commit 090a5de6a930c10a3a57a6e28c486fe5c87e028d
Author: vozerov-gridgain 
Date:   2015-12-29T12:50:39Z

Minor fix.

commit c786820dda7f7cd1849c5593ac24ca9072945887
Author: vozerov-gridgain 
Date:   2016-01-07T13:48:14Z

IgniteHadoopIgfsSecondaryFileSystem.usrName field is renamed to "userName" 
to preserve backward compatibility.

commit 6ab4ce246316442fa4295f9941c372fea70c24ef
Author: vozerov-gridgain 
Date:   2016-01-08T06:23:55Z

IGNITE-2342: Set correct classlader before calling FileSystem.get().

commit 077ab1b3a77fdb1c2c2fd6360fc5b60fda6c50c3
Author: vozerov-gridgain 
Date:   2016-01-08T07:17:45Z

IGNITE-2341: Improved warning message when BinaryMarshaller cannot be used. 
Also it is not shown when "org.apache.ignite" classes is in described situation.

commit 86c4816edfd0e983014f136ffc92cde28ec56cca
Author: vozerov-gridgain 
Date:   2016-01-08T07:26:03Z

IGNITE-2340: Improved error thrown when PROXY mode exists, but secondary 
file system is not IgniteHadoopIgfsSecondaryFileSystem.

commit fc48a8429a84ef6c87ed3225a218d7d3ae617e14
Author: vozerov-gridgain 
Date:   2016-01-08T07:48:42Z

Merge branch 'ignite-1.5.2' into ignite-1.5.3

commit 86740cefe212ed0f506d81056dd8e76de9a31e4f
Author: Ignite Teamcity 
Date:   2016-01-08T09:32:11Z

1.5.3-SNAPSHOT

commit 92229d2a6c6ef86772a62cb52b3aa07a55c99d89
Author: sboikov 
Date:   2016-01-13T05:56:34Z

ignite-2359 Added locking for files used by MarshallerContextImpl. (cherry 
picked from commit 1d8c4e2)

commit 2e4ce585d5f54502c6511d3425b1cd5fbf0a7f4f
Author: Ignite Teamcity 
Date:   2016-01-13T10:37:33Z

1.5.4-SNAPSHOT

commit 6e5f9f0c7d4c86773b1f0cd5c5a673acb58c86c2
Author: Denis Magda 
Date:   2016-01-13T11:42:27Z

Changed year to 2016 in Copyrights

commit 02dbcfd8ed2701a4f415c8871d0b8fd08bfa0583
Author: Alexey Goncharuk 
Date:   2016-01-13T13:47:32Z

IGNITE-2365 - Notify policy if swap or offheap is enabled and rebalanced 
entry was not preloaded.
IGNITE-2099 - Fixing custom collections.
This closes #396

commit 86c2ba2a601e82b824cf17422683e5398a4d8c7d
Author: sboikov 
Date:   2016-01-13T15:40:08Z

ignite-2350 Pass update notifier flag in discovery data (all cluster nodes 
will have the same notifier status as first cluster node)
(cherry picked from commit 7175a42)

commit e1a494df400fc37ca04e8d88d1cf20bca02607b4
Author: sboikov 
Date:   2016-01-14T11:16:33Z

Renamed fields to change fields write order (to preserve backward 
compatibility).
(cherry picked from commit 2a4adf5)

commit 09f978234b6062afa1e1658d5a6439365a856aca
Author: sboikov 
Date:   2016-01-14T11:42:44Z

Merge remote-tracking branch 'origin/ignite-1.5.4' into ignite-1.5.4

commit 30043e7892d0b52dc851ce5ec79c7eb3b7cc44fb
Author: Denis Magda 
Date:   2016-01-14T13:02:50Z

Added release notes

commit

[GitHub] ignite pull request: ignite-2797 Fixed hanging of transactions wit...

2016-03-19 Thread agura 
Github user agura closed the pull request at:

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


---
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-2863) Memory leak in GridUnsafeMap destruct method.

2016-03-19 Thread Krome Plasma (JIRA) 
Krome Plasma created IGNITE-2863:


 Summary: Memory leak in GridUnsafeMap destruct method.
 Key: IGNITE-2863
 URL: https://issues.apache.org/jira/browse/IGNITE-2863
 Project: Ignite
  Issue Type: Bug
  Components: cache, general
Reporter: Krome Plasma


There's a memory leak in GridUnsafeMap destruct method() for loop.
The loop's condition is wrong "binAddr < memCap" where offset + memCap should 
be used.



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

[jira] [Created] (IGNITE-2850) ODBC: Add documentation for the ODBC.

2016-03-19 Thread Igor Sapego (JIRA) 
Igor Sapego created IGNITE-2850:
---

 Summary: ODBC: Add documentation for the ODBC.
 Key: IGNITE-2850
 URL: https://issues.apache.org/jira/browse/IGNITE-2850
 Project: Ignite
  Issue Type: Sub-task
  Components: documentation, odbc
Affects Versions: 1.5.0.final
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


Need to add documentation for the ODBC to http://apacheignite.gridgain.org



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

[jira] [Created] (IGNITE-2859) IGFS: test org.apache.ignite.internal.processors.igfs.IgfsStartCacheTest#testCacheStart fakily fails

2016-03-19 Thread Ivan Veselovsky (JIRA) 
Ivan Veselovsky created IGNITE-2859:
---

 Summary: IGFS: test 
org.apache.ignite.internal.processors.igfs.IgfsStartCacheTest#testCacheStart 
fakily fails
 Key: IGNITE-2859
 URL: https://issues.apache.org/jira/browse/IGNITE-2859
 Project: Ignite
  Issue Type: Bug
  Components: IGFS
Affects Versions: 1.6
Reporter: Ivan Veselovsky
 Fix For: 1.6


{code}
java.io.IOException: File was concurrently deleted: /test/test.file
at 
org.apache.ignite.internal.processors.igfs.IgfsOutputStreamImpl.flush(IgfsOutputStreamImpl.java:278)
at 
org.apache.ignite.internal.processors.igfs.IgfsOutputStreamAdapter.close(IgfsOutputStreamAdapter.java:182)
at sun.nio.cs.StreamEncoder.implClose(StreamEncoder.java:320)
at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:149)
at java.io.OutputStreamWriter.close(OutputStreamWriter.java:233)
at java.io.BufferedWriter.close(BufferedWriter.java:266)
at 
org.apache.ignite.internal.processors.igfs.IgfsStartCacheTest.testCacheStart(IgfsStartCacheTest.java:127)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1758)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1696)
at java.lang.Thread.run(Thread.java:745)

{code}

In method 
org.apache.ignite.internal.processors.igfs.IgfsOutputStreamImpl#flush() 
existence of the file being written is checked with id2InfoPrj.get(id) .
For some reason it appears that sometimes this get returns null, while method 
org.apache.ignite.internal.processors.igfs.IgfsMetaManager#create guaranteed to 
return at this point, and the file creation transaction must already be 
committed.



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

[jira] [Created] (IGNITE-2855) Apache Calcite as an SQL query parser and optimizer

2016-03-19 Thread Roman Shtykh (JIRA) 
Roman Shtykh created IGNITE-2855:


 Summary: Apache Calcite as an SQL query parser and optimizer
 Key: IGNITE-2855
 URL: https://issues.apache.org/jira/browse/IGNITE-2855
 Project: Ignite
  Issue Type: New Feature
Reporter: Roman Shtykh


Apache Calcite (https://calcite.apache.org/) can be used as an SQL query 
parser, validator and optimizer with Ignite at the back end.



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

[jira] [Created] (IGNITE-2860) IGFS: Simplify base file system operations for PRIMARY mode.

2016-03-19 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-2860:
---

 Summary: IGFS: Simplify base file  system operations for PRIMARY 
mode.
 Key: IGNITE-2860
 URL: https://issues.apache.org/jira/browse/IGNITE-2860
 Project: Ignite
  Issue Type: Task
  Components: IGFS
Affects Versions: 1.5.0.final
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 1.6


Currently implementation of IGFS base operations for PRIMARY mode is overly 
complex. It is prone to errors and do not let us implement relaxed mode without 
code duplication.

Need to refactor that.



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

Re: Ignite 1.6 release timelines

2016-03-19 Thread Igor Sapego 
Hi,

As for the ODBC there are about 5 left tickets that are currently going
through review. Except for that there is also such task as implementation
of "Decimal" type for C++/ODBC but it may take much time to implement
so this task should not influence on the release date. If I will not make it
in time to include it in the upcoming release we could just release ODBC
without it.


Best Regards,
Igor

On Thu, Mar 17, 2016 at 12:29 PM, Yakov Zhdanov  wrote:

> Guys,
>
> A lot of time passed since last update to this thread. I want to push this
> thread up and I want everybody working on 1.6 tickets to respond here. We
> are most of all interested in ODBC and distributed SQL joins. I heard about
> some difficulties from Sergi, Artem and Igor while working on these
> features, but it seems that we are almost ready to release now, so, guys,
> please keep us posted.
>
> Thanks!
>
> --Yakov
>
> 2016-02-24 18:12 GMT+03:00 Denis Magda :
>
> > I would add support of the binary mode for distributed data structures
> and
> > atomic references
> > https://issues.apache.org/jira/browse/IGNITE-2701
> >
> > Is anyone interested to pick up this task and implement?
> >
> > --
> > Denis
> >
> >
> > On 2/18/2016 1:36 PM, Vladimir Ozerov wrote:
> >
> >> I would definitely want to include NuGet and ODBC into upcoming release.
> >> Both issues are in review for now. I expect they will be in master in a
> >> week or so.
> >>
> >> LINQ is "nice to have" for me for this release. It changes .NET
> packaging
> >> and moreover must be tested very thoroughly. So it would be cool to
> >> include
> >> it as well, but I do not think it is a showstopper for 1.6.
> >>
> >> On Thu, Feb 18, 2016 at 12:47 PM, Pavel Tupitsyn <
> ptupit...@gridgain.com>
> >> wrote:
> >>
> >> There are some important .NET features on review, like LINQ and NuGet:
> >>> https://issues.apache.org/jira/browse/IGNITE-1630
> >>> https://issues.apache.org/jira/browse/IGNITE-1626
> >>>
> >>> Vova can clarify which of them are going to be included in 1.6.
> >>>
> >>> Thanks,
> >>>
> >>>
> >>> On Thu, Feb 18, 2016 at 12:42 PM, Alexey Goncharuk <
> >>> alexey.goncha...@gmail.com> wrote:
> >>>
> >>> Yakov,
> 
>  Nothing major from my side is planned for 1.6. There is a ticket
>  IGNITE-2610 that I am currently working on (it is almost finished),
> but
>  I
>  believe it does not make any restrictions for the schedule.
> 
> 
> >>>
> >>> --
> >>> --
> >>> Pavel Tupitsyn
> >>> GridGain Systems, Inc.
> >>> www.gridgain.com
> >>>
> >>>
> >
>

Server node info when client disconnects

2016-03-19 Thread Alper Tekinalp 
Hi.

I have a server and a client. I connect server from client with static
ip. When server closed I get client node disconnected event. Is there
easy way that I could know the UUID of the server?

Best regards.

-- 
Alper Tekinalp

Software Developer

Evam Stream Analytics

Atatürk Mah.Turgut Özal Bulvarı Gardenya 1 Plaza 42/B K:4 Ataşehir / İSTANBUL

Tlf : +90216 688 45 46 Fax : +90216 688 45 47 Gsm:+90 536 222 76 01

www.evam.com

[GitHub] ignite pull request: IGNITE-2835 Binary object off heap impl leak ...

2016-03-19 Thread ashutakGG 
GitHub user ashutakGG opened a pull request:

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

IGNITE-2835 Binary object off heap impl leak on public API

Fix.

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

$ git pull https://github.com/ashutakGG/incubator-ignite 
ignite-2835-BinaryObjectOffHeapImpl

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

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


commit 2e64d0d7cc51552fffc231cbc850cd615076fb85
Author: vozerov-gridgain 
Date:   2015-12-29T06:31:58Z

IGNITE-2258: IGFS: now default path modes could be optionally disabled 
using FileSystemConfiguration.isInitializeDefaultPathModes() property.

commit 4cd3b3dc2f1fa0f1a9cceb6bf544dd8fb505d7f5
Author: vozerov-gridgain 
Date:   2015-12-29T09:52:00Z

IGNITE-2258: Fixed type on getter/setter.

commit 5d58fcbf40fdb9114e4cbb32b72dd9bce7fa38ca
Author: iveselovskiy 
Date:   2016-01-04T06:47:28Z

IGNITE-2308: Fixed HadoopClassLoader dependency resolution. This closes 
#391.

commit 83a19179cee2bb15adc36c2265dd0a3c794b60bb
Author: vozerov-gridgain 
Date:   2016-01-04T08:14:58Z

IGNITE-2218: Fixed a problem with native Hadoop libraries load. This closes 
#378.

commit 1d7fb5702fa33cf395e797161f3a86a9600921a7
Author: vozerov-gridgain 
Date:   2016-01-05T06:59:31Z

IGNITE-2206: Hadoop file system creation is now abstracted out using 
factory interface.

commit a12ec7d08573d5396654a5ba05bb7d873e4c2677
Author: Ignite Teamcity 
Date:   2016-01-06T10:50:48Z

1.5.2

commit 090a5de6a930c10a3a57a6e28c486fe5c87e028d
Author: vozerov-gridgain 
Date:   2015-12-29T12:50:39Z

Minor fix.

commit c786820dda7f7cd1849c5593ac24ca9072945887
Author: vozerov-gridgain 
Date:   2016-01-07T13:48:14Z

IgniteHadoopIgfsSecondaryFileSystem.usrName field is renamed to "userName" 
to preserve backward compatibility.

commit 6ab4ce246316442fa4295f9941c372fea70c24ef
Author: vozerov-gridgain 
Date:   2016-01-08T06:23:55Z

IGNITE-2342: Set correct classlader before calling FileSystem.get().

commit 077ab1b3a77fdb1c2c2fd6360fc5b60fda6c50c3
Author: vozerov-gridgain 
Date:   2016-01-08T07:17:45Z

IGNITE-2341: Improved warning message when BinaryMarshaller cannot be used. 
Also it is not shown when "org.apache.ignite" classes is in described situation.

commit 86c4816edfd0e983014f136ffc92cde28ec56cca
Author: vozerov-gridgain 
Date:   2016-01-08T07:26:03Z

IGNITE-2340: Improved error thrown when PROXY mode exists, but secondary 
file system is not IgniteHadoopIgfsSecondaryFileSystem.

commit fc48a8429a84ef6c87ed3225a218d7d3ae617e14
Author: vozerov-gridgain 
Date:   2016-01-08T07:48:42Z

Merge branch 'ignite-1.5.2' into ignite-1.5.3

commit 86740cefe212ed0f506d81056dd8e76de9a31e4f
Author: Ignite Teamcity 
Date:   2016-01-08T09:32:11Z

1.5.3-SNAPSHOT

commit 92229d2a6c6ef86772a62cb52b3aa07a55c99d89
Author: sboikov 
Date:   2016-01-13T05:56:34Z

ignite-2359 Added locking for files used by MarshallerContextImpl. (cherry 
picked from commit 1d8c4e2)

commit 2e4ce585d5f54502c6511d3425b1cd5fbf0a7f4f
Author: Ignite Teamcity 
Date:   2016-01-13T10:37:33Z

1.5.4-SNAPSHOT

commit 6e5f9f0c7d4c86773b1f0cd5c5a673acb58c86c2
Author: Denis Magda 
Date:   2016-01-13T11:42:27Z

Changed year to 2016 in Copyrights

commit 02dbcfd8ed2701a4f415c8871d0b8fd08bfa0583
Author: Alexey Goncharuk 
Date:   2016-01-13T13:47:32Z

IGNITE-2365 - Notify policy if swap or offheap is enabled and rebalanced 
entry was not preloaded.
IGNITE-2099 - Fixing custom collections.
This closes #396

commit 86c2ba2a601e82b824cf17422683e5398a4d8c7d
Author: sboikov 
Date:   2016-01-13T15:40:08Z

ignite-2350 Pass update notifier flag in discovery data (all cluster nodes 
will have the same notifier status as first cluster node)
(cherry picked from commit 7175a42)

commit e1a494df400fc37ca04e8d88d1cf20bca02607b4
Author: sboikov 
Date:   2016-01-14T11:16:33Z

Renamed fields to change fields write order (to preserve backward 
compatibility).
(cherry picked from commit 2a4adf5)

commit 09f978234b6062afa1e1658d5a6439365a856aca
Author: sboikov 
Date:   2016-01-14T11:42:44Z

Merge remote-tracking branch 'origin/ignite-1.5.4' into ignite-1.5.4

commit 30043e7892d0b52dc851ce5ec79c7eb3b7cc44fb
Author: Denis Magda 
Date:   2016-01-14T13:02:50Z

Added release notes

Re: Contributions that are waiting for review

2016-03-19 Thread Denis Magda 

Pavel, Anton,

Can we simply create a page on Apache wiki that will show a result of 
the specific JIRA filter execution? This can be the first improvement we 
can do in this direction.


--
Denis

On 3/4/2016 4:14 PM, Anton Vinogradov wrote:

Pavel,
I think that script should be stored inside TeamCity task.



On Fri, Mar 4, 2016 at 3:56 PM, Pavel Tupitsyn 
wrote:


Anton, good idea, the script can be stored in git this way. Dmitriy, what
do you think?

Another question is the email account to send from. Do we have something
suitable already?



On Fri, Mar 4, 2016 at 3:34 PM, Anton Vinogradov 
wrote:


Raul, I'm not good with shell scripts. As a .net person I was thinking
about a scheduled C# script on one of our TeamCity win machines, but

Dmitry

prefers Jenkins.


On Fri, Mar 4, 2016 at 2:52 PM, Raul Kripalani 

wrote:

I believe all we need is a shell script in our source tree that

queries

the

JIRA API and produces an output on stdout.

We can then schedule an overnight job with, e.g. a 0 23 * * * cron
expression, and configure the output to be sent to the ML, as

indicated

here: https://wiki.apache.org/general/Jenkins.

@Pavel, would you like to work on the shell script? I can help you
configure the JKS job.

@Dmitriy, can you add both Pavel and me as job admins?



https://wiki.apache.org/general/Jenkins?action=show=Hudson#How_do_I_get_an_account

Cheers,

[jira] [Created] (IGNITE-2852) TreeMap can't be converted to portable

2016-03-19 Thread Valentin Kulichenko (JIRA) 
Valentin Kulichenko created IGNITE-2852:
---

 Summary: TreeMap can't be converted to portable
 Key: IGNITE-2852
 URL: https://issues.apache.org/jira/browse/IGNITE-2852
 Project: Ignite
  Issue Type: Bug
  Components: binary
Affects Versions: 1.5.0.final
Reporter: Valentin Kulichenko
 Fix For: 1.6


When trying to convert {{TreeMap}} into binary object using {{toBinary}} 
method, the following exception fails:

{noformat}
Exception in thread "main" java.lang.ClassCastException: 
org.apache.ignite.internal.binary.BinaryObjectImpl cannot be cast to 
java.lang.Comparable
at java.util.TreeMap.compare(TreeMap.java:1188)
at java.util.TreeMap.put(TreeMap.java:531)
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.marshalToBinary(CacheObjectBinaryProcessorImpl.java:495)
at 
org.apache.ignite.internal.processors.cache.binary.IgniteBinaryImpl.toBinary(IgniteBinaryImpl.java:67)
at TreeMapTest.main(TreeMapTest.java:15)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
{noformat}

This happens because maps are not wrapped into binary objects, therefore we 
create another {{TreeMap}} and put {{BinaryObject}} instances, which are not 
{{Comparable}}.



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

[jira] [Created] (IGNITE-2861) IGFS: Move meta processors to separate classes.

2016-03-19 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-2861:
---

 Summary: IGFS: Move meta processors to separate classes.
 Key: IGNITE-2861
 URL: https://issues.apache.org/jira/browse/IGNITE-2861
 Project: Ignite
  Issue Type: Task
  Components: IGFS
Affects Versions: 1.5.0.final
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Minor
 Fix For: 1.6


The goal is to simplify {{IgfsMetaManager}}.



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

[jira] [Created] (IGNITE-2854) Need to implement deadlock detection

2016-03-19 Thread Valentin Kulichenko (JIRA) 
Valentin Kulichenko created IGNITE-2854:
---

 Summary: Need to implement deadlock detection
 Key: IGNITE-2854
 URL: https://issues.apache.org/jira/browse/IGNITE-2854
 Project: Ignite
  Issue Type: New Feature
  Components: cache
Affects Versions: 1.5.0.final
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
 Fix For: 1.6


Currently, if transactional deadlock occurred, there is no easy way to find out 
which locks were reordered.

We need to add a mechanism that will collect information about awating 
candidates, analyze it and show guilty keys. Most likely this should be 
implemented with the help of custom discovery message.

In addition we should automatically execute this mechanism if transaction times 
out and add information to timeout exception.



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

[GitHub] ignite pull request: Ignite-2730: Ignite Events Source Streaming t...

2016-03-19 Thread shroman 
GitHub user shroman opened a pull request:

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

Ignite-2730: Ignite Events Source Streaming to Kafka.



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

$ git pull https://github.com/shroman/ignite ignite-2730

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

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


commit a37f2ec63dfc55b708c20b10e75181aaddec50d2
Author: shtykh_roman 
Date:   2016-03-16T12:09:53Z

IGNITE-2730: Ignite Events Source Streaming to Kafka.

commit 30f96d5eb42e655412a47eb3c45cab50ede9871f
Author: shtykh_roman 
Date:   2016-03-17T08:41:03Z

IGNITE-2730: Ignite Events Source Streaming to Kafka. Enabled user-defined 
filter to avoid massive data load to the client.

commit 9009e10b44000403e3dfc4032b26b230d9d60d92
Author: shtykh_roman 
Date:   2016-03-17T09:10:28Z

IGNITE-2730: Ignite Events Source Streaming to Kafka. Enabled the same 
input to multiple topics.

commit e325e7eeb0f26320844a44e22930463d63497c88
Author: shtykh_roman 
Date:   2016-03-17T09:59:42Z

IGNITE-2730: Ignite Events Source Streaming to Kafka. Reset cache name to 
be able to overwrite task configurations from test to test.




---
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-2858) Refactoring of creation of elements on domains page to using of mixins

2016-03-19 Thread Vasiliy Sisko (JIRA) 
Vasiliy Sisko created IGNITE-2858:
-

 Summary: Refactoring of creation of elements on domains page to 
using of mixins
 Key: IGNITE-2858
 URL: https://issues.apache.org/jira/browse/IGNITE-2858
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.6
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko






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

[jira] [Created] (IGNITE-2857) Change console cluster code generation

2016-03-19 Thread Vasiliy Sisko (JIRA) 
Vasiliy Sisko created IGNITE-2857:
-

 Summary: Change console cluster code generation
 Key: IGNITE-2857
 URL: https://issues.apache.org/jira/browse/IGNITE-2857
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.6
Reporter: Vasiliy Sisko
Priority: Minor


In Java preview of general section remove generation of create cache method 
declaration.  



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

[jira] [Created] (IGNITE-2856) Do not generate index fields when them is absent in query fields

2016-03-19 Thread Vasiliy Sisko (JIRA) 
Vasiliy Sisko created IGNITE-2856:
-

 Summary: Do not generate index fields when them is absent in query 
fields
 Key: IGNITE-2856
 URL: https://issues.apache.org/jira/browse/IGNITE-2856
 Project: Ignite
  Issue Type: Bug
  Components: UI, wizards
Affects Versions: 1.6
Reporter: Vasiliy Sisko






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

[jira] [Created] (IGNITE-2851) ODBC: Metadata type retrieval algorithm is wrong.

2016-03-19 Thread Igor Sapego (JIRA) 
Igor Sapego created IGNITE-2851:
---

 Summary: ODBC: Metadata type retrieval algorithm is wrong.
 Key: IGNITE-2851
 URL: https://issues.apache.org/jira/browse/IGNITE-2851
 Project: Ignite
  Issue Type: Sub-task
  Components: odbc
Affects Versions: 1.5.0.final
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


OdbcColumnMeta.writeBinary() method retrieves binary type for the class in a 
wrong way. Use BinaryUtils.typeByClass() instead of BinaryClassDescriptor.



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

Re: Ignite 1.6 release timelines

2016-03-19 Thread Artem Shutak 
Hi,

I've added tests for non-collocated (distributed) SQL joins and found NPE
(which can mask another issues). As I know Serj already started looking on
it.

-- Artem --

On Thu, Mar 17, 2016 at 9:36 PM, Dmitriy Setrakyan 
wrote:

> Thanks Igor!
>
> Is there any update on the non-collocated SQL functionality?
>
> D.
>
> On Thu, Mar 17, 2016 at 7:00 AM, Igor Sapego  wrote:
>
> > Hi,
> >
> > As for the ODBC there are about 5 left tickets that are currently going
> > through review. Except for that there is also such task as implementation
> > of "Decimal" type for C++/ODBC but it may take much time to implement
> > so this task should not influence on the release date. If I will not make
> > it
> > in time to include it in the upcoming release we could just release ODBC
> > without it.
> >
> >
> > Best Regards,
> > Igor
> >
> > On Thu, Mar 17, 2016 at 12:29 PM, Yakov Zhdanov 
> > wrote:
> >
> > > Guys,
> > >
> > > A lot of time passed since last update to this thread. I want to push
> > this
> > > thread up and I want everybody working on 1.6 tickets to respond here.
> We
> > > are most of all interested in ODBC and distributed SQL joins. I heard
> > about
> > > some difficulties from Sergi, Artem and Igor while working on these
> > > features, but it seems that we are almost ready to release now, so,
> guys,
> > > please keep us posted.
> > >
> > > Thanks!
> > >
> > > --Yakov
> > >
> > > 2016-02-24 18:12 GMT+03:00 Denis Magda :
> > >
> > > > I would add support of the binary mode for distributed data
> structures
> > > and
> > > > atomic references
> > > > https://issues.apache.org/jira/browse/IGNITE-2701
> > > >
> > > > Is anyone interested to pick up this task and implement?
> > > >
> > > > --
> > > > Denis
> > > >
> > > >
> > > > On 2/18/2016 1:36 PM, Vladimir Ozerov wrote:
> > > >
> > > >> I would definitely want to include NuGet and ODBC into upcoming
> > release.
> > > >> Both issues are in review for now. I expect they will be in master
> in
> > a
> > > >> week or so.
> > > >>
> > > >> LINQ is "nice to have" for me for this release. It changes .NET
> > > packaging
> > > >> and moreover must be tested very thoroughly. So it would be cool to
> > > >> include
> > > >> it as well, but I do not think it is a showstopper for 1.6.
> > > >>
> > > >> On Thu, Feb 18, 2016 at 12:47 PM, Pavel Tupitsyn <
> > > ptupit...@gridgain.com>
> > > >> wrote:
> > > >>
> > > >> There are some important .NET features on review, like LINQ and
> NuGet:
> > > >>> https://issues.apache.org/jira/browse/IGNITE-1630
> > > >>> https://issues.apache.org/jira/browse/IGNITE-1626
> > > >>>
> > > >>> Vova can clarify which of them are going to be included in 1.6.
> > > >>>
> > > >>> Thanks,
> > > >>>
> > > >>>
> > > >>> On Thu, Feb 18, 2016 at 12:42 PM, Alexey Goncharuk <
> > > >>> alexey.goncha...@gmail.com> wrote:
> > > >>>
> > > >>> Yakov,
> > > 
> > >  Nothing major from my side is planned for 1.6. There is a ticket
> > >  IGNITE-2610 that I am currently working on (it is almost
> finished),
> > > but
> > >  I
> > >  believe it does not make any restrictions for the schedule.
> > > 
> > > 
> > > >>>
> > > >>> --
> > > >>> --
> > > >>> Pavel Tupitsyn
> > > >>> GridGain Systems, Inc.
> > > >>> www.gridgain.com
> > > >>>
> > > >>>
> > > >
> > >
> >
>

[GitHub] ignite pull request: IGNITE-2844 .NET: Implement ICache.LoadAll

2016-03-19 Thread ptupitsyn 
GitHub user ptupitsyn opened a pull request:

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

IGNITE-2844 .NET: Implement ICache.LoadAll



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

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

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

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


commit 125631b041951ffdac21f58b51eb0ded5c4870af
Author: Pavel Tupitsyn 
Date:   2016-03-16T13:33:01Z

IGNITE-2844 .NET: ICache.LoadAll method is missing

commit d06209b4ec9e11e10988b9f810897360f7de9b16
Author: Pavel Tupitsyn 
Date:   2016-03-17T07:48:56Z

Merge remote-tracking branch 'remotes/upstream/master' into ignite-2844

commit c788d96340191cf65189449e946ccc6a3aed4274
Author: Pavel Tupitsyn 
Date:   2016-03-17T09:35:22Z

wip

commit a304ddd283b0994be348f08df45db51371e6fce6
Author: Pavel Tupitsyn 
Date:   2016-03-17T09:39:51Z

wip

commit 55601dcf9657c67c96237728a51408a47596f6e5
Author: Pavel Tupitsyn 
Date:   2016-03-17T10:40:43Z

wip

commit ee5af2ec83a00ec4a9e8a6cb5aa6f89cb9b28091
Author: Pavel Tupitsyn 
Date:   2016-03-17T10:44:20Z

wip

commit 55d3008228a0e61b2eab5db88505d1c84752f4c1
Author: Pavel Tupitsyn 
Date:   2016-03-17T10:49:03Z

test added

commit b5fd8e05baa1a314bdc2a74d7da2925b84ac8c01
Author: Pavel Tupitsyn 
Date:   2016-03-17T11:36:50Z

wip

commit 885b838f37a4734d455234ae5d04ac232c08483b
Author: Pavel Tupitsyn 
Date:   2016-03-17T11:41:59Z

wip

commit 1566b6c6bf6e5af6d336cdd016d342e1e43e955c
Author: Pavel Tupitsyn 
Date:   2016-03-17T12:03:43Z

Fix test store

commit 23828c062a0cbecf086b4bedcf0ee5d980d80846
Author: Pavel Tupitsyn 
Date:   2016-03-17T12:11:41Z

cleanup

commit 798881220721901335c42b6551984f0498a766f8
Author: Pavel Tupitsyn 
Date:   2016-03-17T12:16:38Z

wip tests

commit 098bc0fd018c0cb29b15a7c2c89e773e5e21489f
Author: Pavel Tupitsyn 
Date:   2016-03-17T12:20:31Z

wip

commit ddf06659f3c7724eeaff9ba46f17a2a49cda2fb2
Author: Pavel Tupitsyn 
Date:   2016-03-17T15:16:35Z

Fix overwrite test




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

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

2016-03-19 Thread Dmitriy Setrakyan 
On Fri, Mar 18, 2016 at 7:57 AM, Vladisav Jelisavcic 
wrote:

> Hi Yakov,
>
> yes, thanks for the comments, I think everything should be ok now,
> please review the PR and tell me if you think anything else is needed.
>
> Once ignite-642 is merged into master,
> I'll submit a PR for IgniteReadWriteLock (hopefully on time for 1.6.
> release).
>

This would be awesome :)


>
> Best regrads,
> Vladisav
>
>
>
> On Fri, Mar 18, 2016 at 11:56 AM, Yakov Zhdanov 
> wrote:
>
> > Vlad, did you have a chance to review my latest comments?
> >
> > Thanks!
> > --
> > Yakov Zhdanov, Director R
> > *GridGain Systems*
> > www.gridgain.com
> >
> > 2016-03-06 12:21 GMT+03:00 Yakov Zhdanov :
> >
> > > Vlad and all (esp Val and Anton V.),
> > >
> > > I reviewed the PR. My comments are in the ticket.
> > >
> > > Anton V. there is a question regarding optimized-classnames.properties.
> > > Can you please respond in ticket?
> > >
> > >
> > > --Yakov
> > >
> > > 2016-02-29 16:00 GMT+06:00 Yakov Zhdanov :
> > >
> > >> Vlad, that's great! I will take a look this week. Reassigning ticket
> to
> > >> myself.
> > >>
> > >> --Yakov
> > >>
> > >> 2016-02-26 18:37 GMT+03:00 Vladisav Jelisavcic :
> > >>
> > >>> Hi,
> > >>>
> > >>> i recently implemented distributed ReentrantLock - IGNITE-642,
> > >>> i made a pull request, so hopefully this could be added to the next
> > >>> release.
> > >>>
> > >>> Best regards,
> > >>> Vladisav
> > >>>
> > >>> On Thu, Feb 18, 2016 at 10:49 AM, Alexey Goncharuk <
> > >>> alexey.goncha...@gmail.com> wrote:
> > >>>
> > >>> > Folks,
> > >>> >
> > >>> > The current implementation of IgniteCache.lock(key).lock() has the
> > same
> > >>> > semantics as the transactional locks - cache topology cannot be
> > changed
> > >>> > while there exists an ongoing transaction or an explicit lock is
> > held.
> > >>> The
> > >>> > restriction for transactions is quite fundamental, the lock() issue
> > >>> can be
> > >>> > fixed if we re-implement locking the same way IgniteSemaphore
> > currently
> > >>> > works.
> > >>> >
> > >>> > As for the "Failed to find semaphore with the given name" message,
> my
> > >>> first
> > >>> > guess is that DataStructures were configured with 1 backups which
> led
> > >>> to
> > >>> > the data loss when two nodes were stopped. Mario, can you please
> > >>> re-test
> > >>> > your semaphore scenario with 2 backups configured for data
> > structures?
> > >>> > From my side, I can also take a look at the semaphore issue when
> I'm
> > >>> done
> > >>> > with IGNITE-2610.
> > >>> >
> > >>>
> > >>
> > >>
> > >
> >
>