[GitHub] ignite pull request: IGNITE-1348 Move .Net platform from GridGain ...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-1348 Move .Net platform from GridGain to Ignite.



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

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

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

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


commit c2eb83ec4e9f76447e3d455936dd81c0394345ba
Author: Pavel Tupitsyn 
Date:   2015-08-24T14:40:29Z

Merge pull request #1 from apache/master

IGNITE-1286: .Net solution and project skeletons.

commit 29c6d1e6dcbe4438078465872b8c6926212fcc43
Author: Pavel Tupitsyn 
Date:   2015-08-25T07:24:23Z

Merge pull request #2 from apache/master

Merging from main repo

commit 51bc2ecd613256d648db340b15b19494d96a7ceb
Author: ptupitsyn 
Date:   2015-08-25T10:03:43Z

Merge remote-tracking branch 'upstream/master'

commit 811b2e2024ede38c7fe8472a3d1002c2c65061fb
Author: ptupitsyn 
Date:   2015-08-25T13:38:48Z

Merge remote-tracking branch 'remotes/upstream/master'

commit 18c06b6dcb2c79a823dc044ed17c96253781ed99
Author: ptupitsyn 
Date:   2015-08-25T13:43:44Z

Merge remote-tracking branch 'remotes/upstream/master'

commit db209709dbed9d0ea0be9272e4b5136162508d36
Author: ptupitsyn 
Date:   2015-08-26T08:29:20Z

Merge remote-tracking branch 'remotes/upstream/master'

commit 3ae21f8f84ea26a0adab24ba7d5ee20d42a17164
Author: ptupitsyn 
Date:   2015-08-26T09:13:39Z

Merge remote-tracking branch 'remotes/upstream/master'

commit 9e29394c9b6a26839d88453a68671f32acc097c9
Author: ptupitsyn 
Date:   2015-08-26T09:55:45Z

Merge remote-tracking branch 'remotes/upstream/master'

commit b1fe45d2bb1f4f350c860cdd0557d75ead90a972
Author: ptupitsyn 
Date:   2015-08-26T13:01:10Z

Merge remote-tracking branch 'remotes/upstream/master'

commit 005ade0375aa6d32243f4a5562149186305113d0
Author: ptupitsyn 
Date:   2015-08-26T13:05:15Z

Merge remote-tracking branch 'remotes/upstream/master'

commit 20043f3534a5e8d7457f4f025b30d5b23385279a
Author: ptupitsyn 
Date:   2015-08-27T08:09:52Z

Merge remote-tracking branch 'remotes/upstream/master'

commit ac81c42f0a7247a838c589c095485930d59a0b35
Author: ptupitsyn 
Date:   2015-08-27T08:44:51Z

Merge remote-tracking branch 'remotes/upstream/master'

commit 486c624b3490031c7f892281287bfb5c90793c27
Author: ptupitsyn 
Date:   2015-08-27T10:07:28Z

Merge remote-tracking branch 'remotes/upstream/master'

commit 56736a8fc96c924b3aff6badff90e8481947515a
Author: ptupitsyn 
Date:   2015-08-27T10:33:37Z

Merge remote-tracking branch 'remotes/upstream/master'

commit 1cfcb497d03d75e654b3f9976a6e8d2683d0e207
Author: ptupitsyn 
Date:   2015-08-31T13:03:30Z

Merge remote-tracking branch 'remotes/upstream/master'

commit e0bc5b930b6f0ffba3cd9826011609bb8b454366
Author: ptupitsyn 
Date:   2015-09-01T11:35:35Z

Merge remote-tracking branch 'remotes/upstream/master'

commit 1fa2632375176610ca7f6dfd8d925d9062801098
Author: ptupitsyn 
Date:   2015-09-01T11:42:53Z

Merge remote-tracking branch 'remotes/upstream/master'

commit 0877d97726e6f43934dacc23ba38843195d7dce5
Author: ptupitsyn 
Date:   2015-09-01T13:44:26Z

Merge remote-tracking branch 'remotes/upstream/master'

commit d0bacad6d55916be95588c3267a661cee07772a3
Author: ptupitsyn 
Date:   2015-09-01T14:01:39Z

Merge remote-tracking branch 'remotes/upstream/master'

commit f63e6b59c0aad8b8b64b7c58e98df87341ce6598
Author: ptupitsyn 
Date:   2015-09-01T15:07:58Z

Merge remote-tracking branch 'remotes/upstream/master'

