[jira] [Created] (IGNITE-7041) Web Console: Incorrect code generation in case if cache has eviction policy and near cache with eviction policy

Pavel Konstantinov created IGNITE-7041: -- Summary: Web Console: Incorrect code generation in case if cache has eviction policy and near cache with eviction policy Key: IGNITE-7041 URL:

Re: TC issues. IGNITE-3084. Spark Data Frame API

Hello, Valentin. Added '-Dscala-2.10' to the build config. Let me know if it helps. Yes, it helps. Thank you! Now, 'Ignite RDD spark 2_10' succeed for my branch. Do you mean that IgniteRDD does not compile on JDK7? If yes, do we know the reason? I don't think switching it to JDK8 is a

[jira] [Created] (IGNITE-7042) Test written in scala doesn't executed on TC

Nikolay Izhikov created IGNITE-7042: --- Summary: Test written in scala doesn't executed on TC Key: IGNITE-7042 URL: https://issues.apache.org/jira/browse/IGNITE-7042 Project: Ignite Issue

[jira] [Created] (IGNITE-7043) Incorrect method name suggested when page eviction starts

Ilya Kasnacheev created IGNITE-7043: --- Summary: Incorrect method name suggested when page eviction starts Key: IGNITE-7043 URL: https://issues.apache.org/jira/browse/IGNITE-7043 Project: Ignite

[GitHub] ignite pull request #3014: IGNITE-6406: SQL: CREATE INDEX should fill index ...

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

[GitHub] ignite pull request #3101: Compress with ssl

GitHub user NSAmelchev opened a pull request: https://github.com/apache/ignite/pull/3101 Compress with ssl You can merge this pull request into a Git repository by running: $ git pull https://github.com/NSAmelchev/ignite comress-with-ssl Alternatively you can review and

[GitHub] ignite pull request #3102: Ignite-6339-buf-overflow

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/3102 Ignite-6339-buf-overflow You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-6339-buf-overflow Alternatively you can

[GitHub] ignite pull request #3103: IGNITE-7043 Fix method name suggested when page e...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/3103 IGNITE-7043 Fix method name suggested when page eviction starts You can merge this pull request into a Git repository by running: $ git pull https://github.com/alamar/ignite patch-1

[jira] [Created] (IGNITE-7050) Add support for spring3

Mikhail Cherkasov created IGNITE-7050: - Summary: Add support for spring3 Key: IGNITE-7050 URL: https://issues.apache.org/jira/browse/IGNITE-7050 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-7048) Cache get fails on node not in BaselineTopology.

Sergey Chugunov created IGNITE-7048: --- Summary: Cache get fails on node not in BaselineTopology. Key: IGNITE-7048 URL: https://issues.apache.org/jira/browse/IGNITE-7048 Project: Ignite

[GitHub] ignite pull request #3105: ignite-gg-13099

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

[GitHub] ignite pull request #3106: Ignite PDS compatibilty framework fixes

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3106 Ignite PDS compatibilty framework fixes dependencies declaration, debug stuff added You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-7049) Optimistic transaction is not properly rolled back if timed out before sending prepare response.

Alexei Scherbakov created IGNITE-7049: - Summary: Optimistic transaction is not properly rolled back if timed out before sending prepare response. Key: IGNITE-7049 URL:

Re: FOR UPDATE support in SELECT clause

In this case you lock rows, but there are not subsequent operation which will use this lock. FOR UPDATE only makes sense as a part of transaction. On Tue, Nov 28, 2017 at 4:56 PM, Dmitriy Setrakyan wrote: > On Tue, Nov 28, 2017 at 12:34 AM, Vladimir Ozerov

[jira] [Created] (IGNITE-7047) NPE at org.jsr166.ConcurrentLinkedHashMap.replace

Alexey Popov created IGNITE-7047: Summary: NPE at org.jsr166.ConcurrentLinkedHashMap.replace Key: IGNITE-7047 URL: https://issues.apache.org/jira/browse/IGNITE-7047 Project: Ignite Issue

Optimization of SQL queries from Spark Data Frame to Ignite

Hello, guys. I have implemented basic support of Spark Data Frame API [1], [2] for Ignite. Spark provides API for a custom strategy to optimize queries from spark to underlying data source(Ignite). The goal of optimization(obvious, just to be on the same page): Minimize data transfer between

[jira] [Created] (IGNITE-7051) SQL Rename table support

Blackfield created IGNITE-7051: -- Summary: SQL Rename table support Key: IGNITE-7051 URL: https://issues.apache.org/jira/browse/IGNITE-7051 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-7046) Client queries should throw a correct exception

Kirill Shirokov created IGNITE-7046: --- Summary: Client queries should throw a correct exception Key: IGNITE-7046 URL: https://issues.apache.org/jira/browse/IGNITE-7046 Project: Ignite Issue

