IGNITE-2552

will take https://issues.apache.org/jira/browse/IGNITE-2552 if you dont mind -- *Best Regards,* *Kuznetsov Aleksey*

[GitHub] ignite pull request #1526: Ignite 1.7.8

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1526 Ignite 1.7.8 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.7.8 Alternatively you can review and apply

Re: Apache Ignite 1.9

Thanks, Denis! On Mon, Feb 13, 2017 at 5:49 PM, Denis Magda wrote: > Well, merged Kubernetes integration to the master and cherry-picked to > 1.9. The docs and getting started for readme.io to be done soon. > > — > Denis > > > On Feb 13, 2017, at 9:10 AM, Denis Magda

Re: Apache Ignite 1.9

Well, merged Kubernetes integration to the master and cherry-picked to 1.9. The docs and getting started for readme.io to be done soon. — Denis > On Feb 13, 2017, at 9:10 AM, Denis Magda wrote: > > Do I merge to the master first and then cherry-pick to 1.9 from there? > >

Re: Patches for Website

Mauricio, I can’t find the patch for htaccess. The archive you sent before contains only this file - add_canonical_url_and_missing_ga_code.patch. In your latest reply I can’t find the patch attached as well. — Denis > On Feb 13, 2017, at 1:21 PM, Mauricio Stekl wrote:

Re: Tasks Scheduling and Chaining

Hi all, I personally think this is a good candidate for implementing Ignite Queue Based messaging where any one of the given nodes can pick up the message. Upon task completion it should fire an event which should be picked up by any node just the way jms queue works. However I am not sure

Re: Patches for Website

Hi Denis, I have updated my local repo and it seems the patch to htaccess was not committed. Attached you can find the .patch file just in case you didn’t receive it ok. Thanks. Mauricio > On Feb 9, 2017, at 18:37, Denis Magda wrote: > > Hi Mauricio, > > I’ve

Re: IGNITE-817: [Test] Disabled tests of GridCacheOffHeapTest

Alexander, could you wipe out this test then making the code clean? — Denis > On Feb 12, 2017, at 11:24 PM, Semyon Boikov wrote: > > Hi, > > GridCacheOffHeapTest is some very old class and I think it can be removed. > Currently all actual benchmarks are in 'benchmarks'

Re: IGNITE-603

Hi Alexander, Looks like the test is commented for a while. GridDeploymentMode has already been renamed to DeploymentMode. Yakov, is this test still relevant for the compute grid? — Denis > On Feb 13, 2017, at 5:45 AM, Александр Меньшиков wrote: > > Hello, everyone. >

Re: Hello

Hi Dmitriy, Welcome to the Ignite community! Added you to the contributors list in JIRA. Please subscribe to both dev and user lists if it’s still relevant for you: https://ignite.apache.org/community/resources.html#mail-lists Get familiar with Ignite development process described here:

Re: Hello

Hi Vasu, Welcome to the Ignite community! Please subscribe to both dev and user lists: https://ignite.apache.org/community/resources.html#mail-lists Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions

Re: Tasks Scheduling and Chaining

The events are proved to be unreliable. If a node doesn’t send a cache event due to a failure then it’s burden of an application to handle topology change events, checking for undelivered events, etc. This doesn’t sound like a straightforward solution to me. Any other thoughts? Yakov, as one

Hello

Hello everyone, I am a new user and would like to start contributing to apache projects, especially the Ignite. I work on Java technologies primarily. I would be working on easy tickets to start with. Thanks Vasu

Re: general question

...and what is the use of inject ? пн, 13 Фев 2017 г., 17:28 Alexey Goncharuk : > Aleksei, > > This processor handles various @*Resource (@IgniteInstanceResource, > @CacheNameResource, ...) annotations for user-supplied objects, such as > tasks, jobs, entry

Re: Custom thread pools for compute tasks

On Mon, Feb 13, 2017 at 8:18 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > > > > We cannot compensate blocked threads with new ones forever. At some point > > we will have to limit new threads which will bring us to the same > problem, > > no? > > > > This means that a user

Re: IGNITE-4534

Hi Ivan, Welcome to the Ignite community! You should get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute can be found here:

Re: Apache Ignite 1.9

Do I merge to the master first and then cherry-pick to 1.9 from there? — Denis > On Feb 13, 2017, at 8:21 AM, Anton Vinogradov > wrote: > > Igniters, > > We're starting release stabilization process. > Branch 1.9 created and equals to master branch right now. > >

[jira] [Created] (IGNITE-4693) Add possibility to wrap Java plugin exceptions to .NET plugin exceptions

Pavel Tupitsyn created IGNITE-4693: -- Summary: Add possibility to wrap Java plugin exceptions to .NET plugin exceptions Key: IGNITE-4693 URL: https://issues.apache.org/jira/browse/IGNITE-4693

Re: Apache Ignite 1.9

Igniters, We're starting release stabilization process. Branch 1.9 created and equals to master branch right now. Please make sure that your changes will be merged to both branches: *ignite-1.9* and *master*. On Fri, Feb 10, 2017 at 4:53 PM, Sergey Kalashnikov wrote: >

Re: Custom thread pools for compute tasks

> > We cannot compensate blocked threads with new ones forever. At some point > we will have to limit new threads which will bring us to the same problem, > no? > This means that a user recursively trying to call blocking tasks inside of blocking tasks. We can as well detect this and fail with an

Re: Custom thread pools for compute tasks

We cannot compensate blocked threads with new ones forever. At some point we will have to limit new threads which will bring us to the same problem, no? I do like the idea, however, of users creating their own thread pools and utilizing them for execution, as proposed by Vladimir. D. On Mon,

[jira] [Created] (IGNITE-4692) .NET: Add ClassName and Message to JavaException

Pavel Tupitsyn created IGNITE-4692: -- Summary: .NET: Add ClassName and Message to JavaException Key: IGNITE-4692 URL: https://issues.apache.org/jira/browse/IGNITE-4692 Project: Ignite Issue

[GitHub] ignite pull request #1525: IGNITE-4617: Added field-access methods for Binar...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1525 IGNITE-4617: Added field-access methods for BinaryObject. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4617

Re: Ensure that builder approach is used for all setters in public API

Andrey, Yakov, An MBean for eviction policy is registered in GridCacheProcessor#prepare(). --AG 2017-02-09 18:53 GMT+03:00 Yakov Zhdanov : > Wow! This is the regression (from long ago version) if true. > > As far as having mbean to manage eviction policy on the fly - why

Re: Custom thread pools for compute tasks

Vladimir, I like the idea of compensating threads with new ones. However, I do not see why users should notify Ignite when a new distributed operation is started because Ignite already is the task executor. We can intercept (virtually) all such calls and adjust pool size automatically. No need to

Re: general question

Aleksei, This processor handles various @*Resource (@IgniteInstanceResource, @CacheNameResource, ...) annotations for user-supplied objects, such as tasks, jobs, entry processors, etc. --AG 2017-02-13 12:42 GMT+03:00 voipp : > Hi, all ! What is the use of

Hello

Hello, I want to work with you. Can you give me access to contribute? My username in JIRA is SomeFire.

[GitHub] ignite pull request #1524: IGNITE-4685 Propagate platform plugin configurati...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1524 IGNITE-4685 Propagate platform plugin configuration to Java You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #1523: IGNITE-4677 Fixed incorrect connectable node dete...

GitHub user nva opened a pull request: https://github.com/apache/ignite/pull/1523 IGNITE-4677 Fixed incorrect connectable node detection in router mode for Java thin client You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1522: IGNITE-4484 fix not compliant with tx isolation s...

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/1522 IGNITE-4484 fix not compliant with tx isolation semantics You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4484

IGNITE-603

Hello, everyone. I think the commented-out method "processSize2Test" can be removed. There aren't class "GridDeploymentMode" which used in arguments. Do you agree with me?

Re: IGNITE-4158 - ready for review

Merged to 2.0. On Sun, Feb 12, 2017 at 10:13 PM, Denis Magda wrote: > Hi Vyacheslav, > > Val, Vovan, please assist with the review > > — > Denis > > > On Feb 10, 2017, at 3:53 AM, Vyacheslav Daradur > wrote: > > > > Hello. I did it. > > > > Please,

[jira] [Created] (IGNITE-4687) Web console: Use pool for process REST request in Web Agent

Andrey Novikov created IGNITE-4687: -- Summary: Web console: Use pool for process REST request in Web Agent Key: IGNITE-4687 URL: https://issues.apache.org/jira/browse/IGNITE-4687 Project: Ignite

[jira] [Created] (IGNITE-4689) .NET: Support java.sql.Time

Vladimir Ozerov created IGNITE-4689: --- Summary: .NET: Support java.sql.Time Key: IGNITE-4689 URL: https://issues.apache.org/jira/browse/IGNITE-4689 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-4690) CPP: Support java.sql.Time

Vladimir Ozerov created IGNITE-4690: --- Summary: CPP: Support java.sql.Time Key: IGNITE-4690 URL: https://issues.apache.org/jira/browse/IGNITE-4690 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-4686) Web Console: Add grouping by company on Amin panel screen

Alexey Kuznetsov created IGNITE-4686: Summary: Web Console: Add grouping by company on Amin panel screen Key: IGNITE-4686 URL: https://issues.apache.org/jira/browse/IGNITE-4686 Project: Ignite

[jira] [Created] (IGNITE-4691) ODBC: Support java.sql.Time

Vladimir Ozerov created IGNITE-4691: --- Summary: ODBC: Support java.sql.Time Key: IGNITE-4691 URL: https://issues.apache.org/jira/browse/IGNITE-4691 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-4688) Change copyrights to 2017

Vladimir Ozerov created IGNITE-4688: --- Summary: Change copyrights to 2017 Key: IGNITE-4688 URL: https://issues.apache.org/jira/browse/IGNITE-4688 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #1514: ignite-4664

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1514 --- 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

[GitHub] ignite pull request #1521: IGNITE-4587: Discontinue and remove CacheAtomicWr...

GitHub user dream-x opened a pull request: https://github.com/apache/ignite/pull/1521 IGNITE-4587: Discontinue and remove CacheAtomicWriteOrderMode.CLOCK mode [Jira ticket](https://issues.apache.org/jira/browse/IGNITE-4587). You can merge this pull request into a Git repository by

general question

Hi, all ! What is the use of GridResourceProcessor ? And its inject() method -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/general-question-tp14522.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

IGNITE-4492 is ready for review

Hello. I fixed it. Please, review https://github.com/apache/ignite/pull/1491 - created new MBean for stripped executor -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-4492-is-ready-for-review-tp14521.html Sent from the Apache Ignite Developers

Re: general question

Please have a look at BinarySchema and it's usages. Essentially this is a fingerprint of object fields in the order they were serialized, represented as [field name] -> [position] hash map. Consider and object with 3 fields - A, B, C. There could be 6 different schemas for it: [A, B, C], [A, C,

Re: general question

What is schema in your context? пн, 13 февр. 2017 г. в 10:50, Vladimir Ozerov : > Alex, > > FieldAccessor stores field positions for the given schema to allow for fast > field value lookup. > > On Fri, Feb 10, 2017 at 7:06 PM, ALEKSEY KUZNETSOV < > alkuznetsov...@gmail.com