Re: Download links on ignite.apache.org not always working

Anton, it's clear now, thanks for your explanation! On Fri, Oct 13, 2017 at 4:01 PM, Anton Vinogradov wrote: > Vyacheslav, > > 1) That's correct case. > All download links except newest version should point to archive. > > 2) That's correct case. > You can change mirror only for newest version.

[GitHub] ignite pull request #2855: IGNITE-6631

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/2855 IGNITE-6631 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6631 Alternatively you can review and apply these

[jira] [Created] (IGNITE-6631) Optimize GridH2KeyValueRowOnheap.getValue() method

Vladimir Ozerov created IGNITE-6631: --- Summary: Optimize GridH2KeyValueRowOnheap.getValue() method Key: IGNITE-6631 URL: https://issues.apache.org/jira/browse/IGNITE-6631 Project: Ignite Iss

[GitHub] ignite pull request #2854: IGNITE-6630 Time units fix.

GitHub user xtern opened a pull request: https://github.com/apache/ignite/pull/2854 IGNITE-6630 Time units fix. You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-6630 Alternatively you can review and apply thes

[jira] [Created] (IGNITE-6630) Incorrect time units of average transaction commit/rollback duration cache metrics.

Pavel Pereslegin created IGNITE-6630: Summary: Incorrect time units of average transaction commit/rollback duration cache metrics. Key: IGNITE-6630 URL: https://issues.apache.org/jira/browse/IGNITE-6630

[GitHub] ignite pull request #2853: gg-12957

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2853 gg-12957 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite gg-12957 Alternatively you can review and apply these chang

Re: Indexing fields of non-POJO cache values

[Crossposting to the dev list] Alexey, Yes, something like that, where the "reference"/"alias" is expressed as a piece of Java code (as part of QueryEntity definition, perhaps) that is invoked by Ignite at the cache entry indexing time. My point is that rather than limiting indexable fields on

Re: Optimized DML execution: how to name it?

Vova, Just to make sure, we are not adding a new configuration property, right? Is this just a JDBC connection flag we are discussing? If yes, can you please provide an example of the JDBC connection string? D. On Fri, Oct 13, 2017 at 9:57 AM, Denis Magda wrote: > Vladimir, > > > "inPlaceUpdat

Re: Optimized DML execution: how to name it?

Vladimir, > "inPlaceUpdate" is not very good candidate because there are a lot of other > "in place update" optimizations in RDBMS word, and most of them relates to > in-place update of some value in the data page. I am afraid users will be > confused with this name. I’m not insisting on this nam

[GitHub] ignite pull request #2852: Ignite 6030 merge 6560

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2852 Ignite 6030 merge 6560 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6030-merge-6560 Alternatively you can revi

Re: Persistence per memory policy configuration

Seems I've got what you’re talking about. I’ve tried to change the root directory (*persistencePath*) and saw that only data/indexes were placed to it while wal stayed somewhere in my work dir. It works counterintuitive and causes non productive discussions like we are in arguing about *persis

[jira] [Created] (IGNITE-6629) Make service persistence and automatic redeployment configurable in ServiceConfiguration

Ivan Rakov created IGNITE-6629: -- Summary: Make service persistence and automatic redeployment configurable in ServiceConfiguration Key: IGNITE-6629 URL: https://issues.apache.org/jira/browse/IGNITE-6629

[jira] [Created] (IGNITE-6628) Make possible to rebuild all SQL indexes programmatically with enabled persistence.

Alexei Scherbakov created IGNITE-6628: - Summary: Make possible to rebuild all SQL indexes programmatically with enabled persistence. Key: IGNITE-6628 URL: https://issues.apache.org/jira/browse/IGNITE-6628

[jira] [Created] (IGNITE-6627) .NET: cache deserialization fail with complex value type & enum

Alexey Popov created IGNITE-6627: Summary: .NET: cache deserialization fail with complex value type & enum Key: IGNITE-6627 URL: https://issues.apache.org/jira/browse/IGNITE-6627 Project: Ignite

[GitHub] ignite pull request #2851: 1.8.13

GitHub user ntikhonov opened a pull request: https://github.com/apache/ignite/pull/2851 1.8.13 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.8.13 Alternatively you can review and apply these cha

Apache Ignite Paris Meetup inaugural gathering 18 October

