[jira] [Created] (IGNITE-5271) Web Console: light basic/advanced configuration

Ilya Borisov created IGNITE-5271: Summary: Web Console: light basic/advanced configuration Key: IGNITE-5271 URL: https://issues.apache.org/jira/browse/IGNITE-5271 Project: Ignite Issue Type:

Re: GridGain Donates Persistent Distributed Store To ASF (Apache Ignite)

> 4) I believe the VOTE to accept the donation should be *decoupled* from > any VOTEs –or decisions– on *what* to do with the donation and *when* to do > it. Although it's sane and healthy to discuss the future of the donation > inside its new home, ultimately there should be no time pressure by

[VOTE] Accept Contribution of Ignite Persistent Store

Igniters, This branch (https://github.com/apache/ignite/tree/ignite-5267) adds a distributed and transactional Persistent Store to Apache Ignite project. The store seamlessly integrates with Apache Ignite 2.0 page memory architecture. One of the main advantages of the store is that Apache

Re: Session Replication Update on spring boot platform

Hello Val, As I discussed earlier, the problem arises in the cluster environment. we have 2 SB staleless instance backed by Ignite data store. The local environment is working fine and I am able to see the user sessions are being stored correctly. I could not make session replication working

[jira] [Created] (IGNITE-5269) [IGNITE-4575] Implement in Ignite wrapper for enums based on H2 user value type

Semen Boikov created IGNITE-5269: Summary: [IGNITE-4575] Implement in Ignite wrapper for enums based on H2 user value type Key: IGNITE-5269 URL: https://issues.apache.org/jira/browse/IGNITE-5269

Re: Session Replication Update on spring boot platform

Hi Rishi, I'm not sure I understand what the issue is. Can you elaborate a bit more and provide exact examples of what is not working? What code tweaks are required and how critical are they? Also I recall that your example was working fine after the latest fixes in 1.9 (if I'm not mistaken). Did

[jira] [Created] (IGNITE-5268) [GG-12193] DDL: Support dynamic index persistence

Semen Boikov created IGNITE-5268: Summary: [GG-12193] DDL: Support dynamic index persistence Key: IGNITE-5268 URL: https://issues.apache.org/jira/browse/IGNITE-5268 Project: Ignite Issue

[GitHub] ignite pull request #1989: IGNITE-4724: SQL: corrected result type for AVG()

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/1989 IGNITE-4724: SQL: corrected result type for AVG() You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4724

Re: Cassandra store and binary objects

Hi Val, As of now, Cassandra store can work with binary objects only as BLOBs - storing them as BLOBs in Cassandra database. Igor On Mon, May 22, 2017 at 1:40 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Igor, > > Can you please clarify if Cassandra store can work

Re: GridGain Donates Persistent Distributed Store To ASF (Apache Ignite)

Guys, As discussed, pushed the branch being stabilized to ignite-5267 (and created the corresponding ticket). 2017-05-21 6:48 GMT+03:00 Denis Magda : > Sounds good to me. > > To keep all of you in the loop, eventually, the *IP clearance vote* has > been initiated on

[jira] [Created] (IGNITE-5267) Persistent storage migration

Alexey Goncharuk created IGNITE-5267: Summary: Persistent storage migration Key: IGNITE-5267 URL: https://issues.apache.org/jira/browse/IGNITE-5267 Project: Ignite Issue Type: New

[GitHub] ignite pull request #1988: properties to configure memoryMetrics are added, ...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1988 properties to configure memoryMetrics are added, documentation improved You can merge this pull request into a Git repository by running: $ git pull

Re: Inefficient approach to executing remote SQL queries

Hi Mike, Generally, establishing connections in parallel could make sense, but note that in most this would be a minor optimization, because: - Under load connections are established once and then reused. If you observe disconnections during application lifetime under load, then

[GitHub] ignite pull request #1987: IGNITE-3562: Updated updated Lucene version.

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1987 IGNITE-3562: Updated updated Lucene version. updated to 4.10. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Inefficient approach to executing remote SQL queries

Hi Igniters, Whilst diagnosing a problem with a slow query, I became aware of a potential issue in the Ignite codebase. When executing a SQL query that is to run remotely, the IgniteH2Indexing#send() method is called, with a Collection as one of its parameters. This collection is iterated

[jira] [Created] (IGNITE-5266) .NET: Support LongCount in LINQ

Pavel Tupitsyn created IGNITE-5266: -- Summary: .NET: Support LongCount in LINQ Key: IGNITE-5266 URL: https://issues.apache.org/jira/browse/IGNITE-5266 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-5265) Eviction Rate memory metric to be implemented

Sergey Chugunov created IGNITE-5265: --- Summary: Eviction Rate memory metric to be implemented Key: IGNITE-5265 URL: https://issues.apache.org/jira/browse/IGNITE-5265 Project: Ignite Issue

Re: Ignite 2.0 TeamCity Run configurations

Igniters, I've created new PR https://github.com/apache/ignite/pull/1986 without merge conflicts against master. Please review these changes instead of PR1956. Thank you Best Regards, Dmitry Pavlov пн, 22 мая 2017 г. в 13:21, Alexey Goncharuk : > Thanks, Dmitriy! >

[GitHub] ignite pull request #1980: Ignite 4947: Fix AI 2.0 TC suites

Github user dspavlov closed the pull request at: https://github.com/apache/ignite/pull/1980 --- 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 #1986: IGNITE-4947: Create AI 2.0 TC suites

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/1986 IGNITE-4947: Create AI 2.0 TC suites New PR against master with squash all commits from https://github.com/apache/ignite/pull/1980 You can merge this pull request into a Git repository by

[GitHub] ignite pull request #1985: IGNITE-5257 .NET: SQL query timeouts

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1985 --- 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 #1581: IGNITE-1094 Ignite.createCache(CacheConfiguration...

Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/1581 --- 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 #1760: Ignite 4551

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

[jira] [Created] (IGNITE-5264) DDL operations must operate on per-schema basis

Vladimir Ozerov created IGNITE-5264: --- Summary: DDL operations must operate on per-schema basis Key: IGNITE-5264 URL: https://issues.apache.org/jira/browse/IGNITE-5264 Project: Ignite Issue

[GitHub] ignite pull request #1985: IGNITE-5257 .NET: SQL query timeouts

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1985 IGNITE-5257 .NET: SQL query timeouts You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-5257 Alternatively you can

[GitHub] ignite pull request #1984: ignite-5203 Simple BLOB support added

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/1984 ignite-5203 Simple BLOB support added You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-5203-master Alternatively

[jira] [Created] (IGNITE-5263) ODBC: use schema notion instead of cache name

Vladimir Ozerov created IGNITE-5263: --- Summary: ODBC: use schema notion instead of cache name Key: IGNITE-5263 URL: https://issues.apache.org/jira/browse/IGNITE-5263 Project: Ignite Issue

[GitHub] ignite pull request #1983: Ignite 4447 2

GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/1983 Ignite 4447 2 Removed IgniteCache150ClientsTest.java to IgniteCacheTestSuite.java. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1981: Expose getFieldName method to SqlFieldsQuery resu...

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

[GitHub] ignite pull request #1982: IGNITE-5252: Expose getFieldName method to SqlFie...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1982 IGNITE-5252: Expose getFieldName method to SqlFieldsQuery result. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #1981: Expose getFieldName method to SqlFieldsQuery resu...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1981 Expose getFieldName method to SqlFieldsQuery result. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5252

[GitHub] ignite pull request #1956: Ignite 4938 & IGNITE-4947: Fix AI 2.0 TC suites

Github user dspavlov closed the pull request at: https://github.com/apache/ignite/pull/1956 --- 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 #1980: Ignite 4947: Fix AI 2.0 TC suites

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/1980 Ignite 4947: Fix AI 2.0 TC suites You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4947 Alternatively you can

[GitHub] ignite pull request #1979: IGNITE-5054

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

Re: Ignite 2.0 TeamCity Run configurations

Thanks, Dmitriy! If there are no other objections, I will merge the changes shortly. 2017-05-22 13:10 GMT+03:00 Dmitry Pavlov : > Hi, Igniters! > > Could you please review and merge changes from > https://github.com/apache/ignite/pull/1956 into master. > > These changes

Re: Ignite 2.0 TeamCity Run configurations

Hi, Igniters! Could you please review and merge changes from https://github.com/apache/ignite/pull/1956 into master. These changes makes running tests with similar results in TC Run configs "Ignite 2.0 Tests" as it is in "Ignite Tests". Best regards, Dmitry Pavlov ср, 17 мая 2017 г. в 20:52,

[jira] [Created] (IGNITE-5261) Why one job of the Task stopped by exception,the other jobs may stopped.

wangbo created IGNITE-5261: -- Summary: Why one job of the Task stopped by exception,the other jobs may stopped. Key: IGNITE-5261 URL: https://issues.apache.org/jira/browse/IGNITE-5261 Project: Ignite

[GitHub] ignite pull request #1978: Ignite 5223 Allow use local binary metadata cache...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1978 Ignite 5223 Allow use local binary metadata cache if it's possible You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1962: IGNITE-5054

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

Cassandra store and binary objects

Hi Igor, Can you please clarify if Cassandra store can work directly with binary objects or not, when POJO strategy is used? In other words, are POJO classes required on server nodes for this strategy? What will happen if CacheConfiguration#keepBinaryInStore property set to true? -Val

[GitHub] ignite pull request #1977: Checkpoint copy page optimization

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/1977 Checkpoint copy page optimization You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite