Re: about AtomicConfiguration

Valentin, Can you please add more explanation to IGNITE-2096, so it will be more clear what needs to be fixed? Thanks, D. On Wed, Jan 13, 2016 at 8:09 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi, > > This behavior is correct and unfortunately your suggestion is not

[jira] [Created] (IGNITE-2376) .NET: UnmanagedUtils.IgnitionStart return value is never used

Pavel Tupitsyn created IGNITE-2376: -- Summary: .NET: UnmanagedUtils.IgnitionStart return value is never used Key: IGNITE-2376 URL: https://issues.apache.org/jira/browse/IGNITE-2376 Project: Ignite

Re: New method in IgniteCache API.

Dmitriy, Are you suggesting that we need to pass partitions state to a topology validator so that user needs to check it manually. I do not think this is convenient for an end-user and like the approach with the policy that Vladimir suggested better. Raul, I assume you want to add IgniteCacheEx

Re: Binary ID mapper that uses a simple name of classes.

I would suggest "SimpleClassNameBinaryIdMapper" --Yakov 2016-01-14 4:59 GMT+03:00 Dmitriy Setrakyan : > I like the last one too. > > On Wed, Jan 13, 2016 at 7:54 AM, Artem Shutak > wrote: > > > Igniters, > > > > I'm working on

[GitHub] ignite pull request: gg-8700

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/403 gg-8700 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ilantukh/ignite ignite-gg-8700 Alternatively you can review and apply these changes

[jira] [Created] (IGNITE-2378) Data loss Part 2. Add flexible DataLoss Policy. Improve dataLoss event with batch.

Vladimir Ershov created IGNITE-2378: --- Summary: Data loss Part 2. Add flexible DataLoss Policy. Improve dataLoss event with batch. Key: IGNITE-2378 URL: https://issues.apache.org/jira/browse/IGNITE-2378

[GitHub] ignite pull request: IGNITE-2376 .NET: UnmanagedUtils.IgnitionStar...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/402 IGNITE-2376 .NET: UnmanagedUtils.IgnitionStart return value is never used You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite

[jira] [Created] (IGNITE-2379) .NET: ASP.NET Output Cache provider

Pavel Tupitsyn created IGNITE-2379: -- Summary: .NET: ASP.NET Output Cache provider Key: IGNITE-2379 URL: https://issues.apache.org/jira/browse/IGNITE-2379 Project: Ignite Issue Type: New

[jira] [Created] (IGNITE-2380) .NET: Ignite configuration in app.config and web.config

Pavel Tupitsyn created IGNITE-2380: -- Summary: .NET: Ignite configuration in app.config and web.config Key: IGNITE-2380 URL: https://issues.apache.org/jira/browse/IGNITE-2380 Project: Ignite

[jira] [Created] (IGNITE-2381) Move Indexed key-value pairs from Cache Screen to Metadata Screen

Alexey Kuznetsov created IGNITE-2381: Summary: Move Indexed key-value pairs from Cache Screen to Metadata Screen Key: IGNITE-2381 URL: https://issues.apache.org/jira/browse/IGNITE-2381 Project:

Re: GridFutureAdapter: deprecate startTime(), duration() and endTime()

+1 BTW, corresponding ticket already exists. You can find it under umbrella ticket IGNITE-2232 14 янв. 2016 г. 18:40 пользователь "Yakov Zhdanov" написал: > Guys, > > We have startTime(), duration() and endTime() methods which have several > usages each along internals of

Re: Json support in Ignite

I would consider a case for generating hash-code by iterating through all the fields by default. We need to make sure that the iteration order is the same on both ends. User can always override it, no? D. On Thu, Jan 14, 2016 at 8:10 AM, Andrey Gura wrote: > Hi, > > > > >

Re: What is jdbc:ignite:cfg ??

Hello, JFYI, I created ticket as result of this discussion: https://issues.apache.org/jira/browse/IGNITE-2382 On Thu, Dec 10, 2015 at 10:29 PM, Dmitriy Setrakyan wrote: > Andrey, > > I agree on both points. However, I still think that we should provide > sample

Re: Json support in Ignite

Hi, > > Also we need following functionality for json objects > > > > 1. Possibility to map json cache key to affinity key. This can be > achieved > > with custom affinity mapper: > > > > cache.setAffinityMapper(new AffinityKeyMapper() { > > @Override public Object affinityKey(Object

[jira] [Created] (IGNITE-2385) Rename metadata to domain model

Vasiliy Sisko created IGNITE-2385: - Summary: Rename metadata to domain model Key: IGNITE-2385 URL: https://issues.apache.org/jira/browse/IGNITE-2385 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-2387) Ignite puzzle picture on readme.io has broken size in FireFox

Pavel Konstantinov created IGNITE-2387: -- Summary: Ignite puzzle picture on readme.io has broken size in FireFox Key: IGNITE-2387 URL: https://issues.apache.org/jira/browse/IGNITE-2387 Project:

[GitHub] ignite pull request: Switch off update notifier

GitHub user vkulichenko opened a pull request: https://github.com/apache/ignite/pull/405 Switch off update notifier You can merge this pull request into a Git repository by running: $ git pull https://github.com/vkulichenko/incubator-ignite gg-10952 Alternatively you can

[jira] [Created] (IGNITE-2384) Notification missed in continuous query

Valentin Kulichenko created IGNITE-2384: --- Summary: Notification missed in continuous query Key: IGNITE-2384 URL: https://issues.apache.org/jira/browse/IGNITE-2384 Project: Ignite Issue

Re: Stupide question about Queue ?

Agree with Denis. Sounds like this can be easily achieved by enabling swap layer for queue cache. So we just need to put this on configuration. -Val On Thu, Jan 14, 2016 at 5:44 AM, Denis Magda wrote: > Hi, > > This seems to be an interesting functionality. As I understand

Re: Stupide question about Queue ?

What are the possibilities for swap spaces? Can we persist the cache/queue content to file system based on the eviction policy? Thanks, Murthy. On Thu, Jan 14, 2016 at 5:23 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Agree with Denis. Sounds like this can be easily

[jira] [Created] (IGNITE-2388) Security issue in corner case

Pavel Konstantinov created IGNITE-2388: -- Summary: Security issue in corner case Key: IGNITE-2388 URL: https://issues.apache.org/jira/browse/IGNITE-2388 Project: Ignite Issue Type:

Re: GridFutureAdapter: deprecate startTime(), duration() and endTime()

Really hard to believe that removing 16 bytes in futures gives 5% of performance. Yakov, are you certain about this? If this turns out to be true, let’s see if we can slim down the futures used internally, without breaking the public API. D. On Thu, Jan 14, 2016 at 8:36 AM, Vladimir Ozerov

Persistence in queues and sets

Igniters, It sounds like users could be interested in being able to persist the data saved in queues and sets. See the thread on user list [1]. The obvious solution is to reuse our CacheStore interface, but I'm not sure that this is possible because it's designed for key-value storage. E.g.,

[GitHub] ignite pull request: IGNITE-2099 - Fixing custom collections.

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

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/369 --- 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: Persistence in queues and sets

I think we need a specialized CollectionStore API for this. Something that will receive an element value and its index (if index is required). D. On Thu, Jan 14, 2016 at 11:31 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Igniters, > > It sounds like users could be

[GitHub] ignite pull request: Switch off update notifier

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

Re: Stupide question about Queue ?

Created ticket for queue swapping feature: https://issues.apache.org/jira/browse/IGNITE-2389 Feel free to provide feedback. -Val On Thu, Jan 14, 2016 at 3:24 PM, Murthy Kakarlamudi wrote: > What are the possibilities for swap spaces? Can we persist the cache/queue > content

[jira] [Created] (IGNITE-2390) IGFS path modes are not honored

Denis Magda created IGNITE-2390: --- Summary: IGFS path modes are not honored Key: IGNITE-2390 URL: https://issues.apache.org/jira/browse/IGNITE-2390 Project: Ignite Issue Type: Bug

Re: Binary ID mapper that uses a simple name of classes.

On Thu, Jan 14, 2016 at 3:39 AM, Yakov Zhdanov wrote: > I would suggest "SimpleClassNameBinaryIdMapper" > Is it consistent? Do we have other classes in the same package that start with word Binary? If not, then I agree. > > --Yakov > > 2016-01-14 4:59 GMT+03:00 Dmitriy

Re: What is jdbc:ignite:cfg ??

Andrey, I am still a bit unclear. Why not have ability to specify a default cache per notebook, not per-interpreter? On Thu, Jan 14, 2016 at 8:42 AM, Andrey Gura wrote: > Hello, > > JFYI, I created ticket as result of this discussion: >

[GitHub] ignite pull request: ignite-2080 Data alignment issues with Unsafe

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/362 --- 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: ignite-2080 Data alignment issues with Unsafe

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/404 ignite-2080 Data alignment issues with Unsafe You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-2080 Alternatively

[jira] [Created] (IGNITE-2382) Force client mode in JDBC driver and provide default configuration file

Andrey Gura created IGNITE-2382: --- Summary: Force client mode in JDBC driver and provide default configuration file Key: IGNITE-2382 URL: https://issues.apache.org/jira/browse/IGNITE-2382 Project:

GridFutureAdapter: deprecate startTime(), duration() and endTime()

Guys, We have startTime(), duration() and endTime() methods which have several usages each along internals of the project, but to support these methods we have 2 long fields in GridFutureAdapter which gives us 16 bytes. Other fields - res (reference 8 bytes at max), ignoreInterrupts (boolean 1

Re: Ignite as Big Data project built on Mesos

Can you send a PR on github/apache/mesos or submit a review ?. On Wed, Jan 13, 2016 at 6:30 PM, Dmitriy Setrakyan wrote: > Hello Mesos community! > > Ignite community would like to add Apache Ignite to this