Re: Id-generator

[Ilya Kasnacheev]

You can specify atomic configuration in your Ignite configuration XML, but
you will have to do key generation manually.

Allocate an IgniteAtomicLong, call methods on it.

Regards,

-- 
Ilya Kasnacheev

2018-05-10 17:50 GMT+03:00 Rusher,Gary <gary.rus...@vizientinc.com>:

> So can I specify IgniteAtomicLong in my cacheconfiguration xml I use to
> bring up my server node?
>
>
>
> Gary
>
>
>
> *From:* Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com]
> *Sent:* Thursday, May 10, 2018 9:17 AM
> *To:* user@ignite.apache.org
> *Subject:* Re: Id-generator
>
>
>
> Hello!
>
> For example, you could have an IgniteAtomicLong, call incrementAndGet() on
> it. This way you can be reasonably sure that numbers are unique per cluster.
>
> Regards,
>
>
> --
>
> Ilya Kasnacheev
>
>
>
> 2018-05-10 16:59 GMT+03:00 Rusher,Gary <gary.rus...@vizientinc.com>:
>
> Hi,
>
>
>
> Doing proof of concept.
>
> Having an issue with identity column, found it’s not possible, but there’s
> a workaround using the ID-generator.
>
>
>
> How does this work?
>
> If I have numerous clients attempting to write db records, won’t the
> id-generator fail to provide a unique value? Maybe?
>
>
>
> Can anyone point me to a simple example of how this works?
>
>
>
> Gary
> --
>
> E-MAIL CONFIDENTIALITY NOTICE: The information transmitted in this e-mail
> and in any replies and forwards are for the sole use of the above
> individual(s) or entities and may contain proprietary, privileged and/or
> highly confidential information. Any unauthorized dissemination, review,
> distribution or copying of these communications is strictly prohibited. If
> this e-mail has been transmitted to you in error, please notify and return
> the original message to the sender immediately at the above listed address.
> Thank you for your cooperation.
>
>
>

RE: Id-generator

[Rusher,Gary]

So can I specify IgniteAtomicLong in my cacheconfiguration xml I use to bring 
up my server node?

Gary

From: Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com]
Sent: Thursday, May 10, 2018 9:17 AM
To: user@ignite.apache.org
Subject: Re: Id-generator

Hello!
For example, you could have an IgniteAtomicLong, call incrementAndGet() on it. 
This way you can be reasonably sure that numbers are unique per cluster.
Regards,

--
Ilya Kasnacheev

2018-05-10 16:59 GMT+03:00 Rusher,Gary 
<gary.rus...@vizientinc.com<mailto:gary.rus...@vizientinc.com>>:
Hi,

Doing proof of concept.
Having an issue with identity column, found it’s not possible, but there’s a 
workaround using the ID-generator.

How does this work?
If I have numerous clients attempting to write db records, won’t the 
id-generator fail to provide a unique value? Maybe?

Can anyone point me to a simple example of how this works?

Gary

E-MAIL CONFIDENTIALITY NOTICE: The information transmitted in this e-mail and 
in any replies and forwards are for the sole use of the above individual(s) or 
entities and may contain proprietary, privileged and/or highly confidential 
information. Any unauthorized dissemination, review, distribution or copying of 
these communications is strictly prohibited. If this e-mail has been 
transmitted to you in error, please notify and return the original message to 
the sender immediately at the above listed address. Thank you for your 
cooperation.

Re: Id-generator

[Ilya Kasnacheev]

Hello!

For example, you could have an IgniteAtomicLong, call incrementAndGet() on
it. This way you can be reasonably sure that numbers are unique per cluster.

Regards,

-- 
Ilya Kasnacheev

2018-05-10 16:59 GMT+03:00 Rusher,Gary :

> Hi,
>
>
>
> Doing proof of concept.
>
> Having an issue with identity column, found it’s not possible, but there’s
> a workaround using the ID-generator.
>
>
>
> How does this work?
>
> If I have numerous clients attempting to write db records, won’t the
> id-generator fail to provide a unique value? Maybe?
>
>
>
> Can anyone point me to a simple example of how this works?
>
>
>
> Gary
> --
> E-MAIL CONFIDENTIALITY NOTICE: The information transmitted in this e-mail
> and in any replies and forwards are for the sole use of the above
> individual(s) or entities and may contain proprietary, privileged and/or
> highly confidential information. Any unauthorized dissemination, review,
> distribution or copying of these communications is strictly prohibited. If
> this e-mail has been transmitted to you in error, please notify and return
> the original message to the sender immediately at the above listed address.
> Thank you for your cooperation.
>