[jira] [Created] (IGNITE-7045) Client queries should throw a correct exception

Kirill Shirokov created IGNITE-7045: --- Summary: Client queries should throw a correct exception Key: IGNITE-7045 URL: https://issues.apache.org/jira/browse/IGNITE-7045 Project: Ignite Issue

[GitHub] ignite pull request #3091: IGNITE-7013 .NET: Fix startup on macOS (dlopen ca...

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

Re: [!!Mass Mail]Re: Ignite Enhancement Proposal #7 (Internal problems detection)

Vladimir, These policies (policy, in fact) can be configured in IgniteConfiguration by calling setFailureProcessingPolicy(FailureProcessingPolicy flrPlc) method. -- Дмитрий Сорокин Тел.: 8-789-13512 Моб.: +7 (916) 560-39-63 28.11.17, 10:28 пользователь "Vladimir Ozerov"

[jira] [Created] (IGNITE-7044) SQL: Documentation for the PARALLEL statement in the CREATE INDEX command

Roman Kondakov created IGNITE-7044: -- Summary: SQL: Documentation for the PARALLEL statement in the CREATE INDEX command Key: IGNITE-7044 URL: https://issues.apache.org/jira/browse/IGNITE-7044

[GitHub] ignite pull request #3104: Ignite-6339-hdr-buf

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/3104 Ignite-6339-hdr-buf You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-6339-hdr-buf Alternatively you can review and

[jira] [Created] (IGNITE-7052) S3 IP finder: add an ability to provide endpoint address

Valentin Kulichenko created IGNITE-7052: --- Summary: S3 IP finder: add an ability to provide endpoint address Key: IGNITE-7052 URL: https://issues.apache.org/jira/browse/IGNITE-7052 Project:

Re: Ignite Enhancement Proposal #7 (Internal problems detection)

I think the failure processing policy should be configured via IgniteConfiguration in a way similar to the segmentation policies. — Denis > On Nov 27, 2017, at 11:28 PM, Vladimir Ozerov wrote: > > Dmitry, > > How these policies will be configured? Do you have any API in

Re: FOR UPDATE support in SELECT clause

On Tue, Nov 28, 2017 at 12:34 AM, Vladimir Ozerov wrote: > I do not see any use case for this. Why would you want to do this? > Atomic cache supports locking to my knowledge. The use case would be identical in SQL use case - to lock a row. Why not?

Re: Ignite node crashes after one query fetches many entries from cache

Ignite Developers, I know community is developing an "Internal Problems Detection" feature . Do you know if it addresses the problem Ray described below? May be we already have a setting to prevent

Apache Ignite Talk at Nike HQ: DEC 14

Hi Apache Ignite Devs, For those of you in the Pacific Northwest, I will be giving a talk at Nike’s Headquarters on Apache Ignite: https://niketechtalksdec2017.splashthat.com You are welcome to join or send this on to others in the area! Thanks kindly, Dani

[jira] [Created] (IGNITE-7055) Text query for a particular field not working

Valentin Kulichenko created IGNITE-7055: --- Summary: Text query for a particular field not working Key: IGNITE-7055 URL: https://issues.apache.org/jira/browse/IGNITE-7055 Project: Ignite

Re: TC issues. IGNITE-3084. Spark Data Frame API

Valentin, For now `Ignite RDD` build runs on jdk1.7. We need to update it to jdk1.8. I wrote the whole versions numbers to be clear: 1. Current master - Spark version is 2.1.0. So both `Ignite RDD` and `Ignite RDD 2.10` runs OK on jdk1.7. 2. My branch - `Ignite RDD 2.10` -

[jira] [Created] (IGNITE-7064) Web console: implement mechanism to

Ilya Borisov created IGNITE-7064: Summary: Web console: implement mechanism to Key: IGNITE-7064 URL: https://issues.apache.org/jira/browse/IGNITE-7064 Project: Ignite Issue Type: Improvement

Re: Rework storage format to index-organized approach

Denis, No, most likely free lists (or any other space management component) will stay still. But in case of index-organized storage we will use it in less number of scenarios. On Tue, Nov 28, 2017 at 6:27 AM, Dmitriy Setrakyan wrote: > Vladimir, > > I definitely like the

Re: Optimization of SQL queries from Spark Data Frame to Ignite

Nikolay, Regarding p3. - partition pruning is already implemented in Ignite, so there is no need to do this on your own. On Wed, Nov 29, 2017 at 3:23 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Nikolay, > > Custom strategy allows to fully process the AST generated by Spark

Re: Ignite Enhancement Proposal #7 (Internal problems detection)

Denis, Yes, but can we look at proposed API before we dig into implementation? On Tue, Nov 28, 2017 at 9:43 PM, Denis Magda wrote: > I think the failure processing policy should be configured via > IgniteConfiguration in a way similar to the segmentation policies. > > — >

Re: Ignite page with video resources and recordings

Sounds like a good idea. On Tue, Nov 28, 2017 at 5:16 PM, Denis Magda wrote: > Igniters, > > There is a plenty of recordings of Ignite meetups, webinars and conference > talks available on the Internet. Some of them introduce basic components > and capabilities, some share

Re: Rework storage format to index-organized approach

Dima, 1) Primary key lookups could become a bit faster, but no breakthrough is expected - there will be no need to jump from B+Tree leaf to data page, but the tree itself will be bigger, because data records will take more space than index records. I expect parity here. 2) We should observe

[jira] [Created] (IGNITE-7063) Web console: improve error handling in case of custom SMTP server

Pavel Konstantinov created IGNITE-7063: -- Summary: Web console: improve error handling in case of custom SMTP server Key: IGNITE-7063 URL: https://issues.apache.org/jira/browse/IGNITE-7063

[GitHub] ignite pull request #3103: IGNITE-7043 Fix method name suggested when page e...

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

Activate/deactivate cluster through http-rest api

Engineers, Any progress regarding this issue [1]? [1] https://issues.apache.org/jira/browse/IGNITE-5733?focusedCommentId=16225941=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16225941 Thanks, -Prachi

Re: Integration of Spark and Ignite. Prototype.

Guys, Looking into the parallel discussion about the strategy support I would change my initial stance and support the idea of releasing the integration in its current state. Is the code ready to be merged into the master? Let’s concentrate on this first and handle the strategy support as a

Re: Apache Ignite Talk at Nike HQ: DEC 14

+ user list Dani, excellent news and good luck! We’ve added an announcement to Ignite events page to draw more attention: https://ignite.apache.org/events.html#niketechtalksdec2017 — Denis > On Nov 28, 2017, at 1:45 PM, Dani Traphagen wrote: > > Hi Apache Ignite Devs, > >

Re: FOR UPDATE support in SELECT clause

On Mon, Nov 27, 2017 at 11:33 PM, Vladimir Ozerov wrote: > Hi Denis, > > "FOR UPDATE" is not supported at the moment. We will add it's support for > transactional case [1]. In non-transactional case it would behave in the > same way as normal SELECT. > Why only for

Re: FOR UPDATE support in SELECT clause

I do not see any use case for this. Why would you want to do this? On Tue, Nov 28, 2017 at 11:18 AM, Dmitriy Setrakyan wrote: > On Mon, Nov 27, 2017 at 11:33 PM, Vladimir Ozerov > wrote: > > > Hi Denis, > > > > "FOR UPDATE" is not supported at the

[jira] [Created] (IGNITE-7060) Prepare Architecture section for the site

Denis Magda created IGNITE-7060: --- Summary: Prepare Architecture section for the site Key: IGNITE-7060 URL: https://issues.apache.org/jira/browse/IGNITE-7060 Project: Ignite Issue Type: Task

Re: Reworking Ignite site's "Features" menu

Dmitriy, Thanks for the feedback. Split all the work into a set of JIRA tasks aggregated under this one: https://issues.apache.org/jira/browse/IGNITE-7061 Hope to complete it by the end of the year. — Denis > On Nov 22, 2017, at 5:03 PM,

Ignite page with video resources and recordings

Igniters, There is a plenty of recordings of Ignite meetups, webinars and conference talks available on the Internet. Some of them introduce basic components and capabilities, some share best practices and pitfalls while the other share use cases. Generally, it's beneficial for both Ignite

[jira] [Created] (IGNITE-7056) Prepare Multi-Language support page for the site

Denis Magda created IGNITE-7056: --- Summary: Prepare Multi-Language support page for the site Key: IGNITE-7056 URL: https://issues.apache.org/jira/browse/IGNITE-7056 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7057) Create Key-Value Page for the site

Denis Magda created IGNITE-7057: --- Summary: Create Key-Value Page for the site Key: IGNITE-7057 URL: https://issues.apache.org/jira/browse/IGNITE-7057 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-7058) Make out a site page for ACID Transactions

Denis Magda created IGNITE-7058: --- Summary: Make out a site page for ACID Transactions Key: IGNITE-7058 URL: https://issues.apache.org/jira/browse/IGNITE-7058 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-7061) Rework Features menu and page

Denis Magda created IGNITE-7061: --- Summary: Rework Features menu and page Key: IGNITE-7061 URL: https://issues.apache.org/jira/browse/IGNITE-7061 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-7062) Ignite page with video resources and recording

Denis Magda created IGNITE-7062: --- Summary: Ignite page with video resources and recording Key: IGNITE-7062 URL: https://issues.apache.org/jira/browse/IGNITE-7062 Project: Ignite Issue Type: