Hi guys,
That has been done.
https://issues.apache.org/jira/browse/IGNITE-13396
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I see it's already being picked up in another thread:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Queue-Documentation-or-Code-defect-td33703.html
I can't delete this thread.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Yes the common pattern is not documented. So was expecting if no exception is
thrown that I'm getting a queue and can put something on it. But then if I
don't check for null I'll get a NullpointerException.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Could you please file a ticket in Ignite JIRA for 2.10 release? That's
definitely an overlook in the current implementation.
-
Denis
On Tue, Aug 18, 2020 at 9:57 AM Humphrey wrote:
> Hope someone pics this up. That the code is not behaving as the
> documentation
> is saying.
> (Not throwing ex
It’s a good catch, but I think this is one of the developer mailing list.
I see the same behaviour. Arguably it’s consistent with the Ignite#cache()
which returns null if the cache doesn’t exist.
Regards,
Stephen
> On 18 Aug 2020, at 15:29, Humphrey wrote:
>
> Hope someone pics this up. That
Hope someone pics this up. That the code is not behaving as the documentation
is saying.
(Not throwing exception when queue can not be fetched).
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
I think that "could not be fetched or created" hints that some error should
happen to get an exception.
Returning null if an object does not exist is a common pattern in Ignite
API so I suspect this is what is the norm here.
Maybe I'm missing something?
Regards,
--
Ilya Kasnacheev
вт,
Great I see something went missing:
Ignite ignite = Ignition.start();
IgniteQueue queue = ignite.queue("Queue", 0, null);
ignite.close();
In the queue created above I expect it to throw an exception if the queue
can not be fetched, instead it is giving me a queue that is "null".
Check the JavaDo
Here how it will look in the code:
https://github.com/ezhuravl/ignite-code-examples/tree/master/src/main/java/examples/service/scheduler
пн, 2 мар. 2020 г. в 15:23, Evgenii Zhuravlev :
> Hi,
>
> There is no pooler out of the box, but you can simply implement one as a
> Service. Even if one of the
Hi,
There is no pooler out of the box, but you can simply implement one as a
Service. Even if one of the nodes with this service will be stopped,
Cluster will manage to restart the service on another node.
org.apache.ignite.services.Service.execute() should be implemented as queue
pooler.
https:/
10 matches
Mail list logo
