[jira] [Created] (IGNITE-6229) Web console: Errors in project code generation

Vasiliy Sisko created IGNITE-6229: - Summary: Web console: Errors in project code generation Key: IGNITE-6229 URL: https://issues.apache.org/jira/browse/IGNITE-6229 Project: Ignite Issue Type:

[GitHub] ignite pull request #2523: IGNITE-6115: Ignore page eviction mode if Ignite ...

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

IgniteFuture -> CompletableFuture

Igniters, I received the following proposal in my blog. I think this is useful. Any thoughts? Please extend IgniteFuture by conversion method to CompletableFuture. I > bored to write something like this: > asyncCache.invoke(key, entryProcessor); > CompletableFuture completableFuture = new Compl

Re: Override cache name created with CREATE TABLE

I think Denis' idea makes sense. Vladimir, what do you think? D. On Wed, Aug 30, 2017 at 2:57 AM, Denis Magda wrote: > Igniters, > > That’s one more feedback about CREATE TABLE usage in practice. > > The command automatically creates an IgniteCache naming it > SQL_PUBLIC_{TABLE}. So, if a Pers

Re: Cluster auto activation design proposal

Hm... Can we also ask user to optionally provide a predicate which will receive a collection of nodes started so far and return true if the activation should happen? Will it be useful? On Wed, Aug 30, 2017 at 6:28 PM, Sergey Chugunov wrote: > Nick, > > As I summed up in this thread above, callin

Re: Ignite Durable Memory & Persistent Store introduction for developers

Dmitriy, this is very useful! Any chance you can also blog about it? On Wed, Aug 30, 2017 at 6:24 PM, Dmitry Pavlov wrote: > Hi Igniters, > > > I am glad to introduce two new wiki articles. These articles contain > high-level description of > > - Ignite Durable Memory ( > https://cwiki.apache.or

Re: Yardstick framework for Ignite 2.1

Alexey, I am seeing that some code was removed. Are we offering to users to try the benchmarks shipped with Ignite instead? On Wed, Aug 30, 2017 at 7:40 PM, Aleksei Zaitsev wrote: > Have done just like we discussed. > > PR: https://github.com/apacheignite/yardstick-ignite/pull/6 > > 24.08.2017,

Re: Redesigning Ignite's site Look & Feel

Chris, Both Prachi and me have merged a lot of changes to trunk recently. Do you keep your copy in sync? How close are you to finish your part? Let me know if my help is needed. — Denis > On Aug 17, 2017, at 1:11 AM, Christos Erotocritou > wrote: > > Hello, try again now. This is hosted cur

Re: sql documentation

On Wed, Aug 30, 2017 at 10:04 PM, Denis Magda wrote: > Serge, > > Undoubtedly, I like this format. I’ve created a new documentation domain > for all our SQL capabilities: > https://apacheignite-sql.readme.io/docs readme.io/docs> > > Once I get an open source license f

Re: [DISCUSSION] Urgent Ignite bug fix release

To be honnest we check heap memory which is used by all Ignite nodes on the host: org.apache.ignite.internal.IgniteKernal#checkPhysicalRam Shouldn't we do the same for offheap? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Adding sqlline tool to Apache Ignite project

Denis, I’m glad you’re thinking of using SQLLine. Under the BSD license, you don’t need my permission to distribute, but I grant that permission. Drill, Phoenix and Calcite already distribute SQLLine, so Ignite is in good company. If you need extensions, please discuss on the dev list, or open

Re: [DISCUSSION] Urgent Ignite bug fix release

Your suggestions sounds reasonable to me. Are they only about the calculations at the code level or you propose to change the message format too? — Denis > On Aug 30, 2017, at 3:24 AM, Vladimir Ozerov wrote: > > I looked at the code of IGNITE-6182 (memory policy suggestions), and I do > not li

Re: sql documentation

Serge, Undoubtedly, I like this format. I’ve created a new documentation domain for all our SQL capabilities: https://apacheignite-sql.readme.io/docs Once I get an open source license for it we can start moving the existing docs and create the new ther

Re: [DISCUSSION] Urgent Ignite bug fix release

IGNITE-6128 is not merged yet. I already raised my concerns, please chime in. ср, 30 авг. 2017 г. в 21:45, Denis Magda : > Have the all pre-release tests passed? If so, let’s kick off the vote. > > — > Denis > > > On Aug 30, 2017, at 4:29 AM, Anton Vinogradov > wrote: > > > > 1) Fixes for: > > -

Re: [DISCUSSION] Urgent Ignite bug fix release

Have the all pre-release tests passed? If so, let’s kick off the vote. — Denis > On Aug 30, 2017, at 4:29 AM, Anton Vinogradov > wrote: > > 1) Fixes for: > - https://issues.apache.org/jira/browse/IGNITE-6204 > - https://issues.apache.org/jira/browse/IGNITE-6193 > merged > > 2) https://issues.

[GitHub] ignite pull request #2556: ignite-6181

GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/2556 ignite-6181 Tx is not rolled back on timeout leading to potential whole grid hang You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/

Re: P2P Deployment - Local Ownership Flag

Hi Igniters, I assume this may be related to case desctibed by user in http://apache-ignite-users.70518.x6.nabble.com/Understanding-the-mechanics-of-peer-class-loading-td12661.html We didn't managed to create a reproducer for this issue. But case is similar: - server has cache classes in it

Re: Yardstick framework for Ignite 2.1

Have done just like we discussed. PR: https://github.com/apacheignite/yardstick-ignite/pull/6 24.08.2017, 02:02, "Dmitriy Setrakyan" : > I would delete all the code from the Yardstick repo to avoid confusion and > in the description of the repo ask users to download Ignite directly. > > On Wed, A

[GitHub] ignite pull request #2553: IGNITE-5931 .NET: Fix type registration race cond...

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

Re: Ignite Durable Memory & Persistent Store introduction for developers

Awesome! Thanks! On Wed, Aug 30, 2017 at 6:24 PM, Dmitry Pavlov wrote: > Hi Igniters, > > > I am glad to introduce two new wiki articles. These articles contain > high-level description of > > - Ignite Durable Memory ( > https://cwiki.apache.org/confluence/display/IGNITE/ > Ignite+Durable+Memory

[GitHub] ignite pull request #2555: IGNITE-6081 .NET: Fix PutAll for dependent object...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2555 IGNITE-6081 .NET: Fix PutAll for dependent objects You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-6081 Alternativel

Re: Cluster auto activation design proposal

Nick, As I summed up in this thread above, calling setter for initial activation nodes is not the only option: 1. user starts up new cluster of desired number of nodes and activates it using existing API. BLT is created with all nodes presented in the cluster at the moment of activati

Ignite Durable Memory & Persistent Store introduction for developers

Hi Igniters, I am glad to introduce two new wiki articles. These articles contain high-level description of - Ignite Durable Memory ( https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood ) - and Ignite Persistent Store ( https://cwiki.apache.org/confluence/d

[jira] [Created] (IGNITE-6228) Avoid closing page store file with ClosedByInterruptException when user thread is interrupted

Ivan Rakov created IGNITE-6228: -- Summary: Avoid closing page store file with ClosedByInterruptException when user thread is interrupted Key: IGNITE-6228 URL: https://issues.apache.org/jira/browse/IGNITE-6228

[jira] [Created] (IGNITE-6227) Delete obsolete benchmarks for Ignite 1.9

Aleksei Zaitsev created IGNITE-6227: --- Summary: Delete obsolete benchmarks for Ignite 1.9 Key: IGNITE-6227 URL: https://issues.apache.org/jira/browse/IGNITE-6227 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6226) Review docs for integration with Apache Zeppelin

Ilya Suntsov created IGNITE-6226: Summary: Review docs for integration with Apache Zeppelin Key: IGNITE-6226 URL: https://issues.apache.org/jira/browse/IGNITE-6226 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6225) Improve tests of WAL iterator with checking DataRecord entries and TxRecords

Dmitriy Pavlov created IGNITE-6225: -- Summary: Improve tests of WAL iterator with checking DataRecord entries and TxRecords Key: IGNITE-6225 URL: https://issues.apache.org/jira/browse/IGNITE-6225 Proj

[GitHub] ignite pull request #2554: Ignite 5569 Fix

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

[GitHub] ignite pull request #2553: IGNITE-5931 .NET: Fix type registration race cond...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2553 IGNITE-5931 .NET: Fix type registration race condition You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-5931 Alternat

[GitHub] ignite pull request #2552: IGNITE-6139 Actual version info in Thick JDBC met...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/2552 IGNITE-6139 Actual version info in Thick JDBC metadata queries. Also fix Product Name to "Apache Ignite" You can merge this pull request into a Git repository by running: $ git pull https://git

Re: ContinuousQueryWithTransformer implementation questions - 2

I would postpone review until we come to a clear decision on what should be done if filter or transformer fails. I don't think cancelling query is too much. From my standpoint this is a kind of heuristic exception and may break some sensitive logic. Thanks! -- Yakov Zhdanov, Director R&D *GridGain

Re: ContinuousQueryWithTransformer implementation questions - 2

Nikolay, You can also use: 1) Global Exception Registry ctx.kernalContext().exceptionRegistry().onException(shortMsg, ex); 2) Statistic final boolean statsEnabled = cctx.config().isStatisticsEnabled(); if (statsEnabled) metrics.incrementOnFails(); P.s. Please make sure that code still valid,

[GitHub] ignite pull request #2551: Ignite 4756 Print info about partition distributi...

GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/2551 Ignite 4756 Print info about partition distribution to log You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-4756-new

P2P Deployment - Local Ownership Flag

Igniters, esp. Alex Goncharuk, There was a problem recently discovered with org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager#locDepOwner As far as I remember, this flag is automatically set if Ignite detects public API usage outside of deployment class loader that implies t

[GitHub] ignite pull request #2550: ignite-gg-12723 Optimistic tx recovery fixed

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/2550 ignite-gg-12723 Optimistic tx recovery fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-gg-12723 Alternativel

[GitHub] ignite pull request #2043: IGNITE-5097: writing arrays length in varint enco...

Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/2043 --- 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 #2549: IGNITE-5097 BinaryMarshaller should write ints in...

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/2549 IGNITE-5097 BinaryMarshaller should write ints in "varint" encoding where it makes sense You can merge this pull request into a Git repository by running: $ git pull https://github.com/dar

Re: ContinuousQueryWithTransformer implementation questions - 2

Hello, Yakov. The new class is OK - got it. Thanks! > Should we extract a super class? Yes, we should. I already have done it. See my last commit in PR - https://github.com/apache/ignite/pull/2372/commits/af1ed2e4dbef4ba5999f8566198cb75ad922f93b > We can put hard requirement that filter and

Re: Cluster auto activation design proposal

How is a user expected to produce a collection of ClusterNode prior to all of the expected nodes joining? Users don't create instances of this, so as far as I can tell it would have to be retrieved from IgniteCluster. However, would doing that and calling the proposed method be really any different

[GitHub] ignite pull request #2503: Ignite 4756 Print info about partition distributi...

Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/2503 --- 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 #2506: IGNITE-6125 Increase robustness of JDBC Metadata

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

Re: ContinuousQueryWithTransformer implementation questions - 2

I think I have already agreed on a separate class since it seems to be the only option due to generics issue. Should we extract a super class? We can put hard requirement that filter and transformer cannot throw exception (same as cache interceptor). If exception is thrown then we cancel the query

[GitHub] ignite pull request #2537: IGNITE-6193 ML profile is missing in 2.1 binary r...

Github user oignatenko closed the pull request at: https://github.com/apache/ignite/pull/2537 --- 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 #2548: IGNITE-6219 - IgniteCache#loadCache executes loca...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/2548 IGNITE-6219 - IgniteCache#loadCache executes local load in caller thread You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-

Re: sql documentation

Sorry for inconvenience! there is a link for a sample: https://drive.google.com/open?id=0B-s4Ivq-lrPobzZ4c2Y1X1ZLcWhGenE4TllVM3VlODhtT2Iw Serge > On 29 Aug 2017, at 19:30, Denis Magda wrote: > > Serge, > > The attachment is missing. Try to share it via google drive or other storage. > > — > D

Re: [DISCUSSION] Urgent Ignite bug fix release

1) Fixes for: - https://issues.apache.org/jira/browse/IGNITE-6204 - https://issues.apache.org/jira/browse/IGNITE-6193 merged 2) https://issues.apache.org/jira/browse/IGNITE-6003 resolved as duplicate to https://issues.apache.org/jira/browse/IGNITE-6182 3) Current list if issues related to release

[GitHub] ignite pull request #2547: Ignite 1.7.15 4557

GitHub user mcherkasov opened a pull request: https://github.com/apache/ignite/pull/2547 Ignite 1.7.15 4557 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.7.15-4557 Alternatively you can review a

[GitHub] ignite pull request #1488: IGNITE-4645

Github user gvvinblade closed the pull request at: https://github.com/apache/ignite/pull/1488 --- 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 #1499: ignite-4646

Github user gvvinblade closed the pull request at: https://github.com/apache/ignite/pull/1499 --- 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-6224) Node stoping does not wait all transactions completion

Vladislav Pyatkov created IGNITE-6224: - Summary: Node stoping does not wait all transactions completion Key: IGNITE-6224 URL: https://issues.apache.org/jira/browse/IGNITE-6224 Project: Ignite

Re: [DISCUSSION] Urgent Ignite bug fix release

I looked at the code of IGNITE-6182 (memory policy suggestions), and I do not like it. Too complex. My proposal: 1) Do not take in count JVM heap. First, we do not need whether it will be really used or not. Second, we never checked it in heap-based Ignite 1.x, and never had a single compliant. 2)

Re: CREATE TABLE usage from Java API, .NET, C++

Folks, Please see this [1] and this [2]. [1] http://apache-ignite-developers.2346864.n4.nabble.com/Rethink-native-SQL-API-in-Apache-Ignite-2-0-td14335.html [2] https://issues.apache.org/jira/browse/IGNITE-4701 On Wed, Aug 30, 2017 at 3:10 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com>

[jira] [Created] (IGNITE-6223) Web console: Agent faile to send task result on job fail.

Vasiliy Sisko created IGNITE-6223: - Summary: Web console: Agent faile to send task result on job fail. Key: IGNITE-6223 URL: https://issues.apache.org/jira/browse/IGNITE-6223 Project: Ignite

[GitHub] ignite pull request #2546: IGNITE-6213

GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/2546 IGNITE-6213 Unexpected setting local deployment owner anyone node You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite igni

[jira] [Created] (IGNITE-6222) Adapt Linear regression for distributed enviroment

Yury Babak created IGNITE-6222: -- Summary: Adapt Linear regression for distributed enviroment Key: IGNITE-6222 URL: https://issues.apache.org/jira/browse/IGNITE-6222 Project: Ignite Issue Type: B

Re: .NET: Iterating collections via interfaces can impact peformance

Hi Mike, I'm aware of this issue and usually try to keep an eye on it. Can you list your findings? I see BinaryProcessor.PutBinaryTypes and Marshaller.OnBinaryTypesSent, anything else? Pavel On Wed, Aug 30, 2017 at 10:41 AM, wrote: > > Dear Igniters, > > Whilst checking out BenchmarkDotNet (t

Re: Cluster auto activation design proposal

Dmitriy, Now I see your point and I think you're right. We can give end-user a simple setter like Ignite::activation::setInitialActivationNodes(Collection nodes) to provide collection of nodes that grid must reach to activate automatically. And then using the collection we'll create BaselineTopo

Re: ContinuousQueryWithTransformer implementation questions - 2

Semyon, Yakov, Here is ticket - https://issues.apache.org/jira/browse/IGNITE-6221 Thank you. Can we now return to my questions about IGNITE-425? 1. I introduce new query class - ContinuousQueryWithTransformer [3]. Reasons: * ContinuousQuery is final so user can't extends it. I don't want to ch

[jira] [Created] (IGNITE-6221) ContinuousQuery. Local listener notified if filter throws exception

Nikolay Izhikov created IGNITE-6221: --- Summary: ContinuousQuery. Local listener notified if filter throws exception Key: IGNITE-6221 URL: https://issues.apache.org/jira/browse/IGNITE-6221 Project: Ig

.NET: Iterating collections via interfaces can impact peformance

Dear Igniters, Whilst checking out BenchmarkDotNet (thanks Pavel!) I came across this issue [1].  There is some useful discussion in [2] under "Dictionary vs IDictionary". It seems that iterating collections via their interfaces has performance implications, specifically that iterating interfac

Re: ContinuousQueryWithTransformer implementation questions - 2

Hi, I had an impression that current behavior is required by jcache, but now I can not find anything about this neither in spec nor in jcache tck tests. So I think we can change current behavior. Thanks On Tue, Aug 29, 2017 at 9:48 PM, Nikolay Izhikov wrote: > Yakov. > > I found following desc