[jira] [Created] (IGNITE-5387) Web console: Agent should report version of internal demo nodes

Vasiliy Sisko created IGNITE-5387: - Summary: Web console: Agent should report version of internal demo nodes Key: IGNITE-5387 URL: https://issues.apache.org/jira/browse/IGNITE-5387 Project: Ignite

Re: nested SQL sub-queries with non-collocated joins

Here is a “known limitations” section on readme.io: https://apacheignite.readme.io/docs/sql-queries#section-known-limitations Feel free to update it with the limitation discussed. — Denis > On Jun 1, 2017, at 1:19 PM, Dmitriy Setrakyan wrote: > > On Thu, Jun 1, 2017 at

Re: nested SQL sub-queries with non-collocated joins

On Thu, Jun 1, 2017 at 1:07 PM, Sergi Vladykin wrote: > If you don't see an exception then it must be supported. This is the whole > point of this exception, right? > Exception is just to enforce the constraint. We still must clearly document what is supported.

Re: nested SQL sub-queries with non-collocated joins

If you don't see an exception then it must be supported. This is the whole point of this exception, right? Sergi 2017-06-01 22:50 GMT+03:00 Dmitriy Setrakyan : > On Thu, Jun 1, 2017 at 12:32 PM, Sergi Vladykin > wrote: > > > I guess it must work

Re: nested SQL sub-queries with non-collocated joins

On Thu, Jun 1, 2017 at 12:32 PM, Sergi Vladykin wrote: > I guess it must work the following way: > > If distributed joins are enabled we can try to prove that the subquery is > collocated, if we can't then try to rewrite it, if we can't, then throw an > exception. > >

Re: nested SQL sub-queries with non-collocated joins

I guess it must work the following way: If distributed joins are enabled we can try to prove that the subquery is collocated, if we can't then try to rewrite it, if we can't, then throw an exception. Still this can not be done 100% correct, probably we have to have some flag which allows to

Re: Geo spatial index

No, feel free to create one. Sergi 2017-06-01 21:00 GMT+03:00 Denis Magda : > Good catch. I found the ticket that’s aim is to integrate the full-text > search indexes with the virtual page memory architecture. > https://issues.apache.org/jira/browse/IGNITE-5371 < >

Re: nested SQL sub-queries with non-collocated joins

Sergi, I am OK with any improvement here, but we need to be able to clearly state to a user what is supported and what is not. If we cannot clearly describe it, I would rather not support it at all and throw an exception. Is this going to be possible with your solution? D. On Thu, Jun 1, 2017

Re: Persistent Distributed Store Metrics

Sergey, thanks, You get a green light from my side. Please go ahead and bring this to life unless anyone else has any comments. — Denis > On Jun 1, 2017, at 4:18 AM, Sergey Chugunov wrote: > > Guys, > > I created a ticket [1] summing up results of our discussion.

Re: Geo spatial index

Good catch. I found the ticket that’s aim is to integrate the full-text search indexes with the virtual page memory architecture. https://issues.apache.org/jira/browse/IGNITE-5371 Sergi, do we have a similar one for the geo-spatial? — Denis

[GitHub] ignite pull request #2064: IGNITE-5355 Create task with release tools

GitHub user achetaev opened a pull request: https://github.com/apache/ignite/pull/2064 IGNITE-5355 Create task with release tools You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5355 Alternatively

[GitHub] ignite pull request #2062: IGNITE-5355 Create task with release tools

Github user achetaev closed the pull request at: https://github.com/apache/ignite/pull/2062 --- 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: BinaryObjectImpl.deserializeValue with specific ClassLoader

I wanted to provide an update on where I am at with this as I'm still exploring different options. For the time being I've taken the path of using a delegating ClassLoader in IgniteConfiguration as was previously suggested; however, with the difference being that whenever a service is

Re: Apache Ignite 2.1 scope

IGNITE-5327 Create predefined cache templates for CREATE TABLE command - minor comments left, ETA is Friday. IGNITE-5380 Validate cache QueryEntities in discovery thread - in progress, the meat of code is written, but need to add lots of tests. ETA is Friday. IGNITE-5188 Support AFFINITY KEY

Re: Persistent Store Stabilization for release

Guys, I merged recent changes from the master branch (SQL-related changes) to the integration branch, we need another TC run to see if the merge broke something. 2017-06-01 19:14 GMT+03:00 Dmitriy Setrakyan : > BTW, can anyone explain to me why do we keep the new

Re: Persistent Store Stabilization for release

BTW, can anyone explain to me why do we keep the new persistence code in a separate module instead of merging it to core? On Thu, Jun 1, 2017 at 4:32 AM, Sergey Chugunov wrote: > Hello Denis, > > There are three suites [1] [2] [3] configured on TeamCity with bunch of

Re: Apache Ignite 2.1 scope

1. IGNITE-5386 Inactive mode must be forced on starting up grid with persistence is enabled It is important improvement to fix critical bug IGNITE-5363. Working on it, ETA - tomorrow. 2. IGNITE-5375 New PersistentStoreMetrics, MemoryMetrics interface improvements A lot of

Re: Apache Ignite 2.1 scope

Compute for C++ - https://issues.apache.org/jira/browse/IGNITE-3355 - merged to master. Best Regards, Igor On Thu, Jun 1, 2017 at 6:56 PM, Taras Ledkov wrote: > Folks, > > IGNITE-4922 JDBC Driver: renew thin client based solution: > > On 2.1 the functionality of the new

[GitHub] ignite pull request #2063: IGNITE-5356 .NET: Fix runtime dependency loading ...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2063 IGNITE-5356 .NET: Fix runtime dependency loading with peer deployment You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite

Re: Cassandra and Ignite C++ Issue

Take a look at initial message. Best Regards, Igor On Thu, Jun 1, 2017 at 6:45 PM, Igor Rudyak wrote: > Could you share your POJO key/value classes and persistence descriptor? > > Igor > > On Jun 1, 2017 8:30 AM, "Igor Sapego" wrote: > > > User's

Re: Apache Ignite 2.1 scope

Folks, IGNITE-4922 JDBC Driver: renew thin client based solution: On 2.1 the functionality of the new thin client JDBC driver will be between deprecated Ignite thin JDBC and Ignite JDBCv2. 1. The most functions of SQL query (include DML) are implemented and ready for review; 2. The most

Re: Apache Ignite 2.1 scope

.NET: * IGNITE-2492 Peer assembly loading - merged * IGNITE-1894 Delegate support in the API via extension methods - postponed to 2.2 (see comments) * IGNITE-4904 DML Delete via LINQ - merged On Thu, Jun 1, 2017 at 6:43 PM, Vladimir Ozerov wrote: > Folks, > > We are almost

Re: Cassandra and Ignite C++ Issue

Could you share your POJO key/value classes and persistence descriptor? Igor On Jun 1, 2017 8:30 AM, "Igor Sapego" wrote: > User's comment: > > I have my own cassandra table with 1 partiton key, 3 clustering keys, > and I expect the value not to be stored in one column as a

Re: Apache Ignite 2.1 scope

Folks, We are almost reached proposed feature-complete date (June 2), Could you please share current status of your major features? On Tue, May 16, 2017 at 3:51 AM, Dmitriy Setrakyan wrote: > Looks a little tight. Let's hope we can make it. > > On Mon, May 15, 2017 at

Re: Cassandra and Ignite C++ Issue

User's comment: I have my own cassandra table with 1 partiton key, 3 clustering keys, and I expect the value not to be stored in one column as a blob. Is there any way I can achieve this? I have used POJO and there is an issue like the key is only getting inserted into the cassandra table Best

Configuration inconsistency IGNITE-896

Will start working on the ticket if nobody mind -- *Best Regards,* *Kuznetsov Aleksey*

[GitHub] ignite pull request #2062: IGNITE-5355 Create task with release tools

GitHub user achetaev opened a pull request: https://github.com/apache/ignite/pull/2062 IGNITE-5355 Create task with release tools You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5355 Alternatively

[GitHub] ignite pull request #2061: IGNITE-4887 Support for starting transaction in a...

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2061 IGNITE-4887 Support for starting transaction in another thread You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite IGNITE-4887

[GitHub] ignite pull request #2060: Ignite-3562-lucele-5.5.2

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2060 Ignite-3562-lucele-5.5.2 for test purposes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3562-5.5.2

Re: contention on DataStructure creation/removing

Alexey, I think, that from user's perspective data structures look more like a library that works on top of caches, not something completely separate and independent. Most properties from CacheConfiguration make sense for Atomics and Collections (for example, properties related to rebalancing).

[jira] [Created] (IGNITE-5386) Inactive mode must be forced on starting up grid with persistence enabled

Sergey Chugunov created IGNITE-5386: --- Summary: Inactive mode must be forced on starting up grid with persistence enabled Key: IGNITE-5386 URL: https://issues.apache.org/jira/browse/IGNITE-5386

[jira] [Created] (IGNITE-5385) Get rid of discovery custom message on exchange completion

Yakov Zhdanov created IGNITE-5385: - Summary: Get rid of discovery custom message on exchange completion Key: IGNITE-5385 URL: https://issues.apache.org/jira/browse/IGNITE-5385 Project: Ignite

Re: contention on DataStructure creation/removing

This is how I see API to create data structures in user-defined caches: https://github.com/apache/ignite/pull/2058 On Thu, Jun 1, 2017 at 2:56 PM, Ilya Lantukh wrote: > Hi all, > > There are other problems with current data structures implementation, > which are related

[GitHub] ignite pull request #2059: IGNITE-5075-pds

GitHub user gvvinblade opened a pull request: https://github.com/apache/ignite/pull/2059 IGNITE-5075-pds You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5075-pds Alternatively you can review and

[GitHub] ignite pull request #2058: Example of API changes.

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/2058 Example of API changes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5075-datastructures Alternatively you

[GitHub] ignite pull request #2057: IGNITE-5309: Added schema to SqlFieldsQuery for C...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2057 IGNITE-5309: Added schema to SqlFieldsQuery for C++ You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5309

[jira] [Created] (IGNITE-5384) JDBC Driver: implement ResultSet#getDate(int, Calendar)

Taras Ledkov created IGNITE-5384: Summary: JDBC Driver: implement ResultSet#getDate(int, Calendar) Key: IGNITE-5384 URL: https://issues.apache.org/jira/browse/IGNITE-5384 Project: Ignite

Re: contention on DataStructure creation/removing

Hi all, There are other problems with current data structures implementation, which are related to new persistence mechanics. For example, take a look at this ticket: https://issues.apache.org/jira/browse/IGNITE-5324 I think the best approach is to store data structures not in special system

[jira] [Created] (IGNITE-5383) Do not perform cache key validation when BinaryMarshaller is used

Vladimir Ozerov created IGNITE-5383: --- Summary: Do not perform cache key validation when BinaryMarshaller is used Key: IGNITE-5383 URL: https://issues.apache.org/jira/browse/IGNITE-5383 Project:

[jira] [Created] (IGNITE-5382) SQL: frequent switch between schemas cause severe slowdown

Vladimir Ozerov created IGNITE-5382: --- Summary: SQL: frequent switch between schemas cause severe slowdown Key: IGNITE-5382 URL: https://issues.apache.org/jira/browse/IGNITE-5382 Project: Ignite

[jira] [Created] (IGNITE-5381) JDBC thin: support JdbcPreparedStatement.getParameterMetaData method

Vladimir Ozerov created IGNITE-5381: --- Summary: JDBC thin: support JdbcPreparedStatement.getParameterMetaData method Key: IGNITE-5381 URL: https://issues.apache.org/jira/browse/IGNITE-5381 Project:

Re: Persistent Store Stabilization for release

Hello Denis, There are three suites [1] [2] [3] configured on TeamCity with bunch of tests for PDS functionality. As you can see most of tests are passing now (only 6 tests are failing, for *partitionLoss *tests problem was almost sorted out), it looks like that this functionality is pretty

[jira] [Created] (IGNITE-5380) Validate cache QueryEntities in discovery thread

Vladimir Ozerov created IGNITE-5380: --- Summary: Validate cache QueryEntities in discovery thread Key: IGNITE-5380 URL: https://issues.apache.org/jira/browse/IGNITE-5380 Project: Ignite

[jira] [Created] (IGNITE-5379) JDBC thin: get rid of cache name

Vladimir Ozerov created IGNITE-5379: --- Summary: JDBC thin: get rid of cache name Key: IGNITE-5379 URL: https://issues.apache.org/jira/browse/IGNITE-5379 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-5378) JDBC thin: support query cancellation

Vladimir Ozerov created IGNITE-5378: --- Summary: JDBC thin: support query cancellation Key: IGNITE-5378 URL: https://issues.apache.org/jira/browse/IGNITE-5378 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-5376) JDBC thin: Expose SqlFieldsQuery hints as parameters

Vladimir Ozerov created IGNITE-5376: --- Summary: JDBC thin: Expose SqlFieldsQuery hints as parameters Key: IGNITE-5376 URL: https://issues.apache.org/jira/browse/IGNITE-5376 Project: Ignite

[jira] [Created] (IGNITE-5377) ODBC: Expose SqlFieldsQuery hints as parameters

Vladimir Ozerov created IGNITE-5377: --- Summary: ODBC: Expose SqlFieldsQuery hints as parameters Key: IGNITE-5377 URL: https://issues.apache.org/jira/browse/IGNITE-5377 Project: Ignite Issue

Re: Persistent Distributed Store Metrics

Guys, I created a ticket [1] summing up results of our discussion. Please review and leave comments if something is still unclear there. Thanks, Sergey [1] https://issues.apache.org/jira/browse/IGNITE-5375 On Wed, May 31, 2017 at 11:56 PM, Dmitriy Setrakyan wrote: >

[jira] [Created] (IGNITE-5375) New PersistentStoreMetrics, MemoryMetrics interface improvements

Sergey Chugunov created IGNITE-5375: --- Summary: New PersistentStoreMetrics, MemoryMetrics interface improvements Key: IGNITE-5375 URL: https://issues.apache.org/jira/browse/IGNITE-5375 Project:

[jira] [Created] (IGNITE-5374) JDBC/ODBC: make sure that server doesn't have idle timeout

Vladimir Ozerov created IGNITE-5374: --- Summary: JDBC/ODBC: make sure that server doesn't have idle timeout Key: IGNITE-5374 URL: https://issues.apache.org/jira/browse/IGNITE-5374 Project: Ignite

[jira] [Created] (IGNITE-5373) JDBC thin driver: improve network configuration

Vladimir Ozerov created IGNITE-5373: --- Summary: JDBC thin driver: improve network configuration Key: IGNITE-5373 URL: https://issues.apache.org/jira/browse/IGNITE-5373 Project: Ignite Issue

[jira] [Created] (IGNITE-5372) .NET: IgniteConfiguration.LongQueryWarningTimeout

Pavel Tupitsyn created IGNITE-5372: -- Summary: .NET: IgniteConfiguration.LongQueryWarningTimeout Key: IGNITE-5372 URL: https://issues.apache.org/jira/browse/IGNITE-5372 Project: Ignite Issue

Re: contention on DataStructure creation/removing

On Thu, Jun 1, 2017 at 1:29 AM, Dmitriy Setrakyan wrote: > Won't it be confusing from a user stand point to have multiple data > structures with the same name? > I won't change this, optionally I can allow to have the same name for different data structures' types, but

[GitHub] ignite pull request #2056: IGNITE-5327 PARTITIONED and REPLICATED cache temp...

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/2056 IGNITE-5327 PARTITIONED and REPLICATED cache templates You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2045: MemoryPolicyConfiguration.rateTimeInterval proper...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2045 --- 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 #2008: IGNITE-5291 Correct handling of cache stop in Ign...

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

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2049 --- 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: nested SQL sub-queries with non-collocated joins

The approach you are suggesting will be very complex for current implementation. Also most probably very inefficient. Actually I was thinking about another but similar approach: in many cases we can rewrite a subquery in WHERE clause into JOIN subquery. Like the following: SELECT x.* FROM x

Re: Summary of SQL changes in 2.1

Dmitry, Pavel, regarding limitations: 1) Caches created through SQL should not interfere with caches created through API and config. We do not understand all implications of this interference for now, especially in the context of persistence, so it is better to restrict this behavior for now.

[GitHub] ignite pull request #2006: IGNITE-5288: Inconsistency of committed and the m...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2006 --- 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 #2014: ignite-4947: binary basic test suite was removed ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2014 --- 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 #2055: IGNITE-5305 Correct schema in GridQueryProcessor....

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/2055 IGNITE-5305 Correct schema in GridQueryProcessor.dynamicTableCreate You can merge this pull request into a Git repository by running: $ git pull

Re: Summary of SQL changes in 2.1

I think it makes sense to reserve IGNITE schema for future use as well. 2017-06-01 0:26 GMT+03:00 Dmitriy Setrakyan : > Vladmir, > > Thanks for the detailed email. My comments are inline... > > On Wed, May 31, 2017 at 11:21 AM, Vladimir Ozerov >

Re: Summary of SQL changes in 2.1

> 3) "CREATE TABLE" creates a cache with special internal property > "sql=true". Such cache cannot be destroyed through "Ignite.destroyCache". > It can only be dropped through "DROP TABLE".The opposite is also holds: > static and dynamic caches cannot be dropped through "DROP TABLE". Hi Vladimir,

Re: Geo spatial index

Same think stays for the full-text indexes which are currently stored in Lucene. 2017-05-24 21:56 GMT+03:00 Dmitriy Setrakyan : > Sergi, > > While we are figuring this out, what happens to the GeoSpatial > functionality in the mean time? Is it going to work at all? If not,

Re: Cache.getAll can return partially commited results. IGNITE-4809

Ah, ok thanks for clarifying. I will leave my ticket unassigned ср, 31 мая 2017 г. в 21:10, Alexey Goncharuk : > Aleksey, > > Generally, this decision cannot be made on a single node because a > transaction may affect multiple nodes, and one node may have already >

[jira] [Created] (IGNITE-5370) IgniteSet misses its size after cluster restart with enabled PDS feature

Igor Seliverstov created IGNITE-5370: Summary: IgniteSet misses its size after cluster restart with enabled PDS feature Key: IGNITE-5370 URL: https://issues.apache.org/jira/browse/IGNITE-5370

Re: [DISCUSS] Ignite memory -> virtual memory

I am fine with this javadoc change as long as there is no confusion between Ignite page memory buffers and the OS Virtual Memory concept. 2017-06-01 2:07 GMT+03:00 Dmitriy Setrakyan : > Igniters, > > With the newly donated persistence functionality in Ignite, I have been >

[jira] [Created] (IGNITE-5369) Add possibility to generate alias for primary key in WebConsole

Evgenii Zhuravlev created IGNITE-5369: - Summary: Add possibility to generate alias for primary key in WebConsole Key: IGNITE-5369 URL: https://issues.apache.org/jira/browse/IGNITE-5369 Project:

[jira] [Created] (IGNITE-5368) Cassandra store should support private/public fields serialization for POJO persistence strategy

Igor Rudyak created IGNITE-5368: --- Summary: Cassandra store should support private/public fields serialization for POJO persistence strategy Key: IGNITE-5368 URL: https://issues.apache.org/jira/browse/IGNITE-5368