Re: vert.x integration

I'm working on cache issues blocking vert.x integration, there is one more issue reproducing in vert.x tests: https://issues.apache.org/jira/browse/IGNITE-1534. Hopefully these issues will be fixed within the next few days. On Wed, Sep 30, 2015 at 9:06 PM, Dmitriy Setrakyan wrote: > Igniters, >

[jira] [Created] (IGNITE-1596) Web console agent improvements

Dmitriy Setrakyan created IGNITE-1596: - Summary: Web console agent improvements Key: IGNITE-1596 URL: https://issues.apache.org/jira/browse/IGNITE-1596 Project: Ignite Issue Type: Sub-tas

[jira] [Created] (IGNITE-1595) Web Console chart refresh functionality

Dmitriy Setrakyan created IGNITE-1595: - Summary: Web Console chart refresh functionality Key: IGNITE-1595 URL: https://issues.apache.org/jira/browse/IGNITE-1595 Project: Ignite Issue Type

[jira] [Created] (IGNITE-1594) Home page for web console

Dmitriy Setrakyan created IGNITE-1594: - Summary: Home page for web console Key: IGNITE-1594 URL: https://issues.apache.org/jira/browse/IGNITE-1594 Project: Ignite Issue Type: Sub-task

Re: IGFS concurrency issue

Vladimir Ozerov wrote > This is how we fixed it for now. But it requires paths locking starting > from the root. Otherwise they can become parent-child in a moment after > sucessfull check. I am not sure if we should be concerned about looking at the root or path here. This lock is only held for t

[GitHub] ignite pull request: Implements distributed semaphore ignite-638

GitHub user vladisav opened a pull request: https://github.com/apache/ignite/pull/120 Implements distributed semaphore ignite-638 This interface provides a rich API for working with distributed semaphore. Distributed semaphore provides functionality similar to java.util.concurre

Re: Let's please fix the mess in Git

On Wed, Sep 30, 2015 at 09:32PM, Raul Kripalani wrote: > Igniters, > > 1. Git history is polluted by lots of commits like: "Merge remote-tracking > branch 'origin/ignite-1.4' into ignite-1.4". Is there a logical reason for > this? Why doesn't the team use git pull --rebase? > > 2. Let's please de

Let's please fix the mess in Git

Igniters, 1. Git history is polluted by lots of commits like: "Merge remote-tracking branch 'origin/ignite-1.4' into ignite-1.4". Is there a logical reason for this? Why doesn't the team use git pull --rebase? 2. Let's please define a policy for Git commit messages. The current Git history is an

Re: New 'Deployment tasks' article on readme.io

Can someone help with answer on Dmitriy's question? Dmitriy, if yes, we should update docs with this information at least. But from continuous queries API standpoint I can't see how it can be used. Can we specify something by string-name there (without pointing out to a class)? -- Artem -- On W

vert.x integration

Igniters, Want to ask again about vert.x integration: https://issues.apache.org/jira/browse/IGNITE-1079 To my knowledge most issues on vert.x integration were closed in 1.4. However, it looks like this issue is still blocked by these tickets: https://issues.apache.org/jira/browse/IGNITE-1221 htt

[GitHub] ignite pull request: IGNITE-1589 Platform .Net: CacheAbstractTest....

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/119 IGNITE-1589 Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails Fix PlatformMemoryStream race condition: finalizer thread calls SynchronizeOutput which affects pooled memory used

[GitHub] ignite pull request: IGNITE-1586: Added IsValid() method to Ignite...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/118 IGNITE-1586: Added IsValid() method to Ignite, Cache and QueryCursor You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-1586

Re: JBPM and Drools integrations

Gianfranco, please try again. I had to change some settings on the repo. D. On Wed, Sep 30, 2015 at 2:50 PM, Gianfranco Murador wrote: > Dmitriy, > I get this error *Permission to apacheignite/drools-ignite.git denied* , > when I push on this repo : https://github.com/apacheignite/drools-igni

Re: Sergey Evdokimov Tickets

Chandresh , Thank you, any help is welcome. We update as soon we can replicate the issue 2015-09-30 11:25 GMT+02:00 chandresh pancholi < chandreshpancholi...@gmail.com>: > Gian, > I would love to help you with IGNITE-417. > > Let me know when and where to start. > > Thanks > > On Wed, Sep 30, 20

[jira] [Created] (IGNITE-1592) [Test Failed] GridCachePartitionedOffHeapValuesQueueApiSelfTest.testQueueRemoveMultithreadBounded

Anton Vinogradov created IGNITE-1592: Summary: [Test Failed] GridCachePartitionedOffHeapValuesQueueApiSelfTest.testQueueRemoveMultithreadBounded Key: IGNITE-1592 URL: https://issues.apache.org/jira/browse/IGNI

[GitHub] ignite pull request: IGNITE-1588: Fix for the IgniteJvmOption clas...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/117 IGNITE-1588: Fix for the IgniteJvmOption class You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-1588 Alternatively you can

[jira] [Created] (IGNITE-1590) IGFS: update & create operations should be truly thread-safe.

Ivan Veselovsky created IGNITE-1590: --- Summary: IGFS: update & create operations should be truly thread-safe. Key: IGNITE-1590 URL: https://issues.apache.org/jira/browse/IGNITE-1590 Project: Ignite

[jira] [Created] (IGNITE-1589) Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails

Pavel Tupitsyn created IGNITE-1589: --- Summary: Platform .Net: CacheAbstractTest.TestPutGetAsyncMultithreaded fails Key: IGNITE-1589 URL: https://issues.apache.org/jira/browse/IGNITE-1589 Project: Ig

[jira] [Created] (IGNITE-1588) CPP: Fix constructor of the IgniteJvmOption class

Igor Sapego created IGNITE-1588: --- Summary: CPP: Fix constructor of the IgniteJvmOption class Key: IGNITE-1588 URL: https://issues.apache.org/jira/browse/IGNITE-1588 Project: Ignite Issue Type:

Re: LGPL in 1.4 examples

On Wed, Sep 30, 2015 at 10:46AM, Branko Čibej wrote: > On 30.09.2015 10:33, Dmitriy Setrakyan wrote: > > On Wed, Sep 30, 2015 at 10:30 AM, Branko Čibej wrote: > > > >> On 30.09.2015 10:28, Sergey Kozlov wrote: > >>> Could we build these modules during building example project? It seems a > >>> bit

[jira] [Created] (IGNITE-1587) [Test Failed] Timeouted IgniteCacheAtomicNodeRestartTest.* at TC Windows agents

Anton Vinogradov created IGNITE-1587: Summary: [Test Failed] Timeouted IgniteCacheAtomicNodeRestartTest.* at TC Windows agents Key: IGNITE-1587 URL: https://issues.apache.org/jira/browse/IGNITE-1587

Re: [RESULT] [VOTE] Apache Ignite 1.4.0 Release (RC1)

Was the announcement send already and I missed it? If not - please do. Thanks! Cos On Mon, Sep 28, 2015 at 07:20PM, Anton Vinogradov wrote: > Site updated. > > On Mon, Sep 28, 2015 at 5:09 PM, Anton Vinogradov > wrote: > > > Ignite 1.4.0 successfuly released to > > https://dist.apache.org/re

[jira] [Created] (IGNITE-1586) CPP: Add isValid() method to all proxy-like classes

Igor created IGNITE-1586: Summary: CPP: Add isValid() method to all proxy-like classes Key: IGNITE-1586 URL: https://issues.apache.org/jira/browse/IGNITE-1586 Project: Ignite Issue Type: Task

[GitHub] ignite pull request: IGNITE-1580: const qualifiers removed for boo...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/116 IGNITE-1580: const qualifiers removed for bool arguments You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-1580 Alternative

Re: Introducing "compatibility level" concept.

+1 Any sort of overly nice infra-software ends up being either - an disaster integration and operation disaster - a maintainer nightmares because of complex internal logic - a dangerously silent data-corruption contraption or any combination of the above. Hadoop RPC versioning is somewhat clos

[jira] [Created] (IGNITE-1585) Test failed - TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine

Anton Vinogradov created IGNITE-1585: Summary: Test failed - TcpDiscoveryCloudIpFinderSelfTest.testGoogleComputeEngine Key: IGNITE-1585 URL: https://issues.apache.org/jira/browse/IGNITE-1585 Proje

[jira] [Created] (IGNITE-1584) Test Failed - IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap

Anton Vinogradov created IGNITE-1584: Summary: Test Failed - IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledTwoBackupsOffheapTieredSwap Key: IGNITE-1584 URL: https://issues.apach

