Re: New Сommitter: Maxim Muzafarov

Maxim, congratulations! -- Roman On Thursday, August 29, 2019, 12:11:29 a.m. GMT+9, Dmitriy Pavlov wrote: Dear community, The Project Management Committee (PMC) for Apache Ignite has invited Maxim Muzafarov to become a committer and we are pleased to announce that he has accepted.

Re: Coding guidelines. Useless JavaDoc comments.

Although I agree we have some meaningless comments, making them optional can result at having no comments.Therefore I'd follow Nikolay's suggestion to have comments (perhaps with some exclusions for loggers, etc.) and make it optional for tests. -- Roman On Wednesday, August 7, 2019,

Re: New Ignite PMC Member: Ilya Kasnacheev

Ilya, congratulations! -- Roman On Wednesday, August 7, 2019, 4:58:36 a.m. GMT+9, Denis Magda wrote: The Project Management Committee (PMC) for Apache Ignite has invited Ilya Kasnacheev to become a committer and we are pleased to announce that he has accepted. Ilya is one of the

Re: [DISCUSSION] Ignite 3.0 and to be removed list

Probably it makes sense to have a survey on users mailing list to have some idea what is being used before deciding what to bury, support in a separate repository or master branch. -- Roman On Thursday, June 20, 2019, 10:26:37 p.m. GMT+9, Ilya Kasnacheev wrote: Hello! I think

Re: [VOTE] Complete Discontinuation of IGFS and Hadoop Accelerator

+1 On Thursday, June 20, 2019, 7:34:47 a.m. GMT+9, Andrey Gura wrote: +1 On Thu, Jun 20, 2019 at 12:58 AM Denis Magda wrote: > > Igniters, > > Based on our earlier discussion [1], let's formalize our decision and vote > for the following: > >    - IGFS and In-Memory Hadoop

Re: Ignite 2.7.5 Release scope

Dmitriy, the probability of having nodes down with these bugs under heavy load conditions is pretty high. Good candidate for cherry-picking. [1] https://issues.apache.org/jira/browse/IGNITE-9803[2] https://issues.apache.org/jira/browse/IGNITE-11127 -- Roman On Wednesday, March 27, 2019,

Re: GridDhtInvalidPartitionException takes the cluster down

for Ignite? > > > > > > > > From SO discussion I see following error message: ": >>> Possible > > > > starvation in striped pool." > > > > Are you sure this message are clear for Ignite user(not Ignite > hacker)? > > > > What user shou

Re: GridDhtInvalidPartitionException takes the cluster down

> > Are you sure this message are clear for Ignite user(not Ignite hacker)? > > > What user should do to prevent this error in future? > > > > > > В Вт, 26/03/2019 в 10:10 +0300, Andrey Kuznetsov пишет: > > > > By default, SYSTEM_WORKER_BLOCKED failu

Re: GridDhtInvalidPartitionException takes the cluster down

wer is NO. We mustn't disable failure handlers. On Mon, Mar 25, 2019 at 2:47 PM Roman Shtykh wrote: > > If it sticks to the behavior we had before introducing failure handler, I > think it's better to have disabled instead of killing the whole cluster, as > in my case, and create

Re: Ignite 2.7.5 Release scope

p.m. GMT+9, Andrey Kuznetsov wrote: Roman, I think the worst thing we can do is to hide the bug you discovered. The sane options are either fix it urgently or classify it as non-critical and postpone. вт, 26 мар. 2019 г. в 05:13, Roman Shtykh : Guys, what do you think about disabling

Re: Ignite 2.7.5 Release scope

Guys, what do you think about disabling SYSTEM_WORKER_TERMINATION (introduced with IEP-14) before "cluster shutdown" bugs are fixed, as suggested by Nikolay I. in "GridDhtInvalidPartitionException takes the cluster down" thread? -- Roman On Tuesday, March 26, 2019, 3:41:29 a.m. GMT+9,

Re: GridDhtInvalidPartitionException takes the cluster down

> Hi Roman, > > I think this InvalidPartition case can be simply handled > in GridCacheTtlManager.expire method. > For workaround a custom FailureHandler can be configured that will not stop > a node in case of such exception is thrown. > > пн, 25 мар. 2019 г. в 08

GridDhtInvalidPartitionException takes the cluster down

Igniters, Restarting a node when injecting data and having it expired, results at GridDhtInvalidPartitionException which terminates nodes with SYSTEM_WORKER_TERMINATION one by one taking the whole cluster down. This is really bad and I didn't find the way to save the cluster from disappearing.

[jira] [Created] (IGNITE-11620) GridDhtInvalidPartitionException stops the cluster

Roman Shtykh created IGNITE-11620: - Summary: GridDhtInvalidPartitionException stops the cluster Key: IGNITE-11620 URL: https://issues.apache.org/jira/browse/IGNITE-11620 Project: Ignite

Re: New PMC Member: Roman Shtykh

has invited Roman Shtykh to become a PMC member and we are pleased to announce that he has accepted. Being a PMC member enables assistance with the management and to guide the direction of the project. Roman is one of the community veterans who is presently popularizing Ignite in Japan

Re: Help Wanted: Java 11 support for Camel & Cassandra integrations

Dmitriy, I will have a look at the Camel Streamer. -- Roman On Tuesday, February 19, 2019, 2:26:26 a.m. GMT+9, Dmitriy Pavlov wrote: Hi Igniters, I've noticed we have a couple more Java11 related failures: Tests here didn't start at all, so assistance here for finding out - reasons

[jira] [Created] (IGNITE-11070) Update RocketMQ dependency to 4.4.0

Roman Shtykh created IGNITE-11070: - Summary: Update RocketMQ dependency to 4.4.0 Key: IGNITE-11070 URL: https://issues.apache.org/jira/browse/IGNITE-11070 Project: Ignite Issue Type: Task

Re: CompactFooter for ClientBinaryMarshaller

Igor, I see. How about having a warning if `BinaryConfiguration` is not provided explicitly to at least raise attention? And creating a JIRA issue for C++ clients -- after it resolves we can probably switch it to cluster default. -- Roman Shtykh On Monday, January 21, 2019, 7:04:30 p.m

Re: CompactFooter for ClientBinaryMarshaller

hange should be done in minor release, maybe in 3.0 Vova, what do you think? It was you, who designed and developed compact footer, right? Best Regards,Igor On Fri, Jan 18, 2019 at 4:20 AM Roman Shtykh wrote: > I believe it has something to do with backward compatibility.That's what I

Re: CompactFooter for ClientBinaryMarshaller

s silently returns null. It should be fixed. For the compact footer being set to false by default - I believe it has something to do withbackward compatibility. Best Regards,Igor On Thu, Jan 17, 2019 at 7:37 AM Roman Shtykh wrote: Igniters, After putting some data with a user-defined key with a

CompactFooter for ClientBinaryMarshaller

Igniters, After putting some data with a user-defined key with a thick client, it's impossible to retrieve it with a thin client.https://issues.apache.org/jira/browse/IGNITE-10960(I was not sure it was a bug, so I first reported the issue to the user ml, Mikhail thanks for checking and the

Re: [RESULT] [VOTE] Apache Ignite 2.7.0 Release (RC2)

Nikolay, Do you know when npm (and other thin client) package will be uploaded? - $ npm i apache-ignite-client --save - npm ERR! code E404 - npm ERR! 404 Not Found: apache-ignite-client@lates -- Roman On Thursday, December 6, 2018, 7:20:33 a.m. GMT+9, Prachi Garg wrote:

[jira] [Created] (IGNITE-10265) PDOStatement::rowCount returns 0

Roman Shtykh created IGNITE-10265: - Summary: PDOStatement::rowCount returns 0 Key: IGNITE-10265 URL: https://issues.apache.org/jira/browse/IGNITE-10265 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-10017) Infinite loop with 3rd party persistency, keepBinary and no value for the key

Roman Shtykh created IGNITE-10017: - Summary: Infinite loop with 3rd party persistency, keepBinary and no value for the key Key: IGNITE-10017 URL: https://issues.apache.org/jira/browse/IGNITE-10017

[jira] [Created] (IGNITE-9897) PDO returns null for column values of string type

Roman Shtykh created IGNITE-9897: Summary: PDO returns null for column values of string type Key: IGNITE-9897 URL: https://issues.apache.org/jira/browse/IGNITE-9897 Project: Ignite Issue

[jira] [Created] (IGNITE-9700) Remove configurable values from mesos pom.xml

Roman Shtykh created IGNITE-9700: Summary: Remove configurable values from mesos pom.xml Key: IGNITE-9700 URL: https://issues.apache.org/jira/browse/IGNITE-9700 Project: Ignite Issue Type

Re: mesos IgniteProvider improvement

ed on our site -- I don't see how it blocks anything. Roman Shtykh On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya Kasnacheev wrote: Hello! There's still two issues with the submission. The first one is that we're downloading "latest" version from preferred mirror bu

Re: Apache Ignite 2.7 release

ite -- I don't see how it blocks anything. Roman Shtykh On Monday, September 10, 2018, 6:16:15 p.m. GMT+9, Ilya Kasnacheev wrote: Hello! There's still two issues with the submission. The first one is that we're downloading "latest" version from preferred mirror but a specifi

Re: Unknown known issue on cache rebalancing delayed

: > > > > > Roman, Anton, > > > > > > I've already created additional PR [2] all and run it on TC [1]. > > > Please, follow up with the results. > > > > > > [1] > > > > > > > > > https://ci.ignite.apache.org/viewType.htm

Re: Apache Ignite 2.7 release

Thanks, Ilya!I will check your comments, and discuss it at JIRA. -- Roman Shtykh On Tuesday, September 4, 2018, 7:17:53 p.m. GMT+9, Ilya Kasnacheev wrote: Hello! IGNITE-9408 looks good to me and may be merged right away. IGNITE-9388 needs more work in my opinion, I have commented

Re: Unknown known issue on cache rebalancing delayed

s and haven't found any problems > with delayed cache rebalacne. > Agree with you - let's uncomment this and remove scary comment. Will you > create a ticket for it? > > In case of any problems we can easily detec deadlock with newly configured > `FailureHandler`. > > On Tu

Re: Apache Ignite 2.7 release

Igniters, I would like Mesos integration update be included in the upcoming release.Can anyone review prs for the following issues? IGNITE-9388: mesos IgniteProvider tries to access obsolete ignite.run or download from slow archiveIGNITE-9408: Update mesos version Roman Shtykh On Thursday

[jira] [Created] (IGNITE-9409) yarn IgniteProvider uses an obsolete URL for a version check

Roman Shtykh created IGNITE-9409: Summary: yarn IgniteProvider uses an obsolete URL for a version check Key: IGNITE-9409 URL: https://issues.apache.org/jira/browse/IGNITE-9409 Project: Ignite

[jira] [Created] (IGNITE-9408) Update mesos version

Roman Shtykh created IGNITE-9408: Summary: Update mesos version Key: IGNITE-9408 URL: https://issues.apache.org/jira/browse/IGNITE-9408 Project: Ignite Issue Type: Task Reporter

[jira] [Created] (IGNITE-9388) IgniteProvider tries to access obolete ignite.run or download from slow archive

Roman Shtykh created IGNITE-9388: Summary: IgniteProvider tries to access obolete ignite.run or download from slow archive Key: IGNITE-9388 URL: https://issues.apache.org/jira/browse/IGNITE-9388

[jira] [Created] (IGNITE-9382) Node.js fails to process large payloads

Roman Shtykh created IGNITE-9382: Summary: Node.js fails to process large payloads Key: IGNITE-9382 URL: https://issues.apache.org/jira/browse/IGNITE-9382 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-9353) Remove "Known issue, possible deadlock in case of low priority cache rebalancing delayed" comment from GridCacheRebalancingSyncSelfTest#getConfiguration

Roman Shtykh created IGNITE-9353: Summary: Remove "Known issue, possible deadlock in case of low priority cache rebalancing delayed" comment from GridCacheRebalancingSyncSelfTest#getConfiguration Key: I

Re: Unknown known issue on cache rebalancing delayed

Hi Maxim, I have some issues with a cluster with rebalance delay enabled, but need to check more -- if I find it's related I'll share.Just wanted to make sure it's not an issue anymore from someone working on rebalancing. We should remove that comment then, it looks scary :) -- Roman Shtykh

Unknown known issue on cache rebalancing delayed

Igniters, I have found "Known issue, possible deadlock in case of low priority cache rebalancing delayed" comment in GridCacheRebalancingSyncSelfTest#getConfiguration.Can you please explain when using rebalance delay can be an issue and why? -- Roman

[jira] [Created] (IGNITE-9253) Rename activation/deactivation commands for REST API

Roman Shtykh created IGNITE-9253: Summary: Rename activation/deactivation commands for REST API Key: IGNITE-9253 URL: https://issues.apache.org/jira/browse/IGNITE-9253 Project: Ignite Issue

[jira] [Created] (IGNITE-9252) Update RocketMQ dependencies to 4.3.0

Roman Shtykh created IGNITE-9252: Summary: Update RocketMQ dependencies to 4.3.0 Key: IGNITE-9252 URL: https://issues.apache.org/jira/browse/IGNITE-9252 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-9037) Apache Pulsar intergration

Roman Shtykh created IGNITE-9037: Summary: Apache Pulsar intergration Key: IGNITE-9037 URL: https://issues.apache.org/jira/browse/IGNITE-9037 Project: Ignite Issue Type: New Feature

[jira] [Created] (IGNITE-8525) Support for IgniteZeroMqStreamer non-multi-part pub-sub

Roman Shtykh created IGNITE-8525: Summary: Support for IgniteZeroMqStreamer non-multi-part pub-sub Key: IGNITE-8525 URL: https://issues.apache.org/jira/browse/IGNITE-8525 Project: Ignite

Re: Docker deployment with EXTERNAL_LIBS environment variable

I had the same problem (pretty common not having -i option) and fixed it. Need a review.https://issues.apache.org/jira/browse/IGNITE-8143 -- Roman On Tuesday, April 17, 2018, 7:15:25 p.m. GMT+9, Petr Ivanov wrote: Hi, Kseniya. I guess that something wrong with

[jira] [Created] (IGNITE-8143) Feching EXTERNAL_LIBS for docker container fails

Roman Shtykh created IGNITE-8143: Summary: Feching EXTERNAL_LIBS for docker container fails Key: IGNITE-8143 URL: https://issues.apache.org/jira/browse/IGNITE-8143 Project: Ignite Issue Type

[jira] [Created] (IGNITE-8052) Clear error message when using a non-existing column name for CREATE TABLE primary key

Roman Shtykh created IGNITE-8052: Summary: Clear error message when using a non-existing column name for CREATE TABLE primary key Key: IGNITE-8052 URL: https://issues.apache.org/jira/browse/IGNITE-8052

[jira] [Created] (IGNITE-7622) SQL: Subquery fails in non-collocated mode

Roman Shtykh created IGNITE-7622: Summary: SQL: Subquery fails in non-collocated mode Key: IGNITE-7622 URL: https://issues.apache.org/jira/browse/IGNITE-7622 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-7598) SQL: INSERT requires you to specify the column names even if you are adding values for all the columns of the table

Roman Shtykh created IGNITE-7598: Summary: SQL: INSERT requires you to specify the column names even if you are adding values for all the columns of the table Key: IGNITE-7598 URL: https://issues.apache.org/jira

[jira] [Created] (IGNITE-7323) Up

Roman Shtykh created IGNITE-7323: Summary: Up Key: IGNITE-7323 URL: https://issues.apache.org/jira/browse/IGNITE-7323 Project: Ignite Issue Type: Bug Reporter: Roman Shtykh

[jira] [Created] (IGNITE-7296) Update RocketMQ to 4.2.0

Roman Shtykh created IGNITE-7296: Summary: Update RocketMQ to 4.2.0 Key: IGNITE-7296 URL: https://issues.apache.org/jira/browse/IGNITE-7296 Project: Ignite Issue Type: Task

[Announcement] Talk: Real-time Data Analysis with Apache Ignite High-Performance In-memory Platform

Hi, I will be making a short presentation at Data Platform Conference Tokyo 2017 on Apache Ignite with emphasis on IoT. Attending is free. Please come if you are in Tokyo. https://ignite.apache.org/events.html#dataplatform-jp Best regards,Roman

[jira] [Created] (IGNITE-6042) Update KafkaStreamer dependencies to Kafka 0.11.x

Roman Shtykh created IGNITE-6042: Summary: Update KafkaStreamer dependencies to Kafka 0.11.x Key: IGNITE-6042 URL: https://issues.apache.org/jira/browse/IGNITE-6042 Project: Ignite Issue

[jira] [Created] (IGNITE-5912) [Redis] EXPIRE/PEXPIRE on keys

Roman Shtykh created IGNITE-5912: Summary: [Redis] EXPIRE/PEXPIRE on keys Key: IGNITE-5912 URL: https://issues.apache.org/jira/browse/IGNITE-5912 Project: Ignite Issue Type: New Feature

Re: Zeppelin, MyBatis and Vert.x update to AI 2.1

Denis, I updated MyBatis integration, and will release it this week. -- Roman On Tuesday, August 1, 2017 5:23 AM, Denis Magda wrote: Andrey, Roman, As maintainers of the projects in the subject, could you please go ahead and update Ignite version to 2.1

Re: [VOTE] Apache Ignite 2.1.0 RC4

+1 (non-binding) -- Roman On Monday, July 24, 2017 10:32 PM, Anton Vinogradov wrote: Igniters, This vote based on same files as RC3. Only one change is that I signed zips with my signature. KEYS files (https://dist.apache.org/repos/dist/release/ignite/KEYS) was

Re: usage analytics

NIkita, While this will help improve Ignite, it will prevent its adoption by many projects -- sending and retaining IP adresses, OS versions, etc. raises tons of questions when considering to use Ignite. Even if it can be opted out. -- Roman On Thursday, July 6, 2017 5:38 AM, Nikita

Re: Null cache names

; > An alternative (an the best way, I think) is introducing a configuration > property to define which cache to use in case it hasn't be defined in a > message. > > I'll appreciate any thoughts on that. > > Regards, > Igor > > 2017-04-24 12:43 GMT+03:00 Roman Shtykh <rsht

Re: Fwd: [ANNOUNCE] Release Apache RocketMQ 4.1.0 (incubating)

Denis, AFAIK, the new version is compatible with the previous one, but I will check it, and if it can be easily done, I will update the dependency today. -- Roman On Sunday, June 18, 2017 10:51 AM, Denis Magda wrote: Roman,  Do you think we need to update the

Re: [DISCUSS] Webinar for Ignite Persistent Store walk-through

;>> currently in the community  may join as well. >>> >>> >>>> — >>>> Denis >>>> >>>>> On Jun 13, 2017, at 11:36 AM, Dmitriy Setrakyan <dsetrak...@apache.org> >>>> wrote: >>>>> >>&g

Re: [DISCUSS] Webinar for Ignite Persistent Store walk-through

Denis, Can you please share slides (or video) after the webinar? I would like to attend it but it's midnight in Japan. -- Roman On Tuesday, June 13, 2017 7:56 AM, Denis Magda wrote: Good, we have a quorum then ;) I plan to schedule webinar for this Friday, June

IGNITE-5229 is ready for review

Igniters, IGNITE-5229 is ready for review.Now Redis can have its default cache specified and used as a template when switching to other caches, as discussed earlier in this ml (please see the JIRA issue). [1] https://issues.apache.org/jira/browse/IGNITE-5229 -- Roman

Re: IGNITE-532 ready for review

Denis, Lately I don't use Scala. Probably someone with more Scala experience will be a better reviewer. Roman On Wednesday, May 24, 2017 1:03 AM, Denis Magda wrote: Roman, Would you mind reviewing the contribution? — Denis > On May 23, 2017, at 8:38 AM, Kozlov

Re: Apache Zeppelin page on readme

o/docs/apache-zeppelin <https://apacheignite-tools.readme.io/docs/apache-zeppelin> Where did you find the old reference? — Denis > On May 22, 2017, at 11:40 PM, Roman Shtykh <rsht...@yahoo.com.INVALID> wrote: > > I noticed the latest Apache Zeppelin integr

Apache Zeppelin page on readme

I noticed the latest Apache Zeppelin integration page on readme is 1.7, but there are integrations for 1.8 and 1.9 too. Missing update? https://apacheignite-mix.readme.io/v1.7/docs/apache-zeppelin -- Roman

Re: Changing cache name when using Redis protocol

Yakov, Thank you for the pointers! Let's implement it with SELECT then, with 'redis-ignite-internal-cache-0' as a default one. Sorry, I was wrong about the number of databases, just remembered there was a limit. I should have had to recheck. -- Roman On Friday, May 19, 2017 6:29 PM,

Re: Changing cache name when using Redis protocol

Yakov, Thanks for sharing your thoughts! I agree that both configuration and CONFIG SET lack flexibility. Let’s forget about these approaches. For specifying cache per connection, CLIENT SETNAME [cache_name] [1] can be another option. It can be done with config templates as you proposed too.

Changing cache name when using Redis protocol

Igniters, Getting back to the discussion on how to switch between caches when using Redis (and potentially memcached).# Please note, that this is a problem only with a part of Redis data stuctures such as currently implemented STRING. For sets and hash tables, set/hash name can be treated as a

[jira] [Created] (IGNITE-5241) Redis hash table support

Roman Shtykh created IGNITE-5241: Summary: Redis hash table support Key: IGNITE-5241 URL: https://issues.apache.org/jira/browse/IGNITE-5241 Project: Ignite Issue Type: New Feature

Re: Store data from Python in multiple caches using Redis or Memcached client in Apache ignite

Denis, yes, I would like to enable switching caches via "CONFIG SET parameter value".I created https://issues.apache.org/jira/browse/IGNITE-5229 for this, and will discuss it in a separate thread. Roman On Tuesday, May 16, 2017 8:45 AM, Denis Magda wrote: Hi, see

[jira] [Created] (IGNITE-5229) Specify caches when using Redis protocol

Roman Shtykh created IGNITE-5229: Summary: Specify caches when using Redis protocol Key: IGNITE-5229 URL: https://issues.apache.org/jira/browse/IGNITE-5229 Project: Ignite Issue Type

[jira] [Created] (IGNITE-5091) Document RocketMQ streamer

Roman Shtykh created IGNITE-5091: Summary: Document RocketMQ streamer Key: IGNITE-5091 URL: https://issues.apache.org/jira/browse/IGNITE-5091 Project: Ignite Issue Type: Sub-task

Re: Null cache names

Don’t see any reason why we keep discussing this if the whole story is about a “one line” fix. Roman, could you implement your suggestion and do a pull-request? — Denis > On Apr 25, 2017, at 6:53 PM, Roman Shtykh <rsht...@yahoo.com.INVALID> wrote: > > Vladimir, > I agree.

[jira] [Created] (IGNITE-5083) Add default cache for Redis

Roman Shtykh created IGNITE-5083: Summary: Add default cache for Redis Key: IGNITE-5083 URL: https://issues.apache.org/jira/browse/IGNITE-5083 Project: Ignite Issue Type: Task

Re: Apache Ignite 2.0 Release

https://issues.apache.org/jira/browse/IGNITE-4960 > > > > — > > Denis > > > >> On Apr 19, 2017, at 7:03 AM, Roman Shtykh <rsht...@yahoo.com.INVALID> > wrote: > >> > >> Alexey, > >> Sorry, I forgot to update dependencies. Now

Re: Null cache names

essage part becomes mandatory. An alternative (an the best way, I think) is introducing a configuration property to define which cache to use in case it hasn't be defined in a message. I'll appreciate any thoughts on that. Regards, Igor 2017-04-24 12:43 GMT+03:00 Roman Shtykh <rsht...@yahoo.co

Re: Null cache names

configuration, but a real cache name in Ignite settings). Roman On Mon, 4/24/17, Seliverstov Igor <gvvinbl...@gmail.com> wrote: Subject: Re: Null cache names To: dev@ignite.apache.org, "Roman Shtykh" <rsht...@yahoo.com> Received:

Re: Null cache names

Just as idea, how about in case of user does not configured "REDIS_CACHE" >  then create it via ignite.getOrCreateCache(new > CacheConfiguration("REDIS_CACHE")) > and prin warning to log "REDIS_CACHE not configured, using default > partitioned cache". > &

Re: Null cache names

che(new CacheConfiguration("REDIS_CACHE"))and prin warning to log "REDIS_CACHE not configured, using default partitioned cache". What do you think? On Mon, Apr 24, 2017 at 10:26 AM, Roman Shtykh <rsht...@yahoo.com.invalid> wrote: Denis, Igor, What can be done no

Re: Null cache names

operty to define which cache to use or mapping in case of > using Redis databases. > > Regards, > Igor > > 22 апр. 2017 г. 8:47 пользователь "Roman Shtykh" <rsht...@yahoo.com.invalid > > > написал: > > > Hi Igor, > > The current implementation s

Re: Null cache names

Hi Igor, The current implementation supports only STRING data type of Redis. In addition, AFAIK, scaling Redis per dataset is normally done via running separate instances of Redis for each dataset. Therefore my choice was storing to the default cache. It looks fine from Redis' perspective, but

Re: Apache Ignite 2.0 Release

quires a local copy of rocketmq. If I revert it back to 4.0.0-incubating, then the test does not compile for me. 2017-04-19 11:55 GMT+03:00 Roman Shtykh <rsht...@yahoo.com.invalid>: Hi Alexey, Fixed now. Thanks for checking! Roman     On Tuesday, April 18, 2017 10:17 PM, Alexey Goncharuk &l

Re: Apache Ignite 2.0 Release

Hi Alexey, Fixed now. Thanks for checking! Roman On Tuesday, April 18, 2017 10:17 PM, Alexey Goncharuk wrote: Hi Roman, I tried to run tests for RocketMQ streamer, but they failed for me (I've added a comment in the ticket). Can you please take a look?

[jira] [Created] (IGNITE-4737) Update Apache Flink dependencies to the latest version

Roman Shtykh created IGNITE-4737: Summary: Update Apache Flink dependencies to the latest version Key: IGNITE-4737 URL: https://issues.apache.org/jira/browse/IGNITE-4737 Project: Ignite

[jira] [Created] (IGNITE-4721) Javadocs build fails with Java 8 update 121

Roman Shtykh created IGNITE-4721: Summary: Javadocs build fails with Java 8 update 121 Key: IGNITE-4721 URL: https://issues.apache.org/jira/browse/IGNITE-4721 Project: Ignite Issue Type: Bug

Re: Implement IgniteZeromqStreamer to stream data from ZeroMQ

Sure, I will have a look in a couple of days.Maxim, thank you for the PR! Roman On Friday, February 17, 2017 12:39 AM, Denis Magda wrote: Roman, As the most experienced committer of the streaming components, could you do the review of Maxim’s changes? — Denis >

Re: Integration with RocketMQ

elease this feature in the nearest AI release (1.9 or 2.0) around February/March? — Denis > On Jan 10, 2017, at 7:57 PM, Roman Shtykh <rsht...@yahoo.com.INVALID> wrote: > > Denis, > I think our Kafka integration is the closest to what may be required for > RockerMQ. But also I

[jira] [Created] (IGNITE-4539) RocketMQ data streamer

Roman Shtykh created IGNITE-4539: Summary: RocketMQ data streamer Key: IGNITE-4539 URL: https://issues.apache.org/jira/browse/IGNITE-4539 Project: Ignite Issue Type: New Feature

[jira] [Created] (IGNITE-4528) Redis INCR values are not picked up by MGET and DBSIZE

Roman Shtykh created IGNITE-4528: Summary: Redis INCR values are not picked up by MGET and DBSIZE Key: IGNITE-4528 URL: https://issues.apache.org/jira/browse/IGNITE-4528 Project: Ignite

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

wrote:  Sally, looks like you got confused with this On Dec 29, 2016, at 2:38 PM, Sally Khudairi <s...@apache.org> wrote: And thanks in advance, Roman Shtykh, for acting as project spokesperson in your role as release manager. Participation from the community at-large is greatly appreci

Re: Update ignite version for Camel, Zeppelin, Vert.x and MyBatis

MyBatis integration is in maven repository now.Btw, the links at [1] are old (pointing to apacheignite.readme.io instead of apacheignite-mix.readme.io). Roman On Wednesday, December 14, 2016 11:04 AM, Roman Shtykh <rsht...@yahoo.com.INVALID> wrote: Denis, Sure, I will update M

Re: Update ignite version for Camel, Zeppelin, Vert.x and MyBatis

Denis, Sure, I will update MyBatis. -Roman On Wednesday, December 14, 2016 5:42 AM, Denis Magda wrote: Raul K., Andrey G., Roman S., Would you mind updating pom files of the external projects [1] Ignite is integrated with by setting its version to 1.8.0?

Re: Major release 2.0 and compilation

Rohit, I don't think this is a very clean approach to maintain multiple copies. +1 for removing deprecated stuff in 2.0 with some exclusions and thoroughly documenting and sharing the changes as it was proposed above. -Roman On Thursday, December 8, 2016 10:47 AM, Rohit Mohta

Re: [VOTE] Apache Ignite 1.8.0 RC1

+1 (binding) -Roman On Tuesday, December 6, 2016 8:14 AM, Denis Magda wrote: +1 (binding) — Denis > On Dec 5, 2016, at 7:22 AM, Vladimir Ozerov wrote: > > Hello, > > We have uploaded the 1.8.0 release candidate to >

Re: Dedicated readme.io documentation for Ignite integrations

Denis, Can you please set permissions for me to edit https://apacheignite-mix.readme.io/docs? -Roman On Thursday, December 1, 2016 4:38 PM, Dmitriy Setrakyan wrote: On Thu, Dec 1, 2016 at 10:28 AM, Denis Magda wrote: > I don't say we need it but

Re: Apache Ignite 1.8 Release

lt;alexander.a.pasche...@gmail.com>: > > > > > >> > > >> Vlad, > > > > > >> > > >> > > > > > >> > > >> Most likely today. > > > > > >> > > >> > > > > > >

Re: IGNITE-3066 Set of Redis commands that can be easily implemented via existing REST commands

h the design and implementation. — Denis > On Nov 19, 2016, at 5:02 AM, Roman Shtykh <rsht...@yahoo.com.INVALID> wrote: > > Alexey, > > I also think this is the way to go. Thank you. Any other opinions? > > Roman > > > > On Saturday, November 19, 2016

Re: IGNITE-3066 Set of Redis commands that can be easily implemented via existing REST commands

Alexey, I also think this is the way to go. Thank you. Any other opinions? Roman On Saturday, November 19, 2016 8:21 PM, Alexey Kuznetsov wrote: Roman, I think we should better implement REDIS processor (if needed) and use Ignite API directly. In this case we will

Re: IGNITE-3066 Set of Redis commands that can be easily implemented via existing REST commands

wrote: Hi Roman, Do you mean that key expiration is not supported in Ignite? If so, then this is not true, see the last example here: https://apacheignite.readme.io/docs/expiry-policies -Val On Fri, Nov 18, 2016 at 7:55 PM, Roman Shtykh <rsht...@yahoo.com.invalid> wrote: > Dmitriy, >

Re: IGNITE-3066 Set of Redis commands that can be easily implemented via existing REST commands

Nov 18, 2016 at 4:23 AM, Roman Shtykh <rsht...@yahoo.com.invalid> wrote: Dmitriy, I have contents prepared for the Redis category page on  https://issues.apache.org/ jira/browse/IGNITE-4233Later I will add examples for Java and some other languages. -Roman     On Thursday, November 17,

Re: IGNITE-3066 Set of Redis commands that can be easily implemented via existing REST commands

/IGNITE-4244  ? -Roman  On Wednesday, November 16, 2016 8:09 PM, Andrey Novikov <anovi...@apache.org> wrote: Roman, I reviewed your PR. Changed it a little and merged to master. Thanks for your contribution! On Wed, Nov 16, 2016 at 9:39 AM, Roman Shtykh <rsht...@yahoo.com.inval

  1   2   >