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.
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, 7:5
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 mos
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 that
+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 Accelerat
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, 2
or log
> I
> > > > would throw this product away.
> > > > Do we want it for Ignite?
> > > >
> > > > From SO discussion I see following error message: ": >>> Possible
> > > > starvation in striped pool."
> > > > Are yo
ssion 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 should do to prevent this error in future?
> > >
> > >
vide is better than hanging. So answer 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
, 2019, 2:46:08 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
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, Dmi
o :
> 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 г.
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.
I
Roman Shtykh created IGNITE-11620:
-
Summary: GridDhtInvalidPartitionException stops the cluster
Key: IGNITE-11620
URL: https://issues.apache.org/jira/browse/IGNITE-11620
Project: Ignite
gnite
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 Japa
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
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
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
h a change 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'
t like that thin client is 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
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 jira
Roman Shtykh created IGNITE-10854:
-
Summary: Change git URL in apply-pull-request.sh to gitbox
Key: IGNITE-10854
URL: https://issues.apache.org/jira/browse/IGNITE-10854
Project: Ignite
Issue
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:
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
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
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
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
hich I find reasonable) documented 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 &q
documented 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 f
his tests before
> keeping
> > > this
> > > > uncommented.
> > > >
> > > >
> > > >
> > > > вт, 21 авг. 2018 г. в 11:08, Maxim Muzafarov :
> > > >
> > > > > Roman,
> > > > >
> > > > > I worke
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 the
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`.
>
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
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
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
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
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
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
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 :)
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
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
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
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
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
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 wget in distribution
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
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
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
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
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
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
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
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
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
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
there?https://cwiki.apache.org/c
+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
updated as well.
We alr
Roman Shtykh created IGNITE-5706:
Summary: Redis FLUSHDB command support
Key: IGNITE-5706
URL: https://issues.apache.org/jira/browse/IGNITE-5706
Project: Ignite
Issue Type: Improvement
nd OS is what causing it?
Thanks!
--Nikita IvanovFounder & CTO
GridGain Systems
On Wed, Jul 5, 2017 at 6:15 PM, Roman Shtykh wrote:
NIkita,
While this will help improve Ignite, it will prevent its adoption by many
projects -- sending and retaining IP adresses, OS versions, etc. raise
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 Ivanov
g 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 :
>
> > Vladimir,
> > Probably
Guys,
Just an observation, but when I introduce Ignite to other developers, they get
very interested. But when the question goes to the support of the language they
use for development, often they look disappointed because a chunk of
functionalities I introduce becomes inaccessible. I think fr
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 rocketmq dependancy in the
gt;>>>
>>>>> On Jun 13, 2017, at 11:36 AM, Dmitriy Setrakyan
>>>> wrote:
>>>>>
>>>>> Denis, any chance you can post info for this webinar on the website?
>>>>>
>>>>> On Tue, Jun 13, 2017 at 10:05 AM, Deni
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 16th, 8.00 - 9.00 AM Pa
rg/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-SubmittingforReview
?
Please let me know will tips help you or not.
On Wed, Jun 7, 2017 at 8:49 AM, Roman Shtykh
wrote:
> Igniters,
> IGNITE-5229 is ready for review.Now Redis can have its default cache
> specified and used
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
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 Maxim wrote:
>
>
in
<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 wrote:
>
> I noticed the latest Apache Zeppelin integration page on readme is 1.7, but
> there are integrations for 1.8
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
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, Yakov
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. W
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 c
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
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 below
> On May 15,
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
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
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 wrote:
>
> Vladimir,
> I agree. But, if I get it right, according to your concern for
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
hould be defined on client
> level, not on the server.
>
> For now, provided that 2.0 is about to be freezed, I propose to stick to
> Dmitriy's approach and use "default" cache name instead of null. This
> should work fine for AI 2.0. We will be able to improve it in further
&g
Magda wrote:
> >
> > Roman,
> >
> > If we squeeze your contribution into 2.0 please add a documentation. You
> can handle the documentation separately as a subtask of this umbrella
> ticket:
> > https://issues.apache.org/jira/browse/IGNITE-4960
> >
> > —
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 :
> Vladimir,
> Pro
configuration, but a real cache name in Ignite settings).
Roman
On Mon, 4/24/17, Seliverstov Igor wrote:
Subject: Re: Null cache names
To: dev@ignite.apache.org, "Roman Shtykh"
Received: Monday, April 24, 2017, 10:49 PM
Roman,
Why
ca
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".
>
> What do you think?
>
> On Mon, Apr 24, 20
n("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
wrote:
Denis, Igor,
What can be done now
1. create a default cache name for Redis data, e.g. "REDIS_CA
ping in case of
> using Redis databases.
>
> Regards,
> Igor
>
> 22 апр. 2017 г. 8:47 пользователь "Roman Shtykh" >
> написал:
>
> > Hi Igor,
> > The current implementation supports only STRING data type of Redis. In
> > addition, AFAIK, scaling R
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 p
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 :
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
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?
2017-04-18 15:13 GMT+03:00 Vlad
MyBatis Ignite cache is updated. The new version is
1.0.4.http://www.mybatis.org/ignite-cache/
Best regards,Roman
On Wednesday, March 8, 2017 4:50 AM, Denis Magda wrote:
Andrey,
Excellent! Thanks for keeping an eye on this. Please let us know what you do
the same for Zeppelin.
*Raul*,
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
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
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
> On Feb 16, 2017, at 1
(https://issues.apache.org/jira/browse/IGNITE-4526). Manish Mishra.-
Rocket MQ data streamer (https://issues.apache.org/jira/browse/IGNITE-4539).
Roman Shtykh.- Hibernate 5 support
(https://issues.apache.org/jira/browse/IGNITE-1794). Mykola Pereyma.- .NET DML
(https://issues.apache.org/jira
nearest AI release (1.9 or 2.0) around February/March?
—
Denis
> On Jan 10, 2017, at 7:57 PM, Roman Shtykh wrote:
>
> Denis,
> I think our Kafka integration is the closest to what may be required for
> RockerMQ. But also I wouldn't exclude expanding to Camel's approach i
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
gt;
I do believe that the modules are not 100% identical and the reason it’s done
this way might be because the modules use different Camel or Ignite interfaces
and concepts. Is this approach somehow related to RocketMQ and Ignite?
—
Denis
> On Jan 9, 2017, at 11:06 PM, Roman Shtykh wrote:
&
Igniters,
Recently I am looking into a new pub/sub messaging Apache incubator project
called RocketMQ [1], originally developed at Alibaba. And I am thinking about
implementing a streamer for Ignite.
Do you think it has to be placed under modules/ of Ignite project, or better to
have it together
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
d with this
On Dec 29, 2016, at 2:38 PM, Sally Khudairi 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
appreciated!
Roman have never been a release manager yet. However, this i
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
wrote:
Denis,
Sure, I will update MyBatis.
-Roman
On Wednesday
1 - 100 of 174 matches
Mail list logo