commit 4c6d1d9fb149af1230c98a2596e1f40bf5d2da34
Author: ptupitsyn 
Date:   2015-09-01T15:11:45Z

IGNITE-1350 Platforms .Net: Add common cpp project to the solution

commit b6b425fc00765ce1edc7c3471b16a271f7dabf40
Author: ptupitsyn 
Date:   2015-09-01T15:39:19Z

wip

commit ed5fa2f6af06910bc0da0640ef85bc94f4f307ca
Author: ptupitsyn 
Date:   2015-09-01T16:35:28Z

Adding files

commit 80bc24bb4d972041b5f7bbff6110fba0d0981532
Author: ptupitsyn 
Date:   2015-09-01T16:49:01Z

Build fixed

commit af5c2a5cb6001240b050345e6ffdab92f8f88a35
Author: ptupitsyn 
Date:   2015-09-01T17:13:34Z

Added tests

commit 

[GitHub] ignite pull request: IGNITE-1344: Fixed imports at java8-examples

[ashutakGG]

Github user ashutakGG closed the pull request at:

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


---
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-1369) CacheClientPortableQueryExample need to update javadoc

[Vasilisa Sidorova (JIRA)]

Vasilisa  Sidorova created IGNITE-1369:
--

 Summary: CacheClientPortableQueryExample need to update javadoc
 Key: IGNITE-1369
 URL: https://issues.apache.org/jira/browse/IGNITE-1369
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.1.4
Reporter: Vasilisa  Sidorova
Priority: Minor


CacheClientPortableQueryExample fails with exception:
{noformat}
Exception in thread "main" org.apache.ignite.cache.CacheExistsException: Failed 
to start cache (a cache with the same name is already started): 
CacheClientPortableQueryExampleOrganizations
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2133)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2094)
at 
org.apache.ignite.internal.IgniteKernal.createCache(IgniteKernal.java:2392)
at 
org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:87)
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:134)
{noformat}
if it's running with node from command line. And 
CacheClientPortableQueryExample is running OK with GridExampleNodeStartup. So, 
it's need to delete text:
{noformat}
* Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM 
which will
 * start node with {@code examples/config/portable/example-ignite-portable.xml} 
configuration.
{noformat}
from example description



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

[GitHub] ignite pull request: Experiments (tmp PR)

[ashutakGG]

GitHub user ashutakGG opened a pull request:

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

 Experiments (tmp PR)

Tmp PR.

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

$ git pull https://github.com/ashutakGG/incubator-ignite 
IgniteCacheSslStartStopSelfTest-experim

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

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


commit 0cba13cc0bfcada072925a15e7cdf79752c6b783
Author: ashutak 
Date:   2015-09-03T10:54:22Z

ignite-1344: Fixed imports at java8-examples

commit 5463df29a5e7c5d2ad7e583fc77d5c1ed38cc5f2
Author: vozerov-gridgain 
Date:   2015-09-03T11:28:07Z

Fixing platform JavaDocs.

commit 7f4c9ace076ba4e0be5a97bc61a655b8ec11c363
Author: vozerov-gridgain 
Date:   2015-09-03T11:28:33Z

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

commit 66a49d75e3cdd001135f32a81dbfb931b9e1584b
Author: sboikov 
Date:   2015-09-03T12:32:26Z

Disabled hanging tests.

commit c5d303bac7a9b17f88260b1bde175fbfbc053988
Author: sboikov 
Date:   2015-09-03T12:34:47Z

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

commit 6a5a48a0c9e379ecf83c8a799d0d8e2397fe5b3c
Author: Denis Magda 
Date:   2015-09-03T13:59:36Z

ignite-1351: moved portable API examples to Ignite except cross-platform 
example

commit 2fbf328b3f5fd08f7d24d2a0dab6e482192281ad
Author: Anton Vinogradov 
Date:   2015-09-03T15:34:38Z

Topology validator test and javadoc improvement

commit 154f18588e01943bfde60ade49262837bb670204
Author: Anton Vinogradov 
Date:   2015-09-03T15:35:06Z

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

commit 8901575e14f7334874d630ae685db624d00dcc7f
Author: Artem Shutak 
Date:   2015-09-03T15:57:47Z

Log4j2LoggerSelfTest.testLogFilesTwoNodes test case for Windows.

commit 011481a557591da6446ab8d708cfeeaaa5daa1f6
Author: ashutak 
Date:   2015-09-03T18:10:57Z

add debug info




---
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: FIx Log4j2LoggerSelfTest.testLogFilesTwoNodes...

[ashutakGG]

Github user ashutakGG closed the pull request at:

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


---
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: Ignite 1.4

[Dmitriy Setrakyan]

On Thu, Sep 3, 2015 at 1:31 AM, Sergey Kozlov  wrote:

> Could someone provide the list of key features (fixes) added for release
> 1.4?
>

I would also like to see the release notes for 1.4.

Also, is the release still happening tomorrow? How close are we?


>
>
> On Wed, Sep 2, 2015 at 3:51 PM, Yakov Zhdanov  wrote:
>
> > Yes, we will be moving almost all the issues to further versions.
> >
> > Branch has already been created.
> >
> > --Yakov
> >
> > 2015-09-01 22:14 GMT+03:00 Branko Čibej :
> >
> > > On 01.09.2015 20:46, Konstantin Boudnik wrote:
> > > > On Tue, Sep 01, 2015 at 08:45PM, Sergey Kozlov wrote:
> > > >> FYI: We've at least 161 unclosed issues planned to fix in version
> 1.4
> > > > If there're so many issues to go - perhaps it makes sense not to
> branch
> > > out
> > > > this early to avoid extra merges?
> > >
> > > Or just go ahead and release 1.4 and get those issues addressed in 1.5.
> > > It's not as if skipping a  "planned to fix" issue would be the end of
> > > the world.
> > >
> > > -- Brane
> > >
> > >
> >
>
>
>
> --
> Sergey Kozlov
>

[GitHub] ignite pull request: Ignite 1273: Tests from GridPortableBuilderAd...

[dmagda]

Github user dmagda closed the pull request at:

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


---
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: Ignite 1.4

[Sergey Kozlov]

Could someone provide the list of key features (fixes) added for release
1.4?


On Wed, Sep 2, 2015 at 3:51 PM, Yakov Zhdanov  wrote:

> Yes, we will be moving almost all the issues to further versions.
>
> Branch has already been created.
>
> --Yakov
>
> 2015-09-01 22:14 GMT+03:00 Branko Čibej :
>
> > On 01.09.2015 20:46, Konstantin Boudnik wrote:
> > > On Tue, Sep 01, 2015 at 08:45PM, Sergey Kozlov wrote:
> > >> FYI: We've at least 161 unclosed issues planned to fix in version 1.4
> > > If there're so many issues to go - perhaps it makes sense not to branch
> > out
> > > this early to avoid extra merges?
> >
> > Or just go ahead and release 1.4 and get those issues addressed in 1.5.
> > It's not as if skipping a  "planned to fix" issue would be the end of
> > the world.
> >
> > -- Brane
> >
> >
>



-- 
Sergey Kozlov

[jira] [Created] (IGNITE-1362) Update notifier causes Ignite instance leak.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1362:
---

 Summary: Update notifier causes Ignite instance leak.
 Key: IGNITE-1362
 URL: https://issues.apache.org/jira/browse/IGNITE-1362
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.1.4
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Critical
 Fix For: ignite-1.4


IgniteKernal has private non-static anonymous class for GridTimerTask which 
forces üpdate notify. 
As a result IgniteKernal instance leaks to it and stays in memory for a long 
time even after node is stopped.



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

[jira] [Created] (IGNITE-1365) Unable to deserialize object because class ID key is not in the cache

[Denis Magda (JIRA)]

Denis Magda created IGNITE-1365:
---

 Summary: Unable to deserialize object because class ID key is not 
in the cache
 Key: IGNITE-1365
 URL: https://issues.apache.org/jira/browse/IGNITE-1365
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: ignite-1.4
Reporter: Denis Magda
Priority: Critical


There is a test that fails because of object deserialization issue:
http://204.14.53.153/viewLog.html?buildId=65291=buildResultsDiv=Ignite_IgniteBasic#testNameId7413691472559096192

According to the log, the reason of the failure is the following:
{noformat}
Caused by: class 
org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException: 
Failed to map keys for cache (all partition nodes left the grid).
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.map(GridPartitionedGetFuture.java:308)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.init(GridPartitionedGetFuture.java:199)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.getAllAsync0(GridDhtAtomicCache.java:1048)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1300(GridDhtAtomicCache.java:124)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$10.apply(GridDhtAtomicCache.java:336)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$10.apply(GridDhtAtomicCache.java:334)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:648)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.getAllAsync(GridDhtAtomicCache.java:334)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.getTopologySafe(GridCacheAdapter.java:1345)
at 
org.apache.ignite.internal.MarshallerContextImpl.className(MarshallerContextImpl.java:148)
at 
org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:174)
at 
org.apache.ignite.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:256)
{noformat}

