GitHub user ezhuravl opened a pull request:
https://github.com/apache/ignite/pull/1677
ignite-4869 remove unnecessary benchmarks for legacy binary identity
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Enjoy: https://ptupitsyn.github.io/LINQ-vs-SQL-in-Ignite/
Hello Dmitriy, thanks! Someone will have a look at your changes soon. Sorry for
the delay.
—
Denis
> On Mar 27, 2017, at 3:24 AM, Дмитрий Рябов wrote:
>
> Hello, can anyone review this issue?
>
> 2017-03-20 16:33 GMT+03:00 Дмитрий Рябов :
>
>>
Hi Rishi,
What is your username in Jira? I will add you as a contributor.
Also please go through [1] and [2] for all the details about our process.
[1] https://ignite.apache.org/community/contribute.html#contribute
[2] https://cwiki.apache.org/confluence/display/IGNITE/Development+Process
-Val
GitHub user iveselovskiy opened a pull request:
https://github.com/apache/ignite/pull/1678
Ignite 1925
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1925
Alternatively you can review and apply
GitHub user skalashnikov opened a pull request:
https://github.com/apache/ignite/pull/1679
IGNITE-4575: Added enum support to SQL queries
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4575
Hi Val,
My user name is ryagnik
Thanks,
Rishi
On Mon, Mar 27, 2017 at 12:14 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Hi Rishi,
>
> What is your username in Jira? I will add you as a contributor.
>
> Also please go through [1] and [2] for all the details about our
Pavel Tupitsyn created IGNITE-4870:
--
Summary: .NET: QueryEntity.TableName
Key: IGNITE-4870
URL: https://issues.apache.org/jira/browse/IGNITE-4870
Project: Ignite
Issue Type: Improvement
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1501
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1648
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user vsisko opened a pull request:
https://github.com/apache/ignite/pull/1673
IGNITE-4838 Check task class on null when task name is invalid.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/1674
IGNITE-4534: Implement offheap eviction policies based on page memory
Per-page eviction policies are implemented, algorithm (random-LRU or
random-K-LRU) can be configured in
Dmitry Karachentsev created IGNITE-4866:
---
Summary: Add lazy value deserialization in
GridCacheRawVersionedEntry
Key: IGNITE-4866
URL: https://issues.apache.org/jira/browse/IGNITE-4866
Project:
Alexandr Kuramshin created IGNITE-4865:
--
Summary: Non-informative error message on using
GridClientOptimizedMarshaller with unknown task classes
Key: IGNITE-4865
URL:
Hi all! There is method that peek cache entry from a cache
org.apache.ignite.internal.processors.cache.GridCacheAdapter#peekEx(java.lang.Object)
And there is another method:
org.apache.ignite.internal.processors.cache.GridCacheMapEntry#peek(boolean,
boolean, boolean,
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/1675
IGNITE-4865 Verbose logging, informative messages
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4865
Hi!
Would be nice if igniteFuture would provide a small but very usable method:
public R to(Function transformer)
it will allow to chain it like:
compute.runAsync(runnable).to(rx()).timeout(5_000).subscribe()
Where rx() is just a static function with something like:
Pavel Tupitsyn created IGNITE-4864:
--
Summary: .NET: Support arrays in SQL
Key: IGNITE-4864
URL: https://issues.apache.org/jira/browse/IGNITE-4864
Project: Ignite
Issue Type: Improvement
Hello, can anyone review this issue?
2017-03-20 16:33 GMT+03:00 Дмитрий Рябов :
> Done.
>
> 2017-03-20 16:30 GMT+03:00 Антон Чураев :
>
>> Dmitry, thank you!
>>
>> Could you please also change issue status to "Patch available".
>>
>> 2017-03-20 16:01
Igniters,
I am glad to announce that old async-style is finally deprecated and now
all asynchronous methods are defined explicitly! Woohoo! Thanks to Taras
for this important contribution.
On Mon, Jan 23, 2017 at 6:12 PM, Taras Ledkov wrote:
> Each compute method produces
Dmitry Karachentsev created IGNITE-4867:
---
Summary: CacheMetricsSnapshot ignores 'size' and 'keySize' fields
Key: IGNITE-4867
URL: https://issues.apache.org/jira/browse/IGNITE-4867
Project:
It doesn't :)
It returns another IgniteFuture where I want to transform it to completely
different type.
On Mon, Mar 27, 2017 at 1:41 PM Дмитрий Рябов wrote:
> IgniteFuture have method
>
> public IgniteFuture chain(IgniteClosure, T>
> doneCb);
>
> which do this.
>
>
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1654
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
IgniteFuture have method
public IgniteFuture chain(IgniteClosure, T>
doneCb);
which do this.
2017-03-27 13:30 GMT+03:00 Sergei Egorov :
> Hi!
>
> Would be nice if igniteFuture would provide a small but very usable method:
>
> public R to(Function
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1649
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1668
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Cool!
Please check my neighboring thread about special .to() method on
IgniteFuture to make it even better :)
On Mon, Mar 27, 2017 at 1:32 PM Vladimir Ozerov
wrote:
> Igniters,
>
> I am glad to announce that old async-style is finally deprecated and now
> all asynchronous
Em... When you get result of your future, closure will produce new future
with completely different type.
2017-03-27 13:43 GMT+03:00 Sergei Egorov :
> It doesn't :)
>
> It returns another IgniteFuture where I want to transform it to completely
> different type.
>
> On Mon, Mar
Andrew Mashenkov created IGNITE-4868:
Summary: SQL: Entry can't be removed from index with
'Object.class' key type configured.
Key: IGNITE-4868
URL: https://issues.apache.org/jira/browse/IGNITE-4868
Evgenii Zhuravlev created IGNITE-4869:
-
Summary: Unnecessary benchmarcs for legacy minary identity
Key: IGNITE-4869
URL: https://issues.apache.org/jira/browse/IGNITE-4869
Project: Ignite
Promising beginning of the week! So many talks in the past and finally we came
to the logical end.
Thanks to both of you Taras and Vovan to making this real ;)
Could any of you update the Migration Guide simplifying the life for those who
will be migrating from AI 1.x?
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1670
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Sergei,
Why should this method be a part of the future API? The only implementation
will do "return func(this);"
I can achieve the same result the following way:
rx(compute.runAsync(runnable)).timeout(5_000).subscribe();
2017-03-27 15:54 GMT+03:00 Sergei Egorov :
> Take a
True, I just prefer functional style over static methods.
Regarding "why should this method be a part of the future API" - why not?
It helps to chain such calls instead of call nesting.
Of course, if Java had extension methods it wouldn't be needed, but we
don't have them.
On Mon, Mar 27, 2017
Take a look at my initial code.
public IgniteFuture chain(IgniteClosure, T> doneCb);
vs
public R to(IgniteClosure, R> transformer);
The result of "chain" is IgniteFuture.
The result of "to" is the object returned from transformer. It would
be CompletableFuture, Rx's Observable, Reactor's
+1 to Alex, this is something external to IgniteFuture.
Should Ignite was implemented in .NET, we could have add proposed feature
it using extension methods. But (un)fortunately Ignite is Java-based :-)
On Mon, Mar 27, 2017 at 4:06 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
>
Alex,
Presently, if to go to the Clusters configuration in Web Console it won’t be
possible to set Kubernetes IP finder as a desired one. Would you mind adding it
to the list?
https://apacheignite-mix.readme.io/docs/kubernetes-discovery
Vasiliy Sisko created IGNITE-4871:
-
Summary: Web console: Implement possibility to configure
Kubernetes IP finder
Key: IGNITE-4871
URL: https://issues.apache.org/jira/browse/IGNITE-4871
Project:
Created issue to add possibility to configure Kubernates IP finder. You can
track it by link: https://issues.apache.org/jira/browse/IGNITE-4871
On Tue, Mar 28, 2017 at 10:18 AM, Denis Magda wrote:
> Alex,
>
> Presently, if to go to the Clusters configuration in Web Console it
Vova,
Agree, I already merged IGNITE-4802.
However, I'm still interested why we always switch to another thread when
executing a job locally. Does anyone have an idea why we do this?
-Val
On Sat, Mar 25, 2017 at 7:22 AM, Vladimir Ozerov
wrote:
> Valya,
>
> I don't think
GitHub user SharplEr opened a pull request:
https://github.com/apache/ignite/pull/1676
IGNITE-4501: Improvement of connection in a cluster of new node
Reopen that PR: https://github.com/apache/ignite/pull/1436
You can merge this pull request into a Git repository by running:
$
Valentin, OK.
To enabled it in my environment I done next:
- built project with command - mvn clean package -DskipTests -Prelease,lgpl
- added folder hibernate to modules in project structure
- added library to dependencies (without it import doesn't working)
After that I have a lot of error,
42 matches
Mail list logo