[jira] [Created] (IGNITE-1583) Test Failed ( GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient )

Anton Vinogradov created IGNITE-1583: Summary: Test Failed ( GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient ) Key: IGNITE-1583 URL: https://issues.apache.org/jira/browse/IGNITE-1583 Proje

[jira] [Created] (IGNITE-1582) Test Failed - GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore

Anton Vinogradov created IGNITE-1582: Summary: Test Failed - GridCacheAtomicNearEnabledFairAffinityMultiNodeFullApiSelfTest.testWithSkipStore Key: IGNITE-1582 URL: https://issues.apache.org/jira/browse/IGNITE-

Re: JBPM and Drools integrations

Dmitriy, I get this error *Permission to apacheignite/drools-ignite.git denied* , when I push on this repo : https://github.com/apacheignite/drools-ignite. Maybe you need to add write permissions to my user. Thanks 2015-09-30 11:05 GMT+02:00 Dmitriy Setrakyan : > Invitation is sent and "drools-

Re: what is "communication encryption"?

Communication encryption is implemented using Security API hence Ignite supports the following security algorithms: http://docs.oracle.com/javase/7/docs/technotes/guides/security/StandardNames.html#SSLContext On Wed, Sep 30, 2015 at 3:23 PM, Dmitriy Setrakyan wrote: > On Wed, Sep 30, 2015 at 12:

[jira] [Created] (IGNITE-1581) Synchronous cache operation can deadlock on async semaphore.

Vladimir Ozerov created IGNITE-1581: --- Summary: Synchronous cache operation can deadlock on async semaphore. Key: IGNITE-1581 URL: https://issues.apache.org/jira/browse/IGNITE-1581 Project: Ignite

Re: what is "communication encryption"?

On Wed, Sep 30, 2015 at 12:18 PM, Branko Čibej wrote: > On 30.09.2015 11:18, Nikolay Tikhonov wrote: > > SslContextFactory allows to set different encryption protocols (by > default > > TLS). I think that just "ssl" confuses users. Might be "ssl\tls=off" more > > acceptable? > > SSL is one (rathe

Re: LGPL in 1.4 examples

On Wed, Sep 30, 2015 at 10:49 AM, Branko Čibej wrote: > On 30.09.2015 10:30, Dmitriy Setrakyan wrote: > > On Wed, Sep 30, 2015 at 9:45 AM, Branko Čibej wrote: > > > >> On 30.09.2015 09:29, Dmitriy Setrakyan wrote: > >>> On Wed, Sep 30, 2015 at 8:25 AM, Sergey Kozlov > >> wrote: > I filed t

Re: New 'Deployment tasks' article on readme.io

On Wed, Sep 30, 2015 at 11:08 AM, Artem Shutak wrote: > Dmitriy, I think it should stay under "Compute Grid" block because > Deployment SPI have the meaning only for ComputeTasks. > I thought that it also works with continuous queries and EventProcessor, no? > > Yakov, yes, Valentine has revie

[GitHub] ignite pull request: IGNITE-1573: mkdirs concurrency fixed.

GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/115 IGNITE-1573: mkdirs concurrency fixed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1573 Alternatively you c

Re: Introducing "compatibility level" concept.

Exposing a manually adjustable "compatibility level" makes the user a participant of Ignite's internals – something I dislike. Most users won't bother with investigating deep enough to make an informed decision to set this value accordingly, and it'll end up being the typical obscure config paramet

Re: Ignite 1.5 plans

With my Ignite hat on, I think having them together in the same assembly makes sense. After all, this is why I have offered the patch in the form it is right now. With my Bigtop hat on: I don't care one way or another. As soon as I can produce one or more assemblies that will have all the required

Re: Introducing "compatibility level" concept.

For me "compatibility level" looks like a complex and dangerous concept. It really must be enough to have versioned protocol, when newer protocol fully understands older ones. And there is no need to store the protocol version with each object, because it must be enough to send it on handshake and

Re: what is "communication encryption"?

On 30.09.2015 11:18, Nikolay Tikhonov wrote: > SslContextFactory allows to set different encryption protocols (by default > TLS). I think that just "ssl" confuses users. Might be "ssl\tls=off" more > acceptable? SSL is one (rather old) specification of Transport Layer Security (TLS). These days, y

Re: LGPL in 1.4 examples

I think we can follow current logic of splitting on java/java8/scala examples and new profile 'LGPL' where new module will be activated On Wed, Sep 30, 2015 at 12:30 PM, Anton Vinogradov wrote: > I offer to split examples to 2 modules: > 'examples' and 'lgpl-examples'. > Ignite convenience bina

Re: LGPL in 1.4 examples

I offer to split examples to 2 modules: 'examples' and 'lgpl-examples'. Ignite convenience binaries will contain only 'examples' project, but user will have opportunity to download sources and using lgpl profile build 'lgpl-examples'. On Wed, Sep 30, 2015 at 11:49 AM, Branko Čibej wrote: > On 30

Re: Sergey Evdokimov Tickets

Gian, I would love to help you with IGNITE-417. Let me know when and where to start. Thanks On Wed, Sep 30, 2015 at 2:30 PM, Dmitriy Setrakyan wrote: > On Wed, Sep 30, 2015 at 10:18 AM, Gianfranco Murador > wrote: > > > Some ticket seem resolved , but the state has been left "open" . I like >

Re: what is "communication encryption"?

SslContextFactory allows to set different encryption protocols (by default TLS). I think that just "ssl" confuses users. Might be "ssl\tls=off" more acceptable? On Wed, Sep 30, 2015 at 11:53 AM, Dmitriy Setrakyan wrote: > On Wed, Sep 30, 2015 at 10:18 AM, Alexey Goncharuk < > alexey.goncha...@gm

Re: New 'Deployment tasks' article on readme.io

Dmitriy, I think it should stay under "Compute Grid" block because Deployment SPI have the meaning only for ComputeTasks. Yakov, yes, Valentine has reviewed the jira and changed page name on: https://apacheignite.readme.io/docs/deployment-spi. I will fix your comments and will update the jira. Th

Re: JBPM and Drools integrations

Invitation is sent and "drools-ignite" repository is created. Let me now if you have troubles accessing it. D. On Wed, Sep 30, 2015 at 10:46 AM, Gianfranco Murador wrote: > My github username is murador. > Thank you. > > 2015-09-30 10:39 GMT+02:00 Dmitriy Setrakyan : > > > On Wed, Sep 30, 2015

Re: Introducing "compatibility level" concept.

>> 6) Node A restarts and meets unknown B-protocol. 6.1 Node A throws exception on start 6.2 Or node A invalidates persistent store (ignores the prev state) 6.3 Or user should have ability to specify converter somehow. Converter logic should be provided with release of new protocol (with more rece

Re: Sergey Evdokimov Tickets

On Wed, Sep 30, 2015 at 10:18 AM, Gianfranco Murador wrote: > Some ticket seem resolved , but the state has been left "open" . I like to > work on IGNITE-417 and IGNITE-888 with the right help from community; > Gianfranco, I am not sure IGNITE-888 is a valid ticket. I personally do knot know wh

[jira] [Created] (IGNITE-1580) CPP: Review Ignition interface.

Vladimir Ozerov created IGNITE-1580: --- Summary: CPP: Review Ignition interface. Key: IGNITE-1580 URL: https://issues.apache.org/jira/browse/IGNITE-1580 Project: Ignite Issue Type: Task

Re: what is "communication encryption"?

On Wed, Sep 30, 2015 at 10:18 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Given that encryption is enabled by setting SslContextFactory, I believe > that SSL is the only option. I am +1 for changing the output. > I changed it and committed to master. > > 2015-09-30 10:21 GMT+03:

Re: LGPL in 1.4 examples

On 30.09.2015 10:30, Dmitriy Setrakyan wrote: > On Wed, Sep 30, 2015 at 9:45 AM, Branko Čibej wrote: > >> On 30.09.2015 09:29, Dmitriy Setrakyan wrote: >>> On Wed, Sep 30, 2015 at 8:25 AM, Sergey Kozlov >> wrote: I filed the ticket: Build examples failed from binary fabric package

Re: JBPM and Drools integrations

My github username is murador. Thank you. 2015-09-30 10:39 GMT+02:00 Dmitriy Setrakyan : > On Wed, Sep 30, 2015 at 10:13 AM, Gianfranco Murador > wrote: > > > Hello Igniters , > > I take the discussion to understand if I have the proper approval from > the > > community > > for the early integra

Re: LGPL in 1.4 examples

On 30.09.2015 10:33, Dmitriy Setrakyan wrote: > On Wed, Sep 30, 2015 at 10:30 AM, Branko Čibej wrote: > >> On 30.09.2015 10:28, Sergey Kozlov wrote: >>> Could we build these modules during building example project? It seems a >>> bit excessively from user standpoint. >> Why do you think users are

Re: JBPM and Drools integrations

On Wed, Sep 30, 2015 at 10:13 AM, Gianfranco Murador wrote: > Hello Igniters , > I take the discussion to understand if I have the proper approval from the > community > for the early integration of Ignite with Drools and JBPM. > I would ask if you can then create a new repository in > https://gi

Re: LGPL in 1.4 examples

On Wed, Sep 30, 2015 at 10:30 AM, Branko Čibej wrote: > On 30.09.2015 10:28, Sergey Kozlov wrote: > > Could we build these modules during building example project? It seems a > > bit excessively from user standpoint. > > Why do you think users are dumb and lazy and can't issue two build > command

Re: LGPL in 1.4 examples

On Wed, Sep 30, 2015 at 9:45 AM, Branko Čibej wrote: > On 30.09.2015 09:29, Dmitriy Setrakyan wrote: > > On Wed, Sep 30, 2015 at 8:25 AM, Sergey Kozlov > wrote: > > > >> I filed the ticket: > >> Build examples failed from binary fabric package > >>

Re: LGPL in 1.4 examples

On 30.09.2015 10:28, Sergey Kozlov wrote: > Could we build these modules during building example project? It seems a > bit excessively from user standpoint. Why do you think users are dumb and lazy and can't issue two build commands instead of one? > On Wed, Sep 30, 2015 at 10:45 AM, Branko Čibe

Re: LGPL in 1.4 examples

Could we build these modules during building example project? It seems a bit excessively from user standpoint. On Wed, Sep 30, 2015 at 10:45 AM, Branko Čibej wrote: > On 30.09.2015 09:29, Dmitriy Setrakyan wrote: > > On Wed, Sep 30, 2015 at 8:25 AM, Sergey Kozlov > wrote: > > > >> I filed the t

Re: Introducing "compatibility level" concept.

My point is that is has to be just one extensible protocol. So in your case, either: in step 6, the node A would be able to read the A-compatible bits of data; or: in step 5, the B-nodes will know that the persistent store was made with A. Doing it any other way will force you to dumb down your wh

Re: Sergey Evdokimov Tickets

Some ticket seem resolved , but the state has been left "open" . I like to work on IGNITE-417 and IGNITE-888 with the right help from community; 2015-09-30 9:42 GMT+02:00 Dmitriy Setrakyan : > On Wed, Sep 30, 2015 at 9:01 AM, Yakov Zhdanov > wrote: > > > Correct. I meant unassign. > > > > There

Re: what is "communication encryption"?

Given that encryption is enabled by setting SslContextFactory, I believe that SSL is the only option. I am +1 for changing the output. 2015-09-30 10:21 GMT+03:00 Dmitriy Setrakyan : > On Wed, Sep 30, 2015 at 8:01 AM, Sergey Kozlov > wrote: > > > On Wed, Sep 30, 2015 at 4:51 AM, Dmitriy Setrakyan

JBPM and Drools integrations

Hello Igniters , I take the discussion to understand if I have the proper approval from the community for the early integration of Ignite with Drools and JBPM. I would ask if you can then create a new repository in https://github.com/apacheignite. Thanks, Regards, Gianfranco -- Gianfranco Murado

Re: Introducing "compatibility level" concept.

Brane, I see you point, but I do not see how we can implement it in our distributed environment. Very weird situations could appear. E.g. if there are two versions A and B: 1) Node A starts. 2) Node B starts and agrees with A to use old A-protocol. 3) Some data is persisted on disk using A-protoco