However, if to take a look at the test code we will see that this situation is 
impossible: all the nodes should be alive during the test's execution.

It means that the issue is somewhere in {{GridCacheAdapter.getTopologySafe}} 
implementation.



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

[jira] [Created] (IGNITE-1363) Add animations for angular strap elements.

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-1363:
-

 Summary: Add animations for angular strap elements.
 Key: IGNITE-1363
 URL: https://issues.apache.org/jira/browse/IGNITE-1363
 Project: Ignite
  Issue Type: Sub-task
  Components: UI
Affects Versions: ignite-1.4
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko
Priority: Minor
 Fix For: ignite-1.4


Tooltip, popover, popup, modal.



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

[jira] [Created] (IGNITE-1364) Move C++ platform to Ignite.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-1364:
---

 Summary: Move C++ platform to Ignite.
 Key: IGNITE-1364
 URL: https://issues.apache.org/jira/browse/IGNITE-1364
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Affects Versions: 1.1.4
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Critical
 Fix For: ignite-1.5


This involves:
1) Moving code base;
2) Moving examples;
3) Fixing doxygen docs generation.



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

Update version for master

[Sergey Kozlov]

Hi

Now we've branch ignite-1.4 for release thus make sense to update for
version for master to 1.5?

-- 
Sergey Kozlov

Re: SVN changes

[Dmitriy Setrakyan]

Thanks, Brane. I think upgrading the client solved the issue. I will keep
an eye on it.

D.

On Wed, Sep 2, 2015 at 11:24 PM, Branko Čibej  wrote:

> On 02.09.2015 21:58, Dmitriy Setrakyan wrote:
> > On Wed, Sep 2, 2015 at 2:53 AM, Branko Čibej  wrote:
> >> Also, any info about the platform you're using, and what kind of
> >> authentication store you're using (KWallet? Gnome Keyring? OSX
> >> Keychain?) would be useful here.
> >>
> > I am running on Mac. To my knowledge I am not using any authentication
> > store.
>
> Keychain is probably enabled, but it doesn't usually play a role in
> trusting the server (public) certificate. You're using the default svn
> on OSX which is hacked a bit ... in fact so much that I can't find where
> it's storing the server cert :)
>
> In any case: I wasn't able to reproduce what you describe, using
> /usr/bin/svn; it did ask about trusting the cert the first time, and
> apparently recorded that *somewhere*.
>
> > I should also mention that this started happening after Apache SVN was
> > upgraded to a newer version recently.
>
> I expect it started happening when Infra replaced the server certs;
> that's more likely, since trusting the cert is a completely client-side
> decision.
>
> If you use Homebrew, I suggest you 'brew install subversion' which will
> (currently) give you 1.8.14.
>
> -- Brane
>

Re: QueryProcessor and CacheProcessor start order

[Sergi Vladykin]

I think it was because caches configured on start must be able to setup SQL
schema, so QueryProcessor must be ready.
If this not true anymore, then the order can be changed.

Sergi

2015-09-03 13:20 GMT+03:00 Yakov Zhdanov :

> Sam, I agree. Please try fix components start order and run tests.
>
> --
> Yakov Zhdanov, Director R
> *GridGain Systems*
> www.gridgain.com
>
> 2015-09-03 12:40 GMT+03:00 Semyon Boikov :
>
> > Does anybody remember why QueryProcessor is started before
> CacheProcessor?
> >
> > With this order cache processor can be stopped at the moment when query
> > request is processed, and this causes sporadic errors like NPE (I see
> this
> > from time to time in IgniteCacheQueryNodeRestartSelfTest).
> >
> > Looks like cache processor does not depend on query processor so start
> > order should be changed.
> >
>

[GitHub] ignite pull request: IGNITE-1344: Fixed imports at java8-examples

[ashutakGG]

GitHub user ashutakGG opened a pull request:

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

IGNITE-1344: Fixed imports at java8-examples

Fixed imports at java8-examples

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

$ git pull https://github.com/ashutakGG/incubator-ignite 
ignite-1344-java8-examples

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

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


commit 0cba13cc0bfcada072925a15e7cdf79752c6b783
Author: ashutak 
Date:   2015-09-03T10:54:22Z

ignite-1344: Fixed imports at java8-examples




---
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.
---

QueryProcessor and CacheProcessor start order

[Semyon Boikov]

Does anybody remember why QueryProcessor is started before CacheProcessor?

With this order cache processor can be stopped at the moment when query
request is processed, and this causes sporadic errors like NPE (I see this
from time to time in IgniteCacheQueryNodeRestartSelfTest).

Looks like cache processor does not depend on query processor so start
order should be changed.

[jira] [Created] (IGNITE-1366) Start CacheProcessor before QueryProcessor

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-1366:


 Summary: Start CacheProcessor before QueryProcessor
 Key: IGNITE-1366
 URL: https://issues.apache.org/jira/browse/IGNITE-1366
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Semen Boikov
Assignee: Semen Boikov
Priority: Critical
 Fix For: ignite-1.5


Now QueryProcessor is started before CacheProcessor. With this order cache 
processor can be stopped at the moment when query request is processed, and 
this causes sporadic errors like NPE (I see this from time to time in 
IgniteCacheQueryNodeRestartSelfTest).

Looks like cache processor does not need QueryProcessor when it's 'start' 
method is called so I think start order should be changed. 



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

[GitHub] ignite pull request: ignite-1351: move portable API examples

[dmagda]

Github user dmagda closed the pull request at:

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


---
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: Update version for master

[Yakov Zhdanov]

Anton V, can you please do it?

--Yakov

2015-09-03 12:05 GMT+03:00 Sergey Kozlov :

> Hi
>
> Now we've branch ignite-1.4 for release thus make sense to update for
> version for master to 1.5?
>
> --
> Sergey Kozlov
>

Re: QueryProcessor and CacheProcessor start order

[Yakov Zhdanov]

Sam, I agree. Please try fix components start order and run tests.

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

2015-09-03 12:40 GMT+03:00 Semyon Boikov :

> Does anybody remember why QueryProcessor is started before CacheProcessor?
>
> With this order cache processor can be stopped at the moment when query
> request is processed, and this causes sporadic errors like NPE (I see this
> from time to time in IgniteCacheQueryNodeRestartSelfTest).
>
> Looks like cache processor does not depend on query processor so start
> order should be changed.
>

Re: Update version for master

[Raul Kripalani]

If development of the 1.4.x release line will continue in the ignite-1.4
branch, the master/develop branch should carry 1.5.0-SNAPSHOT (or
2.0.0-SNAPSHOT, depending on the type of changes expected).

BTW - it seems the tag for ignite-1.4.0 is missing:

$ git fetch --tags
$ git tag -l
1.1.3
1.1.4
1.3.1
1.3.2
1.3.2-p2
1.3.3
1.3.3-p1
1.3.3-p2
1.3.3-p3
1.3.3-p4
1.3.3-p5
1.3.3-p6
1.3.3-rc1
ignite-1.0.0
ignite-1.0.1
ignite-1.0.2
ignite-1.0.6-incubating
ignite-1.1.0-incubating
ignite-1.1.0-incubating-rc1
ignite-1.1.0-incubating-rc2
ignite-1.1.0-incubating-rc3
ignite-1.1.0-incubating-rc4
ignite-1.1.0-incubating-rc5
ignite-1.1.0-incubating-rc6
ignite-1.1.0-incubating-rc7
ignite-1.2.0-incubating
ignite-1.2.0-incubating-rc1
ignite-1.2.0-incubating-rc2
ignite-1.3.0-incubating
ignite-1.3.0-incubating-rc1
ignite-1.3.0-incubating-rc2
release-1.0.0-RC1
release-1.0.0-RC2
release-1.0.0-RC3
$

*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Thu, Sep 3, 2015 at 12:16 PM, Anton Vinogradov 
wrote:

> Should it be 1.5.0-SNAPSHOT?
>
> On Thu, Sep 3, 2015 at 1:32 PM, Yakov Zhdanov  wrote:
>
> > Anton V, can you please do it?
> >
> > --Yakov
> >
> > 2015-09-03 12:05 GMT+03:00 Sergey Kozlov :
> >
> > > Hi
> > >
> > > Now we've branch ignite-1.4 for release thus make sense to update for
> > > version for master to 1.5?
> > >
> > > --
> > > Sergey Kozlov
> > >
> >
>

