Cos, I think the proper fix would be to use the default binary marshaller
on both ends, no?
On Mon, Jan 4, 2016 at 11:05 PM, Konstantin Boudnik wrote:
> In the interest of full disclosure, I have fixed the failing test as shown
> in
> http://is.gd/HsrHGf but I am fairly sure it might/will pop-up
Cos, this seems to be just a typo. The actual release version in maven is
1.5.0.final.
On Mon, Jan 4, 2016 at 8:04 PM, Konstantin Boudnik wrote:
> Running into some issues with Zeppelin integration and have noticed that
> the
> version reported by the node in the log isn't the same as the versio
I have reported what might be a similar issue on the separate thread with subj
"Differences in default marshaller"
Cos
On Mon, Jan 04, 2016 at 01:39PM, Vladimir Ozerov wrote:
> Yes, here it is - https://issues.apache.org/jira/browse/IGNITE-2208
>
> On Thu, Dec 31, 2015 at 1:05 AM, Dmitriy Se
In the interest of full disclosure, I have fixed the failing test as shown in
http://is.gd/HsrHGf but I am fairly sure it might/will pop-up in the actual
deployment, because the client node will be started with OptimizedMarshaller
anyway.
Cos
On Mon, Jan 04, 2016 at 08:40PM, Konstantin Boudnik wr
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/393
IGNITE-429: Apache Storm Streamer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shroman/ignite ignite-429
Alternatively you can review and ap
Sure Dmitriy.
Will wait for sometime :) :)
On Mon, Jan 4, 2016 at 11:38 PM, Dmitriy Setrakyan
wrote:
> Hi Chandresh,
>
> Glad to hear that you are starting to work on Python client for Ignite
> RDDs.
>
> Just want to give you heads up that a good chunk of the community is likely
> to be on a po
Fellas,
I have noticed a weird thing while working on upgrading Ignite in Zeppelin.
One of the tests failed because of
Caused by: class org.apache.ignite.spi.IgniteSpiException: Local node's
marshaller differs from remote node's marshaller (to make sure all nodes in
topology have identical mar
Running into some issues with Zeppelin integration and have noticed that the
version reported by the node in the log isn't the same as the version just
released. It says
1.5.0-final
instead of
1.5.0.final
Cos
On Mon, Jan 04, 2016 at 01:12PM, Anton Vinogradov wrote:
> Hello!
>
> Apache Ig
Valentin Kulichenko created IGNITE-2332:
---
Summary: Service proxy can't be created for package-private
implementation
Key: IGNITE-2332
URL: https://issues.apache.org/jira/browse/IGNITE-2332
Proje
Anton,
I have published the release on the website. However, it looks like we are
missing the Javadoc and Scaladoc for 1.5.0.final version. What is the
procedure for adding it?
D.
On Mon, Jan 4, 2016 at 2:12 AM, Anton Vinogradov wrote:
> Hello!
>
> Apache Ignite 1.5.0.final release (RC3) has b
Gents,
I just looked at the Ignite docker image [1] and it has the following
directive in it:
*ENV IGNITE_HOME /opt/ignite/ignite-fabric-1.0.0-incubating*
Looked like it needs some freshening up.
Nick, given that you have been managing this docker account, can you please
update it?
D.
Hi Chandresh,
Glad to hear that you are starting to work on Python client for Ignite
RDDs.
Just want to give you heads up that a good chunk of the community is likely
to be on a post new year hiatus this week, so don’t despair if you don’t
get a response right away :)
D.
On Mon, Jan 4, 2016 at
Lukas Eichler created IGNITE-2331:
-
Summary: RxJava Intergration
Key: IGNITE-2331
URL: https://issues.apache.org/jira/browse/IGNITE-2331
Project: Ignite
Issue Type: Wish
Reporter:
Hello!
Apache Ignite 1.5.0.final release (RC3) has been accepted.
13 "+1" votes received.
Here are the votes received:
- Anton Vinogradov (binding)
- Nikolay Tikhonov (binding)
- Konstantin Boudnik (binding)
- Semyon Boikov (binding)
- Gianfranco Murador (binding)
- Vladimir O
Yes, here it is - https://issues.apache.org/jira/browse/IGNITE-2208
On Thu, Dec 31, 2015 at 1:05 AM, Dmitriy Setrakyan
wrote:
> Vladimir, do you know the ticket number?
>
> On Wed, Dec 30, 2015 at 9:23 AM, Vladimir Ozerov
> wrote:
>
> > This is a known problem, scheduled for 1.6. You can find c
Hi Igniters,
I have started working on this ticket
https://issues.apache.org/jira/browse/IGNITE-949. If anyone of you can help
me out on how to start implementing JIRA tickets.
Thanks in advance
--
Chandresh Pancholi
Senior Software Engineer
Flipkart.com
Email-id:chandresh.panch...@flipkart.com
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/378
---
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 enab
17 matches
Mail list logo
