Ah, missed that. Thanks!
It is pity to see how Scala based platform forces every downstream to treat
Java code like a second-class citizen. How nice ;(
Cos
On Fri, Oct 09, 2015 at 01:11PM, Andrey Gura wrote:
> Cos,
>
> Ignite provides Java friendly RDD API. See JavaIgniteContext and
> JavaIgnit
Hi Shashank,
Welcome to the Ignite community!
Please properly subscribe to the dev list by sending email to
dev-subscr...@ignite.apache.org and following instructions in the reply.
For resources and information on how to get involved, you can use the
community section of the website:
https://ig
Pavel, can you explain how .NET async semantics are different from Java?
On Fri, Oct 9, 2015 at 1:46 PM, Pavel Tupitsyn
wrote:
> Hi Dmitry,
>
> > First of all, from my experience, the async APIs are used a lot less
> than sync
> ones
>
> This may be true, especially if the API is clunky.
> But .
Guys,
We had to get rid of md5 sum long time ago, but it seems that sha1 is hitting
the wall as well. Here's the good description of the problem:
https://sites.google.com/site/itstheshappening/
I'd suggest to scrape both of them in the next release. Any objections?
Cos
Hi Dmitry,
> First of all, from my experience, the async APIs are used a lot less than sync
ones
This may be true, especially if the API is clunky.
But .NET has async/await functionality which makes async code a lot cleaner
and easier.
Good async/await support is very important, because it does n
Hello everyone,
I am very keen and looking forward to get involved into development process at
Apache ignite.
Thanks & Regards,
Shashank Gupta
ProstGrad Student (BigData Science)
Queen Mary University of London
London.
Sent from my iPhone
I don't think I like the proposed change.
First of all, from my experience, the async APIs are used a lot less than
sync ones, so having 2 lines of code for async calls is not a big deal in
my view.
Secondly, the scope of this change would be huge. We would have to double
our Compute, Cache, Serv
I will add +1 on this, which together with Andrey's +10, brings the total
to +11 :)
D.
On Fri, Oct 9, 2015 at 7:48 AM, Andrey Kornev
wrote:
> Excellent idea! +10
> PS. Got burnt by this a few times already
> _
> From: Vladimir Ozerov
> Sent: Friday, October 9, 2
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/146
IGNITE-1645 .Net: Throw exception on null flag in PortableReader when
reading non-nullable value types
You can merge this pull request into a Git repository by running:
$ git pull https://g
Excellent idea! +10
PS. Got burnt by this a few times already
_
From: Vladimir Ozerov
Sent: Friday, October 9, 2015 4:22 PM
Subject: Which thread is used to run IgniteFuture continuations?
To:
Igniters,
We are missing an ability to sp
Igniters,
We are missing an ability to specify which thread should run continuation
routine when future is completed.
Currently we either run routine in the callee thread or in completion
thread (usually system pool thread). It means user cannot have any blocking
or cache operations inside the co
Vasilisa Sidorova created IGNITE-1648:
--
Summary: ignitevisorcmd: key "-t" for command "log" works incorrect
Key: IGNITE-1648
URL: https://issues.apache.org/jira/browse/IGNITE-1648
Project: Ignite
As a .Net dev, I support this change very much.
Current design with 2 method calls is not easy to use, is error prone, and
is not familiar to .Net crowd:
var cache = ignite.GetCache().WithAsync();
var value = cache.Get(1); // Is it sync or async? Can't tell from code.
In async mode this always
Igniters,
Some time ago we decided to merge sync and async methods. E.g. instead of
...
interface Cache {
V get(K key);
Future getAsync(K key);
}
... we now have:
interface Cache extends AsyncSupport {
V get(K key);
Cache withAsync();
Future lastFuture(); // From AsyncSuppo
Igor Sapego created IGNITE-1647:
---
Summary: CPP: Implement SqlFieldQuery
Key: IGNITE-1647
URL: https://issues.apache.org/jira/browse/IGNITE-1647
Project: Ignite
Issue Type: Task
Compon
Vladimir Ozerov created IGNITE-1646:
---
Summary: .Net: IgniteGuid must be serializable and portable.
Key: IGNITE-1646
URL: https://issues.apache.org/jira/browse/IGNITE-1646
Project: Ignite
Is
Pavel Tupitsyn created IGNITE-1645:
---
Summary: .Net: Throw exception on null flag in PortableReader when
reading non-nullable value types
Key: IGNITE-1645
URL: https://issues.apache.org/jira/browse/IGNITE-1645
Cos,
Ignite provides Java friendly RDD API. See JavaIgniteContext and
JavaIgniteRDD classes.
On Fri, Oct 9, 2015 at 12:26 AM, Konstantin Boudnik wrote:
> Guys,
>
> I've tried to play a little bit with IgniteContext and the whole IgniteRDD
> stuff from the perspective of not touching Scala ever
Pavel Tupitsyn created IGNITE-1644:
---
Summary: .Net: DateTime.Kind is lost during serialization
Key: IGNITE-1644
URL: https://issues.apache.org/jira/browse/IGNITE-1644
Project: Ignite
Issue
19 matches
Mail list logo