Parisian Igniters, You’re invited to the inaugural gathering of Apache Ignite Paris Meetup on the 18th of October at 18:30! The meetup will take place at the Finastra (formerly Misys) Paris offices where we have an evening of technically ric

[GitHub] ignite pull request #2850: ignite-6572 allow multiple caches use one SQL sch...

GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/2850 ignite-6572 allow multiple caches use one SQL schema You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6572 Al

Re: Some questions regard Cache Query and performance

Aaron, let me forward this to DEV: Ignite DEV community, I tried to confirm setLocal(true) semantics for ContinuousQuery and I have got not what I expected. I found that executing a ContinuousQuery with setLocal(true): - Still executes initial query remotely - Listens for modifications loc

Re: Optimized DML execution: how to name it?

Vladimir, I think serverSideDml is better. --Yakov

Re: Download links on ignite.apache.org not always working

Vyacheslav, 1) That's correct case. All download links except newest version should point to archive. 2) That's correct case. You can change mirror only for newest version. Archived versions have no mirrors. See https://issues.apache.org/jira/browse/IGNITE-2964 for details. On Fri, Oct 13, 2017

[GitHub] ignite pull request #2846: IGNITE-6621 .NET: Disable thin client

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/2846 ---

[GitHub] ignite pull request #2849: Ignite 1.9.7.b3

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

[GitHub] ignite pull request #2847: IGNITE-6624

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/2847 IGNITE-6624 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6624 Alternatively you can review and apply these

[jira] [Created] (IGNITE-6626) SQL: Doesn't materialize rows when possible

Vladimir Ozerov created IGNITE-6626: --- Summary: SQL: Doesn't materialize rows when possible Key: IGNITE-6626 URL: https://issues.apache.org/jira/browse/IGNITE-6626 Project: Ignite Issue Type

[GitHub] ignite pull request #2848: IGNITE-6626

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/2848 IGNITE-6626 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6626 Alternatively you can review and apply these

[GitHub] ignite pull request #2846: IGNITE-6621 .NET: Disable thin client

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2846 IGNITE-6621 .NET: Disable thin client You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6621 Alternatively you c

[jira] [Created] (IGNITE-6625) JDBC thin: support SSL connection to Ignite node

Taras Ledkov created IGNITE-6625: Summary: JDBC thin: support SSL connection to Ignite node Key: IGNITE-6625 URL: https://issues.apache.org/jira/browse/IGNITE-6625 Project: Ignite Issue Type:

Re: Download links on ignite.apache.org not always working

Dmitry, I assume that the problem on the download page [1], because: 1) The *default* link to the latest release is: http://mirror.linux-ia64.org/apache//ignite/2.2.0/apache-ignite-fabric-2.2.0-bin.zip instead of: https://archive.apache.org/dist/ignite/2.2.0/apache-ignite-2.2.0-src.zip like the o

[GitHub] ignite pull request #2842: IGNITE-4723 .NET: Support REGEXP_LIKE in LINQ

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2842 ---

[jira] [Created] (IGNITE-6624) SQL: IndexingQueryCacheFilter should use immediate partition data if possible

Vladimir Ozerov created IGNITE-6624: --- Summary: SQL: IndexingQueryCacheFilter should use immediate partition data if possible Key: IGNITE-6624 URL: https://issues.apache.org/jira/browse/IGNITE-6624 P

[GitHub] ignite pull request #2836: IGNITE-6605

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/2836 ---

[jira] [Created] (IGNITE-6623) Web console: export query result set doesn't work on Edge

Pavel Konstantinov created IGNITE-6623: -- Summary: Web console: export query result set doesn't work on Edge Key: IGNITE-6623 URL: https://issues.apache.org/jira/browse/IGNITE-6623 Project: Ignite

[GitHub] ignite pull request #2845: IGNITE-6519 Race in SplitAwareTopologyValidator o...

GitHub user akuramshingg opened a pull request: https://github.com/apache/ignite/pull/2845 IGNITE-6519 Race in SplitAwareTopologyValidator on activator and server node join TestRecordingCommunicationSpi fix references IGNITE-6507 Commit can be lost in network split scenario You

[GitHub] ignite pull request #2767: IGNITE-6519 Race in SplitAwareTopologyValidator o...

Github user akuramshingg closed the pull request at: https://github.com/apache/ignite/pull/2767 ---

[jira] [Created] (IGNITE-6622) User defined function doesn't work if query executed via ignite.context().query().querySqlFieldsNoCache(qry, true);

Pavel Konstantinov created IGNITE-6622: -- Summary: User defined function doesn't work if query executed via ignite.context().query().querySqlFieldsNoCache(qry, true); Key: IGNITE-6622 URL: https://issues.apach

[GitHub] ignite pull request #2839: Ignite 1.9.7.b2

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/2839 ---

[GitHub] ignite pull request #2844: Ignite 1.8 master

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

[GitHub] ignite pull request #2843: Ignite 1.7 master

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

[jira] [Created] (IGNITE-6621) .NET: Disable thin client for 2.3 release

Pavel Tupitsyn created IGNITE-6621: -- Summary: .NET: Disable thin client for 2.3 release Key: IGNITE-6621 URL: https://issues.apache.org/jira/browse/IGNITE-6621 Project: Ignite Issue Type: Ta

[jira] [Created] (IGNITE-6620) Document JDBC/ODBC "skipReducerOnUpdate" flag

Vladimir Ozerov created IGNITE-6620: --- Summary: Document JDBC/ODBC "skipReducerOnUpdate" flag Key: IGNITE-6620 URL: https://issues.apache.org/jira/browse/IGNITE-6620 Project: Ignite Issue Ty

[GitHub] ignite pull request #2488: IGNITE-6024: support for server-side dml

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2488 ---

[GitHub] ignite pull request #2830: IGNITE-6371 .NET: Thin client example

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2830 ---

[jira] [Created] (IGNITE-6619) .NET: Ignite Demo Application

Pavel Tupitsyn created IGNITE-6619: -- Summary: .NET: Ignite Demo Application Key: IGNITE-6619 URL: https://issues.apache.org/jira/browse/IGNITE-6619 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-6618) Do not show client nodes in node selection modal

Pavel Konstantinov created IGNITE-6618: -- Summary: Do not show client nodes in node selection modal Key: IGNITE-6618 URL: https://issues.apache.org/jira/browse/IGNITE-6618 Project: Ignite

Re: Persistence per memory policy configuration

Denis, Data/index storage and WAL are located under the same root by default. However, this is not mandatory: *storagePath* and *walPath* properties can contain both absolute and relative paths. If paths are absolute, storage and WAL can reside on different devices, like this: storagePath: /

[jira] [Created] (IGNITE-6617) Web console: there is no error message that cluster is not active on Queries screen

Pavel Konstantinov created IGNITE-6617: -- Summary: Web console: there is no error message that cluster is not active on Queries screen Key: IGNITE-6617 URL: https://issues.apache.org/jira/browse/IGNITE-6617

[GitHub] ignite pull request #2842: IGNITE-4723 .NET: Support REGEXP_LIKE in LINQ

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/2842 IGNITE-4723 .NET: Support REGEXP_LIKE in LINQ You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4723 Alternativel

Re: Optimized DML execution: how to name it?

Or "skipReducerOnUpdate" On Fri, Oct 13, 2017 at 10:05 AM, Vladimir Ozerov wrote: > Guys, > > I think I have a little bit better candidate: "bypassReducerOnUpdate". > > On Fri, Oct 13, 2017 at 10:03 AM, Vladimir Ozerov > wrote: > >> Dima, >> >> Yes, in future releases we will enable it by defau

Re: Optimized DML execution: how to name it?

Guys, I think I have a little bit better candidate: "bypassReducerOnUpdate". On Fri, Oct 13, 2017 at 10:03 AM, Vladimir Ozerov wrote: > Dima, > > Yes, in future releases we will enable it by default. New TX protocol will > work in pretty much the same way. > > On Fri, Oct 13, 2017 at 4:57 AM, D

Re: Optimized DML execution: how to name it?

Dima, Yes, in future releases we will enable it by default. New TX protocol will work in pretty much the same way. On Fri, Oct 13, 2017 at 4:57 AM, Dmitriy Setrakyan wrote: > On Wed, Oct 11, 2017 at 11:45 PM, Vladimir Ozerov > wrote: > > > Igniters, > > > > We prepared optimization of DML proc

Re: Optimized DML execution: how to name it?

Denis, In future SQL transactional protocol will do all updates "in place" instead of passing it to the client. This is the only possible way to perform large updates without killing the client with OOME. "inPlaceUpdate" is not very good candidate because there are a lot of other "in place update"