Igniters,
While investigating this issue reported by user, I noticed that LOCAL cache
is fully destroyed when close() is called, which is inconsistent with other
cache modes. Is there any reason for this?
-Val
-- Forwarded message --
From: vkulichenko
Folks,
I made several enhancements in our direct marshalling protocol that will
reduce the amount of data transferred over the network. There are two main
changes:
- Optimized encoding of integers and longs. Now small numbers (0-127)
consume only one byte instead of four, greater number
Hi,
I'm against optional checksum verification. It's not safe, adds one more
configuration property and I don't see any use case that can require this.
I also don't completely understand what you're trying to achieve. Can you
please describe the sequence of serialization/deserialization events
+1
On Thu, Nov 5, 2015 at 9:50 AM, Dmitriy Setrakyan
wrote:
> Sounds good to me.
>
> On Thu, Nov 5, 2015 at 6:27 AM, Yakov Zhdanov wrote:
>
> > Agree with Pavel.
> >
> > --Yakov
> >
> > 2015-11-05 16:48 GMT+03:00 Pavel Tupitsyn
1/spring-framework-reference/htmlsingle/#cache-annotations-put
> >
> > We support all these?
> >
> > D.
> >
> > On Thu, Nov 5, 2015 at 8:00 AM, Andrey Gura <ag...@gridgain.com> wrote:
> >
> > > Oops, I didn't noticed.
> > >
> &g
Igniters,
I just tried to switch from multicast to VM IP finder in example-ignite.xml
and nodes stopped joining each other. If I start two servers, they both
start with order=1; if I start a server and then a client, the client never
joins.
Can someone else try to do this and see if it's
No, these are different Spring projects.
Actually it looks like Boot is just a tool for faster bootstrap of
Spring-enabled projects (I looked through the docs really briefly, so can
miss something). Dmitry, what kind of integration do you have in mind?
-Val
On Wednesday, November 4, 2015,
Andrey, we already have this. See SpringCacheManager class.
-Val
On Thursday, November 5, 2015, Andrey Gura wrote:
> Hi,
>
> @Cacheable is not Spring Boot annotation. It's part of spring-context
> module.
>
> If client want use @Cacheable annotation in Spring based project
Artem,
I merged the ticket [1] where you fixed URI deployment JavaDoc and one of
the tests started to fail after that [2]. I think something is just missing
on test classpath, can you please take a look?
[1] https://issues.apache.org/jira/browse/IGNITE-1559
[2]
+1 for 'instanceName'. 'nodeName' looks confusing as well - I would think
that it should be unique among all nodes.
-Val
On Wed, Aug 26, 2015 at 2:25 AM, Raul Kripalani r...@evosent.com wrote:
Agree. The term grid to refer to a single node is very confusing.
On 19 Aug 2015 08:58, Semyon
Hi Ken,
I was just in process of reviewing them :) Please give me couple more hours
and I will provide feedback.
-Val
On Mon, Aug 31, 2015 at 6:47 PM, Ken Cheng <kcheng@gmail.com> wrote:
> Hi Valentin Kulichenko* & *Alexey Kuznetsov
>
> Can you help to do the code re
gt; it took a long time to respond to your previous email).
>
> 2015-08-31 18:48 GMT-07:00 Valentin Kulichenko <
> valentin.kuliche...@gmail.com>:
>
> > Hi Ken,
> >
> > I was just in process of reviewing them :) Please give me couple more
> hours
> > and I w
Igniters,
Are portable objects already migrated and will be released as a part of 1.4
(I see that APIs and configuration changes are already in master)? I just
thought it's a pretty big change and we were going to include it only in
1.5, correct me if I'm wrong.
-Val
Sergi,
Can you please take a look at this issue? I create a ticket and attached
the test to it: https://issues.apache.org/jira/browse/IGNITE-1552
I already made some debugging and I think the reason is that TableFunction
is parsed as an ordinary Function, so it's columnList field is ignored. As
Folks,
Based on user's feedback about beta of 1.5, I created several tickets for
binary marshaller that should be fixed in the final version. Here is the
list:
- https://issues.apache.org/jira/browse/IGNITE-2098
- https://issues.apache.org/jira/browse/IGNITE-2099
-
Igniters,
I noticed that when I execute cache.invoke() in transactional cache, it's
invoked twice for the same old value on the primary node. First invocation
is done on prepare step [1], the second one happens on commit [2]. Is this
expected behavior? Why can't we reuse already calculated new
Igniters,
Can someone please explain the purpose
of GridCacheIoManager.processFailedMessage() method? I've already seen
several reports on user@ about "Unsupported direct type" exception thrown
from this method and each time we just add processing for one more message.
In my opinion this
se
> Ignite
> > > > needs to calculate a return value for the first invoke() and then it
> > > should
> > > > be called second time during commit when transactional locks are
> held.
> > >
> > >
> > > Current requirement is that a
Folks,
I just noticed that NearCacheConfiguration class extends JCache's
MutableConfiguration. This means that it inherits properties like
writeThrough, readThrough, etc., which doesn't look right to me.
Was it done on purpose? Does anyone know the reason?
-Val
xey G., would be nice to hear your thoughts here.
>
> D.
>
> On Wed, Dec 2, 2015 at 9:08 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Igniters,
> >
> > I noticed that when I execute cache.invoke() in transactional cache, it's
>
ll be locked by first started
> > > process and other will failed.
> > >
> > > I think we should go as I mentioned above.
> > >
> > >
> > > On Wed, Dec 16, 2015 at 7:23 AM, Dmitriy Setrakyan <
> > dsetrak...@apache.org&
r suggestion to it.
>
> --Yakov
>
> 2015-12-14 11:47 GMT+03:00 Valentin Kulichenko <
> valentin.kuliche...@gmail.com>:
>
> > Denis,
> >
> > Yes, this can be a workaround, but at the same time it makes things even
> > more confusing :) This means that client
Dmitry,
How do you think, should we just change the behavior or make it
configurable?
-Val
On Fri, Dec 11, 2015 at 1:59 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:
> I agree that we have a consistency issue here. I am OK with the change.
>
> On Fri, Dec 11, 2015 at 11:
Igniters,
We have a class that is called CacheLoadOnlyStoreAdapter. This is a cache
store adapter that implements utility logic for multithreaded data loading,
so that user has to provide only the logic that queries DB and parses DB
row into object. Everything else is done automatically.
It's a
Igniters,
I'm looking at the question on SO [1] and I'm a bit confused.
We ship ignite-hadoop module only in Hadoop Accelerator and without Hadoop
JARs, assuming that user will include them from the Hadoop distribution he
uses. It seems OK for me when accelerator is plugged in to Hadoop to run
Folks,
Currently there are two different ways how a client node behaves in case
there are no server nodes:
1. If it's trying to start, it will wait and block the thread that
called Ignition.start().
2. If server nodes left when it was already running, it will throw
disconnect
gt;> distribution), or file "/etc/default/hadoop" exists and matches the Hadoop
>> distribution used (BigTop, Cloudera, HDP, etc.)
>>
>> The exact mechanism of the Hadoop classpath composition can be found in
>> files
>> IGNITE_HOME/bin/include/hadoo
ode will become a
> part of the ring.
>
> Is this property applicable or you want to support something different?
>
> --
> Denis
>
> On 12/12/2015 6:13 AM, Valentin Kulichenko wrote:
>
>> Dmitry,
>>
>> How do you think, should we just change the behavior or make
Regarding IGNITE-2212. The original issue is reproduced only with optimized
marshaller, so I don't think it's critical. But at the same time I observe
strange behavior when I run the same test with binary marshaller: to send
an Externalizable object across network, we serialize, deserialize, and
unt the number of (de)serializations
> in
> > that case. Any ideas?
> >
> > D.
> >
> > On Mon, Dec 21, 2015 at 5:31 PM, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > Regarding IGNITE-2212. The original issue is
Igniters,
I just found out that all release download links on [1] are broken (at
least in Chrome).
It seems that there are some template placeholders that are not replaced
properly, because the links look like this:
Moving this discussion to the dev list.
As far as I know, IGFS stores data in blocks, so one file can be
distributed across nodes. So I don't see how each node can persist locally.
In my understanding it should be designated shared directory where all
files are persisted. This is actually
Igniters,
Do we allow to acquire explicit locks (cache.lock(..) method) within an
explicit transaction? Currently it doesn't work which makes me think that
it's an invalid usage, but it fails with NPE [1]. Do we need to fix it or
just provide proper message?
[1]
Folks,
I added the IgniteRDD.keepBinary() method, as described in [1]. Changes are
committed to branch ignite-3215.
Alexey Goncharuk, since you were implementing IgniteRDD, can you please
take a look and check if everything is fine?
[1] https://issues.apache.org/jira/browse/IGNITE-3215
-Val
Hi Saikat,
I reviewed and merged changes you made in scope of [1] (Web Session renewal
after login).
Thanks for you contribution!
[1] https://issues.apache.org/jira/browse/IGNITE-2344
-Val
Hm, we can use it :) Create properly designed IgniteSession class and
deprecate existing IgniteContext.
Thoughts?
-Val
On Thu, May 26, 2016 at 5:47 AM, mabiao wrote:
> And the Apache Spark 2.0 maven repo will be available soon. The spark 2.0
> will no longer use SparkContext
Hi,
This behavior is correct and unfortunately your suggestion is not going to
work. We create only one cache for all atomic structures, so you can't pass
new configuration for each created atomic. It makes perfect sense to define
all parameters that are not specific for a particular atomic
Agree with Denis. Sounds like this can be easily achieved by enabling swap
layer for queue cache. So we just need to put this on configuration.
-Val
On Thu, Jan 14, 2016 at 5:44 AM, Denis Magda wrote:
> Hi,
>
> This seems to be an interesting functionality. As I understand
Igniters,
It sounds like users could be interested in being able to persist the data
saved in queues and sets. See the thread on user list [1].
The obvious solution is to reuse our CacheStore interface, but I'm not sure
that this is possible because it's designed for key-value storage. E.g.,
> content to file system based on the eviction policy?
>
> Thanks,
> Murthy.
>
> On Thu, Jan 14, 2016 at 5:23 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
>> Agree with Denis. Sounds like this can be easily achieved by enabling
>>
As far as I know, these commands come from Memcache protocol. Since we
claim that we're Memcache-compatible, we can't just remove them. But we
definitely should fix the ticket :)
-Val
On Tue, Jun 21, 2016 at 6:21 AM, Saikat Maitra
wrote:
> Sure Dmitriy
>
> I can pick
Hi Andrey,
It seems to me that LOCAL cache simply doesn't have any special handling
here and therefore works in the same way as distributed caches do. I tend
to agree that this is incorrect, can you please create a ticket?
-Val
On Mon, Jun 27, 2016 at 1:16 AM, Andrey Kornev
Igniters,
Interesting question was posted on the user list (see below). Have we ever
tested Hadoop Accelerator with Apache Drill?
-Val
-- Forwarded message --
From: pshomov
Date: Thu, Feb 4, 2016 at 1:56 PM
Subject: Apache Drill querying
Igniters,
Do we have API doc for .NET? If not, I think we should create it and put on
the website.
-Val
Vladimir,
As I already suggested in the ticket [1], I think that by default we should
return metrics for the whole cluster. Now we collect them only from local
node, which is confusing, especially on the client. If one needs metrics
for one node or from subset of nodes, metrics(ClusterGroup)
Alex,
I don't know in advance how many bytes I will write because some classes
can be successfully registered, but some not. Therefore I can't extend by
more than 5 bytes at this point.
Makes sense?
-Val
On Fri, Feb 5, 2016 at 4:02 AM, Alexey Goncharuk wrote:
>
Igniters,
I noticed that we don't inject resources to entry processors. This doesn't
look consistent, because do this everywhere else (closures, jobs,
listeners, etc.). But at the same time I believe it will cause performance
degradation, because we will have to inject on each operation.
Any
e doxygen plans which generate docs. Though, it appears that these
> docs are not published on the website.
>
> Who can assist us with this?
>
> On Fri, Feb 5, 2016 at 1:57 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Igniters,
> >
>
Hi,
First of all, the JavaDoc is incorrect, there are no async counterparts for
queue and set operations in the current API.
The question is - do we need them? I think we should have have them for new
affinityRun and affinityCall methods that you're adding, but I'm not sure
about others.
Does
Hi,
Most likely you have 'java8' profile enabled. Go to Maven
Projects->Profiles and remove the corresponding checkbox.
-Val
On Thu, Feb 11, 2016 at 6:35 AM, Dood@ODDO wrote:
> Hello all,
>
> I am working on a ticket that is not very difficult, if you are good with
>
Nikolay,
As far as I know you were creating Docker images for Ignite.
I just opened it [1] and noticed that the version is 1.0.0 there. Is there
a reason for this? Can we switch it to the latest?
[1] https://hub.docker.com/r/apacheignite/ignite/~/dockerfile/
-Val
Yes, this happens because in a single JVM the dynamic proxy class is
available for Class.forName, but for multi-jvm case this is not true. We
should additionally write information about the implemented interfaces and
manually recreate the proxy during unmarshalling. But the problem is that
it's
Denis,
Yes, this is not supported now, because user doesn't know the underlying
cache name. Here is the ticket:
https://issues.apache.org/jira/browse/IGNITE-1144
-Val
On Thu, Jan 28, 2016 at 2:12 AM, Denis Magda wrote:
> Igniteres,
>
> Seems that the documentation
arshaller
>
>
> Key: IGNITE-1523
> URL: https://issues.apache.org/jira/browse/IGNITE-1523
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Valentin Kulichenko
> Assignee: Valen
, Feb 2, 2016 at 9:20 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Anton,
> >
> > If you're working in this issue, can you please assign it to yourself?
> >
> > -Val
> >
> > -- Forwarded message --
>
Igniters,
I fixed java.lang.reflect.Proxy serialization in both optimized and binary
marshaller. Can someone familiar with marshalling code review my changes
before I merge? Patch is attached to the ticket [1].
[1] https://issues.apache.org/jira/browse/IGNITE-2450
Thanks!
-Val
the same effect be achieved by broadcasting a closure to the
> cluster and executing scan-query on every node locally?
>
> D.
>
> On Wed, Feb 3, 2016 at 9:17 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Igniters,
> >
> > I keep
Igniters,
I keep getting requests from our users to add optional transformers to SCAN
queries. This will allow to iterate through cache, but do not transfer
whole key-value pairs across networks (e.g., get only keys). The feature
looks useful and I created a ticket [1].
I am struggling with the
throw e;
> }
> }
>
> I have included the following at the top of the class
> GridCacheQueueAdapter:
> private final IgniteCompute compute;
>
> this.compute = cctx.kernalContext().grid().compute();
>
> Let me know what you think!
>
>
> On 1/27/2016 3:55 PM,
b, now it shows dockerfile from "1.5.0.final" tag.
>
> [1] https://hub.docker.com/r/apacheignite/ignite/tags
>
> On Fri, Jan 29, 2016 at 9:34 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Nikolay,
> >
> > As fa
Alexey, Igor,
Binary format is internal format used by Ignite, it can't be used directly
or outside of Ignite. So there is no way and no reason to have special
binary serializer in Cassandra store implementation. If user wants to save
BinaryObject as a BLOB to the store (to later load it back to
Hi,
Both GridCacheQueueAdapter and GridCacheSetImpl have a reference to
GridCacheContext which represents the underlying cache for the data
structure. GridCacheContext.name() will give you the correct cache name
that you can use when calling affinityRun method.
-Val
On Wed, Jan 27, 2016 at 9:13
I added couple more tests and merged your changes into master. Thanks for
the contribution!
-Val
On Mon, Feb 22, 2016 at 9:13 PM, Dood@ODDO <oddodao...@gmail.com> wrote:
> Val,
>
> All the test passed on TC - you can look at the PR at any time. Thanks!
>
>
> On 2/2
Folks,
I noticed that the 'newbie' filter on site [1] searches issues by
*component*. But it seems to me that the majority of such tickets are
marked with a label instead, so contributors don't see them when they open
this link.
Is there a policy? For me label makes more sense. 'newbie' is not a
wrote:
> On 2/23/2016 7:05 PM, Valentin Kulichenko wrote:
>
>> I added couple more tests and merged your changes into master. Thanks for
>> the contribution!
>>
>
> Thanks! What other ticket do you think I could/should tackle?
>
Actually, adding Externalizable support to binary marshaller should not be
difficult, no? BinaryWriterExImpl already implements ObjectOutput, so we
just need to pass to writeExternal (and the same for deserialization). To
be honest, I don't understand why we use optimized marshaller here and
Folks,
We have a pretty serious issue [1] that potentially breaks cross-cache
queries in JDBC driver and in other integrations like Zeppelin interpreter,
Spark, etc.
I made a simple fix - catch the exception and create all client caches that
are currently missing.
Can someone review my changes
Sergi,
That's a good point, thanks. I will double-check this.
-Val
On Sat, Feb 27, 2016 at 12:04 PM, Sergi Vladykin
wrote:
> Val,
>
> I didn't look at the code but I hope you've covered case when schema name
> is configured to be different from the cache name?
>
>
Binti,
This is not an issue. What is discussed here is just proper naming of this
configuration property, but the concept stays the same - this is the name
of local Ignite instance and there is no requirement for all nodes in
topology to share the same name.
Whether nodes discover each other or
Yakov,
I'm not sure I understand. What exactly you want to change and how it will
fix the user's issue?
-Val
On Wed, Feb 24, 2016 at 2:21 AM, Yakov Zhdanov wrote:
> Guys,
>
> Please take a look at stacktrace reported here -
>
>
support
this use case. If one wants to query the default cache, leave it blank in
the URL and explicitly specify names of all other caches.
>
>
>
> On Tue, Jan 19, 2016 at 12:47 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > I think we can just
Looks nice, but what is ToQueryable() method for? Is the cache initially
not queryable? :)
-Val
On Fri, Jan 22, 2016 at 9:49 AM, Sergi Vladykin
wrote:
> Looks cool to me.
>
> Sergi
>
> 2016-01-22 18:04 GMT+03:00 Pavel Tupitsyn :
>
> > Igniters,
Folks,
Are ad-hoc queries already available in master?
-Val
-- Forwarded message --
From: ght230
Date: Mon, Feb 15, 2016 at 6:09 AM
Subject: When will Ignite support cross-cache SQL joins?
To: u...@ignite.apache.org
I had learned that in version 1.5, Ignite
Folks,
There were several questions about transactional queues on user forum and
it looks like this is not supported right now.
My question is: why do we have atomicity mode in CollectionConfiguration
then? Does setting it to TRANSACTIONAL change anything?
-Val
Igniters,
One of our users is asking me if this is possible to have a proxy on Java
client for a service implemented in .NET (and vica versa). He tried to do
this, but without success. Is it not supported or he is doing something
wrong?
For me it sounds like a useful feature and I don't see any
Crossposting to dev@.
Folks,
This is not the first time I see this issue. Is there a way to detect it
and throw an exception?
-Val
On Fri, Feb 19, 2016 at 2:42 PM, vkulichenko
wrote:
> Hi Vinay,
>
> Yes, you should always create the configuration object from
Folks,
I recently faced an issue which seems to be pretty critical. As you know,
when binary marshaller meets an Externalizable object, it switches to
optimized marshaller. And if there is a regular object inside, it's still
serialized with optimized, even if its type is declared in binary
I need to do anything special
> looking at IgniteComputeImpl.java it looks like affinityRun()/Call() are
> already implemented in async fashion?)?
>
> Thanks!
>
>
> On 2/12/2016 1:49 PM, Valentin Kulichenko wrote:
>
>> Hi,
>>
>> First of all, the JavaDo
Folks,
I reopened the ticket where we improved the serialization of Ignite
components [1].
>From what I can see, the fix was made for IgniteKernal, but not for other
classes like ClusterGroupAdapter, GridKernalContextImpl and others. What is
the reason for this?
Vladimir Ershov, it looks like
t; introduce
> > SqlTransformQuery. Right? At this point see previous item.
> >
> > Transformation logic is some kind of strategy. IMHO, the most convenient
> > API should get transformation logic as some function provided by user.
> >
> > On Thu, Feb
> Why can’t we simply compare the binary arrays?
>
> On Mon, Feb 29, 2016 at 9:18 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Igniters,
> >
> > We currently have a pretty serious limitation for binary objects: they
> can
> &g
Andrey,
Any comparable object can be used as a field. You can execute a query like
'my_object > ?' and provide the instance of the object as an argument. Of
course, this is not something that everyone does, but it can be useful in
some cases. And now it's fully supported with JDK or optimized
Folks,
I noticed that we use pessimistic transaction to update atomic reference.
Is there any reason for that? Why don't we use atomic cache and invoke()
instead?
-Val
mHolder@5e2c15f7
>>>
>>>> ])
>>>>>> but failed to remove it when the web application was stopped. Threads
>>>>>>
>>>>> are
>>>
>>>> going to be renewed over time to try and avoid a probable memory le
Folks,
I tried to switch to Geronimo and it works fine for me. Are we going to
wait for version 1.0, or we're OK with alpha?
-Val
On Mon, Mar 28, 2016 at 7:37 AM, Dmitriy Setrakyan
wrote:
> Igniters,
>
> Can someone check if the Geronimo JCache jar is the same as the
Alexei,
I would start with defining which thread locals cause this and why they are
not properly cleaned on node shutdown. Ideally, this should never happen.
-Val
On Tue, Apr 5, 2016 at 10:36 AM, Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:
> Hello.
>
> Currently I'm working on the
Folks,
Do we have a component or a label that we commonly use to mark
documentation-related tickets?
-Val
Valentin, I think we should have a “documentation” component.
>
> Having browsed through the component list, we should get rid of the
> following components:
> “1.4”, “community”, “newbie”. I am not sure how these names got there, but
> they are not components.
>
> D.
>
&
Hi Paolo,
See my comment in the ticket.
-Val
On Wed, Mar 2, 2016 at 2:04 AM, Paolo Di Tommaso
wrote:
> Hi Val,
>
> I surely can contribute on that issue but I would need a fix as soon as
> possible so I will do both. Thus, I will try the dirty path on my own
>
Vladislav,
I provided my thoughts in the ticket. Please take a look.
-Val
On Mon, Feb 29, 2016 at 8:46 AM, Vladisav Jelisavcic
wrote:
> Sure, no problem.
>
> I created a ticket:
> https://issues.apache.org/jira/browse/IGNITE-2735
>
> and a PR to resolve this problem.
> I
Hi Konstantin,
Do you have any progress on this ticket? When do you plan to finish it?
-Val
On Wed, Mar 2, 2016 at 2:54 AM, Yakov Zhdanov wrote:
> Hi Konstantin!
>
> I have added a comment to the ticket.
>
> --Yakov
>
> 2016-03-01 16:13 GMT+03:00 Konstantin Margorin
+1 (binding)
On Fri, May 20, 2016 at 1:48 AM, Nikolay Tikhonov
wrote:
> +1 (binding)
>
> On Fri, May 20, 2016 at 10:38 AM, Anton Vinogradov <
> avinogra...@gridgain.com
> > wrote:
>
> > +1 (binding)
> >
> > On Fri, May 20, 2016 at 12:16 AM, Vladimir Ozerov
Vasiliy,
You can specify failover SPI to use for a particular task via
@ComputeTaskSpis annotation. If there is no annotation, the first SPI in
the list will be used.
-Val
On Tue, May 17, 2016 at 12:02 AM, Vasiliy Sisko wrote:
> Hello Igniters.
>
>
> I noticed that a grid
Hi Naden,
If you already have a fix, you should provide a patch or create a PR and
someone in the community will take a look. The workflow is described in
details here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Workflow
If you have any technical
Biao Ma,
I just merged your first fix in Apache Ignite. Congratulations and thanks
for your effort!
Looking forward to more contributions from you.
-Val
Hi Juan,
All our modules have the same version. So when you create a new one, simply
specify the same version that ignite-core has.
-Val
On Wed, May 25, 2016 at 9:44 AM, Juan Carlos Fiorenzano <
jcfiorenzan...@gmail.com> wrote:
> Hello everybody I wan to create a new module to integrate Ignite
Crossposting to dev@
Folks,
I noticed the exception below in couple of user threads already. This
actually means that partition number for the key is -1, which doesn't make
much sense to me. Does anyone has any ideas?
Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
at
SET query is for IgniteSet and it's internal only, not exposed to the
public API.
-Val
On Mon, Jul 25, 2016 at 3:37 PM, Dmitriy Setrakyan
wrote:
> My comments are below...
>
> On Thu, Jul 7, 2016 at 9:41 AM, Alexey Kuznetsov
> wrote:
>
> > Hi,
unction like enum('MY_ENUM_NAME') but probably it will not
> work if we will not pass enum type there as well, so it have look like
> enum('com.mycompany.MyEnum', 'MY_ENUM_NAME') which is ugly.
>
> Sergi
>
> On 23 июля 2016 г., 0:43, Valentin Kulichenko <
> valentin.kuliche
Hi Igor,
I noticed that current Cassandra store implementation doesn't support
batching for writeAll and deleteAll methods, it simply executes all updates
one by one (asynchronously in parallel).
I think it can be useful to provide such support and created a ticket [1].
Can you please give your
1 - 100 of 1097 matches
Mail list logo