[jira] [Created] (IGNITE-6858) Wait for exchange inside GridReduceQueryExecutor.query which never finishes due to opened transaction

Alexandr Kuramshin created IGNITE-6858: -- Summary: Wait for exchange inside GridReduceQueryExecutor.query which never finishes due to opened transaction Key: IGNITE-6858 URL:

[jira] [Created] (IGNITE-6857) Multi stage start cache

Dmitriy Govorukhin created IGNITE-6857: -- Summary: Multi stage start cache Key: IGNITE-6857 URL: https://issues.apache.org/jira/browse/IGNITE-6857 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-6856) SQL: invalid security checks during query execution

Vladimir Ozerov created IGNITE-6856: --- Summary: SQL: invalid security checks during query execution Key: IGNITE-6856 URL: https://issues.apache.org/jira/browse/IGNITE-6856 Project: Ignite

[jira] [Created] (IGNITE-6855) Refactor JMSStreamer to better align with overall streamer design

Timothy Steffens created IGNITE-6855: Summary: Refactor JMSStreamer to better align with overall streamer design Key: IGNITE-6855 URL: https://issues.apache.org/jira/browse/IGNITE-6855 Project:

Re: JMSStreamer enhancement -- needs to support multiple IgniteDataStreamers.

Tim, If you want to do this change by yourself, then create a ticket in Jira, assign to yourself and prepare a pull request. See here for more information about the process: https://ignite.apache.org/community/contribute.html#contribute

Re: JMSStreamer enhancement -- needs to support multiple IgniteDataStreamers.

Yes, this makes sense. The proposed changes will improve the overall implementation of the JMSStreamer and the changes will also allow for me to then extend the streamer and implement my own custom functionality as needed. What are the next steps to getting this change implemented? On

Re: JMSStreamer enhancement -- needs to support multiple IgniteDataStreamers.

Tim, I think you properly defined flaws in the JmsStreamer and it defintely makes sense to do the following: - Deprecate org.apache.ignite.stream.jms11.MessageTransformer in favor of extractors defined in StreamAdapter. This JMS specific transformer doesn't provide any value and only

[jira] [Created] (IGNITE-6854) Enabling Persistent Memory for Ignite

Mulugeta Mammo created IGNITE-6854: -- Summary: Enabling Persistent Memory for Ignite Key: IGNITE-6854 URL: https://issues.apache.org/jira/browse/IGNITE-6854 Project: Ignite Issue Type: New

Re: Fair affinity resurrection with baseline topology

Huge +1. Related question - is it possible to use affinity comparison to "merge" partition maps of caches with similar affinity functions? If we do that, we will be able to get rid of these nasty "cache groups". On Thu, Nov 9, 2017 at 7:42 PM, Dmitriy Setrakyan wrote: >

[jira] [Created] (IGNITE-6853) Cassandra cache store does not clean prepared statements cache when remove old cassandra session

Mikhail Cherkasov created IGNITE-6853: - Summary: Cassandra cache store does not clean prepared statements cache when remove old cassandra session Key: IGNITE-6853 URL:

[GitHub] ignite pull request #3011: Ignite : Javadocs for cache change request operat...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3011 Ignite : Javadocs for cache change request operation You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12790-1

Re: Fair affinity resurrection with baseline topology

I think it definitely makes sense to add the Fair affinity function back to Ignite. On Thu, Nov 9, 2017 at 11:46 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Igniters, > > After spending some time on baseline topology review, it came to my mind > that we can return stateful

Re: [DISUCSS] Ticket filing process

On Thu, Nov 9, 2017 at 11:10 PM, Vladimir Ozerov wrote: > Ok, I see. Then the question is when to do a review? > Whenever, the sooner the better. This we cannot enforce. But since the tickets will have the upcoming release version, the review will have to happen before the

[jira] [Created] (IGNITE-6852) Kill ignite process in case of multithreaded updates cause segmentation fault

Dmitriy Pavlov created IGNITE-6852: -- Summary: Kill ignite process in case of multithreaded updates cause segmentation fault Key: IGNITE-6852 URL: https://issues.apache.org/jira/browse/IGNITE-6852

Fair affinity resurrection with baseline topology

Igniters, After spending some time on baseline topology review, it came to my mind that we can return stateful affinity functions for persistent caches. Since now we will have a topology which is persisted to the cluster metastore, why not save the partition affinity distribution together with

[jira] [Created] (IGNITE-6851) CREATE INDEX statement should accept no name indexes

Roman Kondakov created IGNITE-6851: -- Summary: CREATE INDEX statement should accept no name indexes Key: IGNITE-6851 URL: https://issues.apache.org/jira/browse/IGNITE-6851 Project: Ignite

Re: [DISUCSS] Ticket filing process

Ok, I see. Then the question is when to do a review? On Wed, Nov 8, 2017 at 9:19 AM, Dmitriy Setrakyan wrote: > On Wed, Nov 8, 2017 at 1:32 PM, Vladimir Ozerov > wrote: > > > Dima, > > > > What is the problem you are trying to solve? I am not sure I

[GitHub] ignite pull request #3003: IGNITE-6762: SparseDistributedMatrixExample faile...

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

[GitHub] ignite pull request #3009: IGNITE-6849: Failed k-means tests with multiple n...

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

[GitHub] ignite pull request #3010: IGNITE-6818 - Handle half open connection in comm...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/3010 IGNITE-6818 - Handle half open connection in communication. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #3009: Ignite 6849

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

[jira] [Created] (IGNITE-6850) SQL: integrate index inline size to CREATE INDEX syntax

Vladimir Ozerov created IGNITE-6850: --- Summary: SQL: integrate index inline size to CREATE INDEX syntax Key: IGNITE-6850 URL: https://issues.apache.org/jira/browse/IGNITE-6850 Project: Ignite

[GitHub] ignite pull request #3006: IGNITE-6848

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

[GitHub] ignite pull request #3008: IGNITE-3244: fix for custom arrays properly seria...

GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/3008 IGNITE-3244: fix for custom arrays properly serialization You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3244

[GitHub] ignite pull request #3007: IGNITE-6844

GitHub user xtern opened a pull request: https://github.com/apache/ignite/pull/3007 IGNITE-6844 You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-6844 Alternatively you can review and apply these changes as

[jira] [Created] (IGNITE-6849) Failed k-means tests with multiple nodes

Yury Babak created IGNITE-6849: -- Summary: Failed k-means tests with multiple nodes Key: IGNITE-6849 URL: https://issues.apache.org/jira/browse/IGNITE-6849 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #3006: IGNITE-6848

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

[GitHub] ignite pull request #3005: IGNITE-6735: Java 9: fix Java version resolution/...

GitHub user OSa86 opened a pull request: https://github.com/apache/ignite/pull/3005 IGNITE-6735: Java 9: fix Java version resolution/check logic You can merge this pull request into a Git repository by running: $ git pull https://github.com/OSa86/ignite ignite-6735

[jira] [Created] (IGNITE-6848) SQL parser: support DROP INDEX command

Vladimir Ozerov created IGNITE-6848: --- Summary: SQL parser: support DROP INDEX command Key: IGNITE-6848 URL: https://issues.apache.org/jira/browse/IGNITE-6848 Project: Ignite Issue Type:

[GitHub] ignite pull request #3001: IGNITE-6840

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