Re: Update version for master

[Yakov Zhdanov]

Yes. Correct.
On Sep 3, 2015 14:16, "Anton Vinogradov"  wrote:

> Should it be 1.5.0-SNAPSHOT?
>
> On Thu, Sep 3, 2015 at 1:32 PM, Yakov Zhdanov  wrote:
>
> > Anton V, can you please do it?
> >
> > --Yakov
> >
> > 2015-09-03 12:05 GMT+03:00 Sergey Kozlov :
> >
> > > Hi
> > >
> > > Now we've branch ignite-1.4 for release thus make sense to update for
> > > version for master to 1.5?
> > >
> > > --
> > > Sergey Kozlov
> > >
> >
>

Re: Update version for master

[Branko Čibej]

On 03.09.2015 13:47, Raul Kripalani wrote:
> If development of the 1.4.x release line will continue in the ignite-1.4
> branch, the master/develop branch should carry 1.5.0-SNAPSHOT (or
> 2.0.0-SNAPSHOT, depending on the type of changes expected).
>
> BTW - it seems the tag for ignite-1.4.0 is missing:

There hasn't been a 1.4.0 release package yet, so of course no tag?

-- Brane

Re: Update version for master

[Anton Vinogradov]

Should it be 1.5.0-SNAPSHOT?

On Thu, Sep 3, 2015 at 1:32 PM, Yakov Zhdanov  wrote:

> Anton V, can you please do it?
>
> --Yakov
>
> 2015-09-03 12:05 GMT+03:00 Sergey Kozlov :
>
> > Hi
> >
> > Now we've branch ignite-1.4 for release thus make sense to update for
> > version for master to 1.5?
> >
> > --
> > Sergey Kozlov
> >
>

[jira] [Created] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore

[Alexandre Boudnik (JIRA)]

Alexandre Boudnik created IGNITE-1371:
-

 Summary: Key-Value store (like Cassandra) as CacheStore
 Key: IGNITE-1371
 URL: https://issues.apache.org/jira/browse/IGNITE-1371
 Project: Ignite
  Issue Type: New Feature
  Components: cache
Reporter: Alexandre Boudnik
Assignee: Alexandre Boudnik






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

Re: Ignite still showing as incubating in ASF Git

[Konstantin Boudnik]

I believe an INFRA ticket needs to be filed for this.

On Thu, Sep 03, 2015 at 01:36PM, Raul Kripalani wrote:
> Hey guys,
> 
> Not sure if you're aware and already working on it, but searching the ASF
> Git still shows Ignite as incubating:
> 
> 
> https://git-wip-us.apache.org/repos/asf?a=project_list=ignite=Search
> 
> I guess it still needs to be changed in some descriptor file somewhere.
> 
> Regards,
> 
> *Raúl Kripalani*
> Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
> Integration specialist
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk

[GitHub] ignite pull request: IGNITE-1370 Streamers: Implement multiple tup...

[raulk]

GitHub user raulk opened a pull request:

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

IGNITE-1370 Streamers: Implement multiple tuple extractor.

Added also a unit test in SocketStreamerSelfTest. 

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

$ git pull https://github.com/raulk/incubator-ignite ignite-1.4

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

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


commit 36467a027fa95ba6587ada721155e1d0479e1808
Author: Raul Kripalani 
Date:   2015-09-03T22:31:08Z

IGNITE-1370 Streamers: Implement multiple tuple extractor.




---
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.
---

Ignite Teamcity at Apache side

[Anton Vinogradov]

Hello,

As you may know we already have Ignite Teamcity server where contributors
can check it's patches. But, as Cos said before, this test environment
should be runned under apache hardware.

Apache test environment based on Jenkins, but it is not so simple to
migrate from TeamCity to Jenkins.

Is it possible to make Ignite test environment at Apache side using
TeamCity, not Jenkins?
TeamCity can be used under opensource license (
https://www.jetbrains.com/teamcity/buy/opensource.html).

[GitHub] ignite pull request: ignite-1334 Fixed concurrent destroyCache/nod...

[sboikov]

Github user sboikov closed the pull request at:

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


---
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: Ignite Teamcity at Apache side

[Branko Čibej]

On 03.09.2015 15:11, Anton Vinogradov wrote:
> Hello,
>
> As you may know we already have Ignite Teamcity server where contributors
> can check it's patches. But, as Cos said before, this test environment
> should be runned under apache hardware.
>
> Apache test environment based on Jenkins, but it is not so simple to
> migrate from TeamCity to Jenkins.
>
> Is it possible to make Ignite test environment at Apache side using
> TeamCity, not Jenkins?
> TeamCity can be used under opensource license (
> https://www.jetbrains.com/teamcity/buy/opensource.html).

There are two ways to do this:

  * Ask Infra (in JIRA or mail) to provide a TeamCity instance on our
infrastructure. This is far more likely to succeed if several PMCs
make the request.
  * Ask Infra to set up a VM for Ignite and manage a dedicated instance.

The first option is by far preferred, but be aware that Infra has very
limited resources.

-- Brane

Re: Portable objects

[Denis Magda]

To be more specific public Portable API is located in the following 
packages:
- org.apache.ignite.marshaller.portable package (contains 
PortableMarshaller only);
- org.apache.ignite.portable package (PortableObject, PortableBuilder, 
PortableMetadata, etc.);

- IgnitePortables interface is placed into org.apache.ignite;

New methods are added to some existed public interfaces:
- Ignite.portables() - returns reference to IgnitePortables interface impl;
- IgniteCache.withKeepPortable() - returns cache instance with 
'keepPortable' flag enabled;
- CacheConfiguration.isKeepPortableInStore()/setKeepPortableInStore() - 
controls 'keepPortableInStore' flag.


Portable API examples should be merged shortly to 1.4 branch.

--
Denis

On 9/3/2015 8:02 AM, Denis Magda wrote:

Val,

Yes, the portable API and its implementation is already a part of both 
master and 1.4 branches.


--
Denis

On 9/2/2015 11:54 PM, Valentin Kulichenko wrote:

Igniters,

Are portable objects already migrated and will be released as a part 
of 1.4
(I see that APIs and configuration changes are already in master)? I 
just

thought it's a pretty big change and we were going to include it only in
1.5, correct me if I'm wrong.

-Val

Re: Update version for master

[Raul Kripalani]

On Thu, Sep 3, 2015 at 1:16 PM, Branko Čibej  wrote:

> There hasn't been a 1.4.0 release package yet, so of course no tag?
>

Well, that would explain it ;-) But why is the POM version for both master
and ignite-1.4 branches already on 1.4.1-SNAPSHOT in that case?

https://github.com/apache/ignite/blob/master/pom.xml#L35
https://github.com/apache/ignite/blob/ignite-1.4/pom.xml#L35

Is the 1.4.0 release cut and under VOTE?

Regards,

*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

Re: Update version for master

[Branko Čibej]

On 03.09.2015 14:29, Raul Kripalani wrote:
> On Thu, Sep 3, 2015 at 1:16 PM, Branko Čibej  wrote:
>
>> There hasn't been a 1.4.0 release package yet, so of course no tag?
>>
> Well, that would explain it ;-) But why is the POM version for both master
> and ignite-1.4 branches already on 1.4.1-SNAPSHOT in that case?
>
> https://github.com/apache/ignite/blob/master/pom.xml#L35
> https://github.com/apache/ignite/blob/ignite-1.4/pom.xml#L35

No idea ... possibly an oversight.


> Is the 1.4.0 release cut and under VOTE?

I don't see any vote mail, so my best guess is, nope.

-- Brane

Re: Update version for master

[Anton Vinogradov]

Version Updated

On Thu, Sep 3, 2015 at 3:29 PM, Raul Kripalani  wrote:

> On Thu, Sep 3, 2015 at 1:16 PM, Branko Čibej  wrote:
>
> > There hasn't been a 1.4.0 release package yet, so of course no tag?
> >
>
> Well, that would explain it ;-) But why is the POM version for both master
> and ignite-1.4 branches already on 1.4.1-SNAPSHOT in that case?
>
> https://github.com/apache/ignite/blob/master/pom.xml#L35
> https://github.com/apache/ignite/blob/ignite-1.4/pom.xml#L35
>
> Is the 1.4.0 release cut and under VOTE?
>
> Regards,
>
> *Raúl Kripalani*
> Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
> Integration specialist
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>

Ignite still showing as incubating in ASF Git

[Raul Kripalani]

Hey guys,

Not sure if you're aware and already working on it, but searching the ASF
Git still shows Ignite as incubating:


https://git-wip-us.apache.org/repos/asf?a=project_list=ignite=Search

I guess it still needs to be changed in some descriptor file somewhere.

Regards,

*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk