SQL: setting key field name for types registered via CacheConfiguration.setIndexedTypes

Guys, Let’s suppose there is a cache that stores entries like that: * key - int * value - custom object which fields are annotated by @QuerySqlField Before 2.0 if I wanted to refer to the key in an SQL query I had to use “_key” keyword. In 2.0 this is no longer the requirement. Any name can be

Re: Add ability to enable and disable rebalancing per-node

to Nick, could you please describe in more detail the use of DataStreamer (do you use StreamReceiver)? It seems that you've unnecessary care about synchronous service startup and cache rebalance. Service should start quickly after node has joined the topology, and will process all the data has

Re: Apache Ignite 2.1 scope

Vyacheslav, I think it is worth the research, but you should always keep data querying and indexing in mind. For example, I don't see how by-page compression will solve it. On Thu, May 11, 2017 at 1:52 AM, Vyacheslav Daradur wrote: > Dmitriy, > > I'm researching a best way

[GitHub] ignite pull request #1926: IGNITE-4597: CPP: Add mechanism to reset argument...

GitHub user vinx13 opened a pull request: https://github.com/apache/ignite/pull/1926 IGNITE-4597: CPP: Add mechanism to reset arguments for sql queries. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vinx13/ignite ignite-4597

Re: [jira] [Commented] (IGNITE-4052) Add ability to set up users for MESOS

Hello guys! I want to update https://apacheignite.readme.io/docs/mesos-deployment with new text according with https://cwiki.apache.org/confluence/display/IGNITE/Documentation But have a problem with authentication, registered login vaopols...@gmail.com. Help me, please. New text: 3.Copy the

Re: Apache Ignite 2.1 scope

Denis, The described roadmap looks great! Additional, I vote for introducing an ability (OOTB) to store objects in a cache in a compressed form. This will allow to store more data at the cost of incriasing of CPU utilization. 2017-05-11 4:23 GMT+03:00 Denis Magda : >

[jira] [Created] (IGNITE-5200) Web Console: Watch in ignite_modules works incorrect after migration on webpack2

Andrey Novikov created IGNITE-5200: -- Summary: Web Console: Watch in ignite_modules works incorrect after migration on webpack2 Key: IGNITE-5200 URL: https://issues.apache.org/jira/browse/IGNITE-5200

IGNITE-1094 Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

Igntrs! Plz, review my changes https://issues.apache.org/jira/browse/IGNITE-1094 *https://github.com/apache/ignite/pull/1904 * -- *Best Regards,* *Kuznetsov Aleksey* -- *Best Regards,* *Kuznetsov Aleksey*

Re: Apache Ignite 2.1 scope

On Thu, May 11, 2017 at 12:44 AM, Vyacheslav Daradur wrote: > Denis, > > The described roadmap looks great! > > Additional, I vote for introducing an ability (OOTB) to store objects in a > cache in a compressed form. > This will allow to store more data at the cost of

Re: Apache Ignite 2.1 scope

Dmitriy, I'm researching a best way for this future. At the moment I found only one way (querying and indexing compatible), this is per-objects-field compression. But there is a good proffit only for long strings or fields with large objects. Maybe it makes sense just to introduce compression

[jira] [Created] (IGNITE-5201) .NET: SegmentationResolver

Pavel Tupitsyn created IGNITE-5201: -- Summary: .NET: SegmentationResolver Key: IGNITE-5201 URL: https://issues.apache.org/jira/browse/IGNITE-5201 Project: Ignite Issue Type: New Feature

[GitHub] ignite pull request #1930: logging of memory configuration improvements on n...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1930 logging of memory configuration improvements on node start You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-5206) Test mesos user and mesos role parameters on real mesos cluster.

Vadim Opolski created IGNITE-5206: - Summary: Test mesos user and mesos role parameters on real mesos cluster. Key: IGNITE-5206 URL: https://issues.apache.org/jira/browse/IGNITE-5206 Project: Ignite

[GitHub] ignite pull request #1929: Removed condition, simplified logic

GitHub user yzhdanov opened a pull request: https://github.com/apache/ignite/pull/1929 Removed condition, simplified logic You can merge this pull request into a Git repository by running: $ git pull https://github.com/yzhdanov/ignite atomic-sequence-optimization

[jira] [Created] (IGNITE-5203) JDBC driver should support BLOB fields

Andrey Gura created IGNITE-5203: --- Summary: JDBC driver should support BLOB fields Key: IGNITE-5203 URL: https://issues.apache.org/jira/browse/IGNITE-5203 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-5204) The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception

Chris Wang created IGNITE-5204: -- Summary: The Unicode character in the value of a field which are included in an un-unique index will cause "stack overhead" exception Key: IGNITE-5204 URL:

[GitHub] ignite pull request #1928: Ignite 5193

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

Re: Add ability to enable and disable rebalancing per-node

As far as I can see from ticket title reporter wants to disable rebalancing on per-node basis. So, some nodes would not load partitions from other nodes while others should load normally. Disabling partition map exchange will stop rebalancing all over the grid (however, I find this pretty useful

Re: Apache Ignite 2.1 scope

As for .NET, I would propose to concentrate on peer deployment (IGNITE-2492) and related stuff, like IGNITE-1894 .NET: Delegate support in the API via extension methods. SQL Dependency does not look important to me, we can reschedule it for later versions. On Thu, May 11, 2017 at 12:01 PM,

[jira] [Created] (IGNITE-5202) Default mem policy name is not changed after setting defaultMemoryPolicyName property

Ksenia Rybakova created IGNITE-5202: --- Summary: Default mem policy name is not changed after setting defaultMemoryPolicyName property Key: IGNITE-5202 URL: https://issues.apache.org/jira/browse/IGNITE-5202

Re: Add ability to enable and disable rebalancing per-node

Hi Alexandr, Yes, I'm using a StreamReceiver since I'm mostly using the cache as a router. The implementation is more-or-less like the following: The StreamPipeline is managed by the data node which contains the stages that make up the pipeline and what service is responsible for each stage

Re: 10X decrease in performance with Ignite 2.0.0

Cross-posting to devlist. --Yakov