Re: Introducing "compatibility level" concept.

On 30.09.2015 09:51, Vladimir Ozerov wrote: > Igniters, > > Normally we are trying to maintain backward compatibility with previous > versions. But it is not always possible. > > E.g. we are about to release portable protocol. There are lots suggestions > how to optimize it, but all of them are rel

Re: New 'Deployment tasks' article on readme.io

I am looking at this page - https://apacheignite.readme.io/docs/deployment-spi. Correct? Good job! However, I have minor comments: 1. SPI parameters explanations and code example should be before scanners (scanner is SPI config as well, just more detailed info) 2. code example should include all

Introducing "compatibility level" concept.

Igniters, Normally we are trying to maintain backward compatibility with previous versions. But it is not always possible. E.g. we are about to release portable protocol. There are lots suggestions how to optimize it, but all of them are relatively hard to implement. It would not be a problem if

Re: LGPL in 1.4 examples

On 30.09.2015 09:29, Dmitriy Setrakyan wrote: > On Wed, Sep 30, 2015 at 8:25 AM, Sergey Kozlov wrote: > >> I filed the ticket: >> Build examples failed from binary fabric package >> >> > > I think the reason is that we do not upload Ignite LGPL i

Re: Sergey Evdokimov Tickets

On Wed, Sep 30, 2015 at 9:01 AM, Yakov Zhdanov wrote: > Correct. I meant unassign. > > There are no critical tickets in my view - > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20%20status%20!%3D%20closed%20AND%20assignee%20%3D%20sevdokimov-gg%20ORDER%20BY%20due%20ASC

