Hello everyone,
My name is Kumar Ashish. I am a 2nd year student at IEM kolkata. My primary
area of interest is backend development and I am willing to participate in
gsoc this summer.
I was looking for open source projects to contribute to and I read that
Apache Ignite will be applying for GSoC
Hi.
Thanks for your comments. Let me investigate the issue deeper.
Regards.
On Thu, Feb 23, 2017 at 11:00 PM, Dmitriy Setrakyan
wrote:
> If you use the same (or default) configuration for the affinity, then the
> same key in different caches will always end up on the same node. This is
> guara
Dear Eclipse Aether community,
In January 2017 Sonatype Nexus repository reported a suspiciously enormous
number of downloads for Apache Ignite artifacts. After conducting the
investigation with the help of Sonatype folks we figured out that Aether
contributed to the most of downloads:
https://
Denis Magda created IGNITE-4750:
---
Summary: SQL: Support GROUP_CONCAT function
Key: IGNITE-4750
URL: https://issues.apache.org/jira/browse/IGNITE-4750
Project: Ignite
Issue Type: Task
Hi Vadim,
Yes, this issue might be still relevant. I can’t guide you through but,
basically, you need to reproduce the issue, spot it in the code and propose a
fix.
BTW, do you have any experience with Hibernate? If so, I would be amazing if
you pick up this ticket reassigning on yourself:
htt
If you use the same (or default) configuration for the affinity, then the
same key in different caches will always end up on the same node. This is
guaranteed.
D.
On Thu, Feb 23, 2017 at 8:09 AM, Andrey Mashenkov <
andrey.mashen...@gmail.com> wrote:
> Val,
>
> Yes, with same affinity function en
GitHub user lammic opened a pull request:
https://github.com/apache/ignite/pull/1572
automatically detect IGNITE_HOME in service.sh
it would be handy to have service.sh detect IGNITE_HOME, without relying on
other files to be sourced before calling it
You can merge this pull reques
Val,
Yes, with same affinity function entries with same key should be saved in
same nodes.
As far as I know, primary node is assinged automatically by Ignite. And I'm
not sure that
there is a guarantee that 2 entries from different caches with same key
will have same primary and backup nodes.
So,
Actually, this should work this way out of the box, as long as the same
affinity function is configured for all caches (that's true for default
settings).
Andrey, am I missing something?
-Val
On Thu, Feb 23, 2017 at 7:02 AM, Andrey Mashenkov <
andrey.mashen...@gmail.com> wrote:
> Hi Alper,
>
>
Hi Alper,
You can implement you own affinityFunction to achieve this.
In AF you should implement 2 mappings: key to partition and partition to
node.
First mapping looks trivial, but second doesn't.
Even if you will lucky to do it, there is no way to choose what node wil be
primary and what will b
Thanks Val for looking into it.
On Wed, Feb 22, 2017 at 9:32 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Hi Rishi,
>
> Got it, I think I'm reproducing the issue. I'll take a look and let you
> know my findings soon.
>
> -Val
>
> On Tue, Feb 21, 2017 at 7:27 PM, Rishi Yagnik
I think it makes a sense to define factory in IgniteConfiguration, as the
Map which will be ised when deserializing.
Interface example:
public intterface InstanceFactory {
newInstance(Class clazz, BinaryReader reader);
}
P.S.
About "constructor(BinraryReader reader)" - I think there is no se
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/1571
IGNITE-4539: RocketMQ Streamer implementation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shroman/ignite IGNITE-4539
Alternatively you ca
Dear sirs !
I want to resolve issue IGNITE-933
https://issues.apache.org/jira/browse/IGNITE-933
Is it actual ?
In which class and method you want me to make changes ?
Vadim Opolski
14 matches
Mail list logo
