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

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

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

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

[jira] [Created] (IGNITE-1369) CacheClientPortableQueryExample need to update javadoc

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

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

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

[GitHub] ignite pull request: FIx Log4j2LoggerSelfTest.testLogFilesTwoNodes...

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

Re: Ignite 1.4

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,

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

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

Re: Ignite 1.4

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

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

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

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

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

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

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:

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

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

Update version for master

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

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

Re: QueryProcessor and CacheProcessor start order

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

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

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

QueryProcessor and CacheProcessor start order

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

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

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

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

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

Re: Update version for master

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

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

Re: Update version for master

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

Re: Update version for master

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

Re: Update version for master

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

Re: Update version for master

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

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

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

Re: Ignite still showing as incubating in ASF Git

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

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

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

Ignite Teamcity at Apache side

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.

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

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

Re: Ignite Teamcity at Apache side

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

Re: Portable objects

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

Re: Update version for master

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?

Re: Update version for master

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

Re: Update version for master

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

Ignite still showing as incubating in ASF Git

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*