Re: LGPL in 1.4 examples

On Wed, Sep 30, 2015 at 9:34 AM, Yakov Zhdanov wrote: > We can. > I am currently at ApacheCon. Let me ask a few folks. I will respond here soon. > > --Yakov > > 2015-09-30 10:29 GMT+03:00 Dmitriy Setrakyan : > > > On Wed, Sep 30, 2015 at 8:25 AM, Sergey Kozlov > > wrote: > > > > > I filed the

Re: Error when removing SQL indexes during node stop

On Wed, Sep 30, 2015 at 9:22 AM, Sergi Vladykin wrote: > Dmitriy, > > You should provide more details when you create issues in Jira. > Your setup is unclear (there are 2 or 3 nodes? of what roles?), which node > produced the exception unclear as well, > The stopping node printed this exception

Re: LGPL in 1.4 examples

We can. --Yakov 2015-09-30 10:29 GMT+03:00 Dmitriy Setrakyan : > On Wed, Sep 30, 2015 at 8:25 AM, Sergey Kozlov > wrote: > > > I filed the ticket: > > Build examples failed from binary fabric package > > > > > > > I think the reason is that we

Re: Switched main version to 1.4 on readme.io

done. --Yakov 2015-09-29 20:34 GMT+03:00 Dmitriy Setrakyan : > Yakov, > > The javadoc link on Ignite documentation still points to 1.3. Can you make > the switch? > > Thanks, > D. > > On Mon, Sep 28, 2015 at 3:24 PM, Yakov Zhdanov > wrote: > > > subj > > > > --Yakov > > >

Re: LGPL in 1.4 examples

On Wed, Sep 30, 2015 at 8:25 AM, Sergey Kozlov wrote: > I filed the ticket: > Build examples failed from binary fabric package > > I think the reason is that we do not upload Ignite LGPL integrations, e.g. ignite-hiberbnate artifact to maven c

Re: Error when removing SQL indexes during node stop

Dmitriy, You should provide more details when you create issues in Jira. Your setup is unclear (there are 2 or 3 nodes? of what roles?), which node produced the exception unclear as well, what happened after that (something hung or something went wrong or you just dislike this exception printout?)

Re: what is "communication encryption"?

On Wed, Sep 30, 2015 at 8:01 AM, Sergey Kozlov wrote: > On Wed, Sep 30, 2015 at 4:51 AM, Dmitriy Setrakyan > wrote: > > > I got the following printout on 1.4 startup: > > - > > Security status [authentication=off, communication encryption=off] > > - > > > > Do we mean SSL by "com

Re: Ignite 1.5 plans

On Wed, Sep 30, 2015 at 4:34 AM, Nikita Ivanov wrote: > I'm not sure how a file system concept corresponds to shared RDD or custom > MapReduce implementation... May we should have another "assembly" just for > in-memory file system? > And how would users use IgniteRDD and IGFS in the same projec

Re: Sergey Evdokimov Tickets

Correct. I meant unassign. There are no critical tickets in my view - https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20%20status%20!%3D%20closed%20AND%20assignee%20%3D%20sevdokimov-gg%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC --Yakov 2015-09-29 19: