[GitHub] ignite pull request #1355: IGNITE-4440

GitHub user prokofyev opened a pull request: https://github.com/apache/ignite/pull/1355 IGNITE-4440 Added bcastCall() method to ScalarProjectionPimp scalar class. You can merge this pull request into a Git repository by running: $ git pull https://github.com/prokofyev/ignite

[jira] [Created] (IGNITE-4440) scalar misses bcastCall() in ScalarProjectionPimp class

Alexander Prokofyev created IGNITE-4440: --- Summary: scalar misses bcastCall() in ScalarProjectionPimp class Key: IGNITE-4440 URL: https://issues.apache.org/jira/browse/IGNITE-4440 Project: Ignite

[RESULT] [VOTE] Apche Ignite PMC Chair Election

Time to do the final tally. Vladimir Ozerov, binding: 0, non-binding: 1 Konstantin Boudnik, binding: 3, non-binding: 1 Valentin Kulichenko, binding: 0, non-binding: 0 Denis Magda, binding: 7, non-binding: 1 Branko Čibej - withdrawn his candidacy Denis Magda has been elected as the new Apache

Re: Striped pool configuration

Yakov, thanks. Here are some thoughts from the Son of the Earth :) > Another reason for not switching to striped pool completely is that stripes > are good for cache updates and single or batched get operations since they > reduce inter-thread communication and synchronization to minimum How

Re: Striped pool configuration

Yakov, I think that our thread pool configuration is getting overly complex. I am reading your reasoning for having both, old and striped thread pools, and even I get confused, even though I have written some of this code myself. In my view, we should hide most of such configuration intricacies

Re: Striped pool configuration

>In this case users will not be able to perform synchronous cache operations from compute tasks, right? why? you are still free to do this. --Yakov

Re: Striped pool configuration

In this case users will not be able to perform synchronous cache operations from compute tasks, right? On Thu, Dec 15, 2016 at 11:05 PM, Yakov Zhdanov wrote: > do you agree with the point that we need to keep pub and sys pool together > with striped pool for now? > >

Fwd: Striped pool configuration

do you agree with the point that we need to keep pub and sys pool together with striped pool for now? --Yakov

[jira] [Created] (IGNITE-4439) Create attribute based node filter

Valentin Kulichenko created IGNITE-4439: --- Summary: Create attribute based node filter Key: IGNITE-4439 URL: https://issues.apache.org/jira/browse/IGNITE-4439 Project: Ignite Issue

Re: Striped pool configuration

Yakov, Not really :-) I asked on how to better expose it's configuration to API, not about it's internals. On Thu, Dec 15, 2016 at 10:22 PM, Yakov Zhdanov wrote: > Denis, there was no discussion on dev list. Do not worry, Son of the Earth, > you are all right :) I

Fwd: Striped pool configuration

Denis, there was no discussion on dev list. Do not worry, Son of the Earth, you are all right :) I thought I would send letter a bit later when I finish the full scope of optimizations I have in plan. Currently, I use striped pool only for cache messages that are targeted to some defined

Re: [VOTE] Apche Ignite PMC Chair Election

Denis Magda On Thu, Dec 15, 2016 at 6:22 PM, Anton Vinogradov wrote: > Denis Magda > > P.s. 72 hours is not enough for such votes. > > On Thu, Dec 15, 2016 at 3:52 AM, Rohit Mohta > wrote: > > > Vladimir Ozerov > > > > > > > > > On Dec 14,

Re: Access to apacheignite-mix.readme.io

Thanks, Denis, I've received and accepted it. Best Regards, Igor On Thu, Dec 15, 2016 at 7:03 PM, Denis Magda wrote: > Hi Igor, > > Awesome news. I’ve sent you the invitation. > > — > Denis > > > On Dec 15, 2016, at 5:13 AM, Igor Sapego wrote: > > > >

Re: Striped pool configuration

Igniters, Why not just move to striped pools and remove this confusion? At this point we are forcing users to understand what a striped pool is, which seems unnecessary in my view. D. On Thu, Dec 15, 2016 at 8:09 AM, Denis Magda wrote: > Vladimir, > > > On Dec 15, 2016, at

Re: greetings

Hi Sergey, Welcome to the Ignite community! Please subscribe to both dev and user lists: https://ignite.apache.org/community/resources.html#mail-lists Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

[GitHub] ignite pull request #1353: IGNITE-4408: IndexingSpi supports BinaryObjects

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1353 IGNITE-4408: IndexingSpi supports BinaryObjects Allow BinaryObjects to be passed to IndexinSpi implementation. You can merge this pull request into a Git repository by running: $ git pull

Re: Striped pool configuration

Vladimir, > On Dec 15, 2016, at 1:22 AM, Vladimir Ozerov wrote: > > One of them is "striped pool" which can be used instead of current system > pool. Would you mind explaining the whole purpose of this pool and why it was decided to introduce it? If I missed some

[GitHub] ignite pull request #1351: IndexingSpi supports BinaryObjects

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

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1352 Igntie-4408 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite igntie-4408 Alternatively you can review and apply

Re: Access to apacheignite-mix.readme.io

Hi Igor, Awesome news. I’ve sent you the invitation. — Denis > On Dec 15, 2016, at 5:13 AM, Igor Sapego wrote: > > Hello, Igniters, > > I want to start working on the following ticket: [1]. > To do so I need a write access to [2]. Can someone from community help me? >

[GitHub] ignite pull request #1351: IndexingSpi supports BinaryObjects

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1351 IndexingSpi supports BinaryObjects Allow BinaryObjects to be passed to IndexinSpi implementation. You can merge this pull request into a Git repository by running: $ git pull

greetings

Greetings! My name is Sergey and I'd like to join and contribute to Ignite. Best Regards, Sergey

[GitHub] ignite pull request #1350: IGNITE-4169 DML integration w/data streamer

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/1350 IGNITE-4169 DML integration w/data streamer You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4169

[jira] [Created] (IGNITE-4438) Remove old branch from Ignite's git repo

Rohit Mohta created IGNITE-4438: --- Summary: Remove old branch from Ignite's git repo Key: IGNITE-4438 URL: https://issues.apache.org/jira/browse/IGNITE-4438 Project: Ignite Issue Type: Wish

Re: API to collect list of running SQL queries

Dmitriy, Yes, that is what I'm going to do as first prototype. But, I would prefer to discuss API with experts. As Vladimir mentioned, there a usability use case with queries that also could be discussed. Sergi, could you, please, point a proper class where such API (for collecting list of

Re: API to collect list of running SQL queries

Alexey, How about you only look at the client side, which obviously has the full query? D. On Thu, Dec 15, 2016 at 1:35 AM, Alexey Kuznetsov wrote: > I like Vladimir idea. > > May be we could *compress* large strings? > Or may be we could have API to ask for *string

[GitHub] ignite pull request #1349: ignite 4026

GitHub user ntikhonov opened a pull request: https://github.com/apache/ignite/pull/1349 ignite 4026 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8.0.1ea7-4026 Alternatively you can review and

Access to apacheignite-mix.readme.io

Hello, Igniters, I want to start working on the following ticket: [1]. To do so I need a write access to [2]. Can someone from community help me? [1] - https://issues.apache.org/jira/browse/IGNITE-4230 [2] - https://apacheignite-mix.readme.io Best Regards, Igor

Re: [VOTE] Apche Ignite PMC Chair Election

Denis Magda P.s. 72 hours is not enough for such votes. On Thu, Dec 15, 2016 at 3:52 AM, Rohit Mohta wrote: > Vladimir Ozerov > > > > > On Dec 14, 2016, at 11:38, Dmitriy Setrakyan > wrote: > > > > I will be closing the vote today, so please get

[GitHub] ignite pull request #1348: Ignite 1.8.2 hadoop

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1348 --- 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-4437) Make sure data structures do not use outTx call

Alexei Scherbakov created IGNITE-4437: - Summary: Make sure data structures do not use outTx call Key: IGNITE-4437 URL: https://issues.apache.org/jira/browse/IGNITE-4437 Project: Ignite

Re: API to collect list of running SQL queries

I like Vladimir idea. May be we could *compress* large strings? Or may be we could have API to ask for *string with original SQL* on any node? This *string with original SQL* only needed for special cases like *monitoring utility* and *warning on long query*. On Thu, Dec 15, 2016 at 4:11 PM,

Striped pool configuration

Folks, As I see important performance improvements were merged to the *master *branch. One of them is "striped pool" which can be used instead of current system pool. I think it's configuration is not very good at the moment: int IgniteConfiguration.setStripedPoolSize(); Problems: 1) It has

Re: API to collect list of running SQL queries

I created issue for this: https://issues.apache.org/jira/browse/IGNITE-4436 On Thu, Dec 15, 2016 at 4:11 PM, Sergi Vladykin wrote: > I think in some cases it will not affect performance much (when query > processing time is big enough), but if it is a large enough

[jira] [Created] (IGNITE-4436) SQL: create API to collect list of running SQL queries

Alexey Kuznetsov created IGNITE-4436: Summary: SQL: create API to collect list of running SQL queries Key: IGNITE-4436 URL: https://issues.apache.org/jira/browse/IGNITE-4436 Project: Ignite

[jira] [Created] (IGNITE-4435) Discovery data distribution process optimization

Sergey Chugunov created IGNITE-4435: --- Summary: Discovery data distribution process optimization Key: IGNITE-4435 URL: https://issues.apache.org/jira/browse/IGNITE-4435 Project: Ignite

Re: API to collect list of running SQL queries

I think in some cases it will not affect performance much (when query processing time is big enough), but if it is a large enough query (large string) which actually runs fast, this may affect throughput. I guess we have to measure some scenarios and evaluate the possible performance drop before

[GitHub] ignite pull request #1345: IGNITE-4277

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

Re: API to collect list of running SQL queries

Sergi, How do you think, will it affect performance significantly if we start passing original SQL between nodes? Not only this will help Alexey, but also improve user experience, because currently long-running queries are printed in transformed form, and it is pretty hard for users to understand

[jira] [Created] (IGNITE-4434) Fix label width for text mixin

Dmitriy Shabalin created IGNITE-4434: Summary: Fix label width for text mixin Key: IGNITE-4434 URL: https://issues.apache.org/jira/browse/IGNITE-4434 Project: Ignite Issue Type: Bug

Re: API to collect list of running SQL queries

List of SQL queries running where? On some exact server node? The original SQL query is not available there, we only have generated MAP part of the query. Sergi 2016-12-15 6:13 GMT+03:00 Alexey Kuznetsov : > Hi! > > Do we have API to collect list of running SQL queries? >