GitHub user akuznetsov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/219
IGNITE-1888 Added support for Spring Application context for benchmark node
Added Spring App Context.
You can merge this pull request into a Git repository by running:
$ git pull ht
Hi Denis:
I tried compute.call(new ExampleServiceImplA());
But if my service is by ModuleA.ExampleServiceImpl call
ModuleB.ExampleServiceImpl,
and ModuleB.ExampleServiceImpl call other complicated service.
The ModuleA only has ExampleServiceImpl there is
Alexey Kuznetsov created IGNITE-1888:
Summary: IgniteNode for Yardstick stared without Spring
ApplicationContext
Key: IGNITE-1888
URL: https://issues.apache.org/jira/browse/IGNITE-1888
Project: Ig
Andrey Novikov created IGNITE-1887:
--
Summary: REST-HTTP change queryId generation from sequence to
random.
Key: IGNITE-1887
URL: https://issues.apache.org/jira/browse/IGNITE-1887
Project: Ignite
Thanks Raul, this is great!
Can you please describe again the philosophy between choosing a fragment or
a bundle for Ignite dependencies. I couldn’t fully grasp it from your
explanation.
D.
On Tue, Nov 10, 2015 at 4:17 PM, Raul Kripalani wrote:
> Hi all,
>
> Just to inform you that I've pushed
Gentlemen,
I have several comments below…
On Tue, Nov 10, 2015 at 11:52 AM, Raul Kripalani wrote:
> Andrey, I already specified some points of my disagreement in the Wiki. In
> my previous email I also said: "If we create an SPI it should be for more
> generic hinting applicable in other circum
Hi all,
Just to inform you that I've pushed the POM changes to generate the OSGi
Manifest for all Java modules except: gce, cloud, hadoop, log4j2, spark,
yarn, mesos, as the prove a bit more difficult for different reasons each.
Some modules are bundles (e.g. mqtt, zookeeper, kafka, etc.) while o
GitHub user endian675 opened a pull request:
https://github.com/apache/ignite/pull/218
Ignite 1681
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/endian675/ignite ignite-1681
Alternatively you can review and apply these changes
Github user endian675 closed the pull request at:
https://github.com/apache/ignite/pull/217
---
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 e
GitHub user endian675 opened a pull request:
https://github.com/apache/ignite/pull/217
Ignite 1681
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/endian675/ignite ignite-1681
Alternatively you can review and apply these changes
Igniters,
While investigating this issue reported by user, I noticed that LOCAL cache
is fully destroyed when close() is called, which is inconsistent with other
cache modes. Is there any reason for this?
-Val
-- Forwarded message --
From: vkulichenko
Date: Tue, Nov 10, 2015 at
Sergi,
I tried to execute this query and got an NPE in H2:
https://issues.apache.org/jira/browse/IGNITE-1886. Can you please take a
look?
-Val
-- Forwarded message --
From: ght230
Date: Tue, Nov 10, 2015 at 8:46 AM
Subject: Re: Does Ignite support nested SQL Queries?
To: u...@ig
Valentin Kulichenko created IGNITE-1886:
---
Summary: NPE in H2 when running query with subselects
Key: IGNITE-1886
URL: https://issues.apache.org/jira/browse/IGNITE-1886
Project: Ignite
I
Hi Denis
I'm looking at it now
Regards
Mike
On Tue, Nov 10, 2015 at 11:19 AM, Denis Magda wrote:
> Michael,
>
> Would you mind finishing that task? You should add a couple of tests to
> validate that everything works is expected. I've put all the info into the
> ticket.
>
>
> Regards,
> Denis
Guys,
we are working to have Zeppelin as a part of upcoming Bigtop 1.1 stack. Does
anyone here has/can share with us the interpreter.json content for Ignite, so
we don't need to re-invent the wheel?
Thanks in advance!
--
Take care,
Cos
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
C
Branch deletion moratorium is a temp. thing. Should be lifted once they figure
out a couple of things... Shouldn't be set in the first place, IMO
On Mon, Nov 09, 2015 at 01:59PM, Artem Shutak wrote:
> Igniters,
>
> Since no one can delete any branch Apache Git repo I've been created
> https://cwi
Raúl Kripalani created IGNITE-1885:
--
Summary: Ignite ZooKeeper: Upgrade Curator to 2.9.1
Key: IGNITE-1885
URL: https://issues.apache.org/jira/browse/IGNITE-1885
Project: Ignite
Issue Type: I
Andrey, I already specified some points of my disagreement in the Wiki. In
my previous email I also said: "If we create an SPI it should be for more
generic hinting applicable in other circumstances during serialisation with
other frameworks and what not."
What I don't understand is the interest i
Raul,
Could you please be a bit more specific about the nature of your disagreement?
Is the proposed SPI not generic enough? Or, is it just the naming?
As per Romain's suggestion, could you please just make sure the SPI is hooked
into the new marshalling implementation and a no-op codec implem
GitHub user iveselovskiy opened a pull request:
https://github.com/apache/ignite/pull/216
IGNITE-1566: fix + new test.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/iveselovskiy/ignite ignite-1566
Alternatively you can review
Hi Romain,
The implementation I have in mind won't be costly. I'm working on it this
week.
I still don't agree with a ClassLoaderCodec SPI as-is. If we create an SPI
it should be for more generic hinting applicable in other circumstances
during serialisation with other frameworks and what not.
O
Sorry I haven't made an appearance in this thread yet.
> 6. MQTT streamer
> https://issues.apache.org/jira/browse/IGNITE-535
Yes, it was merged to master before the ignite-1.5 was created.
I'd like to add:
Camel Streamer => https://issues.apache.org/jira/browse/IGNITE-1790
-- I'll merge this as
Guys,
A quick update on the release status.
I have spotted several potential slowdowns that I would like to add to 1.5
release. I am currently working in a separate branch and preliminary
testing showed that we can get about 4-5% performance improvement in tx-put
benchmark. There are other potent
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/215
IGNITE-1884 .Net: JNI local ref can't be accessed from another thread
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-
Pavel Tupitsyn created IGNITE-1884:
---
Summary: .Net: JNI local ref can't be accessed from another thread
Key: IGNITE-1884
URL: https://issues.apache.org/jira/browse/IGNITE-1884
Project: Ignite
To be honest Raoul, I'm more interesting in the interface (SPI) declaration
than the implementation. If you can do it for the 1.5 I'm ok. Otherwise I
ready to start it by introducing the interface and implementing the dummy
version for non OSGi environment.
It will free me to implement a temporary
Hi Romain,
If you don't mind, I'm working on the entire OSGi integration including the
serialisation technique.
I'll ping you if I need help.
Thanks for your collaboration,
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/214
IGNITE-1881 .Net: Rename "portable" to "binary/binarizable"
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-1881
Alte
Hi,
I have put my comments. Hope they will make the things progress :)
Should I start to implement this ticket or should I wait and see if Raoul
want to take it?
Romain
Le mar. 10 nov. 2015 à 02:58, Dmitriy Setrakyan a
écrit :
> Thanks Raul, great points! I have created a ticket for the
> class
Sergey Kozlov created IGNITE-1883:
-
Summary: Test path to swap files of a cache during cache creating
Key: IGNITE-1883
URL: https://issues.apache.org/jira/browse/IGNITE-1883
Project: Ignite
I
Vladislav, do you have any updates for
https://issues.apache.org/jira/browse/IGNITE-638? Or any questions?
--Yakov
2015-11-02 22:23 GMT+03:00 Vladisav Jelisavcic :
> >10. I would also like to include distributed Semaphore. Vladislav, any
> >chance you can finish with it this week?
> >https://iss
Vladimir Ozerov created IGNITE-1882:
---
Summary: Rename BinaryTypeIdMapper to BinaryIdMapper
Key: IGNITE-1882
URL: https://issues.apache.org/jira/browse/IGNITE-1882
Project: Ignite
Issue Type
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/213
IGNITE-1880 .Net: Intermittent "Invalid global JNI handle passed to
DeleteGlobalRef"
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsy
Val,
I've tried to run the nodes using the configuration discussed below on
OS X Yosemity.
Works perfectly fine, both nodes joined the topology and see each other.
Will try to check on OS X El Captain a bit later.
BTW, the problem may be in IPv6. I googled for post [1]. The issue
discussed t
Michael,
Would you mind finishing that task? You should add a couple of tests to
validate that everything works is expected. I've put all the info into
the ticket.
Regards,
Denis
Pavel Tupitsyn created IGNITE-1881:
---
Summary: .Net: Rename "portable" to "binary/binarizable"
Key: IGNITE-1881
URL: https://issues.apache.org/jira/browse/IGNITE-1881
Project: Ignite
Issue
Pavel Tupitsyn created IGNITE-1880:
---
Summary: .Net: Intermittent "Invalid global JNI handle passed to
DeleteGlobalRef"
Key: IGNITE-1880
URL: https://issues.apache.org/jira/browse/IGNITE-1880
Projec
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/212
IGNITE-1845 .Net: Adopt portable API changes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-1845-2
Alternatively yo
Alexey Kuznetsov created IGNITE-1879:
Summary: Add platforms configurations
Key: IGNITE-1879
URL: https://issues.apache.org/jira/browse/IGNITE-1879
Project: Ignite
Issue Type: Sub-task
Dmitriyff created IGNITE-1878:
-
Summary: Implement support to package manager for vendor libs
Key: IGNITE-1878
URL: https://issues.apache.org/jira/browse/IGNITE-1878
Project: Ignite
Issue Type: S
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/191
---
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 enabl
Hi Ken!
My idea was to quit using distributed atomic long, but switch to invokes
that change values atomically. In most cases this can work over atomic
cache and provide faster performance.
Does anyone in community have comments?
--Yakov
2015-11-10 10:49 GMT+03:00 Ken Cheng :
> Hi Yakov Zhdano
42 matches
Mail list logo
