On Wed, Sep 16, 2015 at 9:22 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> I think that at least our direct marshalling is incompatible with big
> endian, because DirectByteBufferStream always uses Unsafe. We should have
> something similar to PortablePrimitives (or even this s
I think that at least our direct marshalling is incompatible with big
endian, because DirectByteBufferStream always uses Unsafe. We should have
something similar to PortablePrimitives (or even this specific class) there
and automatically switch to byte-by-byte processing if needed.
-Val
On Tue, S
ARM device may be working in big endian mode. This can definitely cause
issues with Unsafe that uses predefined x86/x64 offsets (for little
endian) in Ignite code.
I'll dig deeply to prove my conjecture and can respond the user later.
--
Denis
On 9/16/2015 4:48 AM, Dmitriy Setrakyan wrote:
I
On Wed, Sep 16, 2015 at 9:01 AM, Denis Magda wrote:
> The tests keep failing. It means that Alex's changes don't correlate with
> an issue I'm observing in ignite-801.
>
> Put the latest info in [1]
>
Thanks Denis. Let's tackle this ticket in 1.5 release.
>
> --
> Denis
>
>
> On 9/16/2015 8:55
Hello Lalit,
Welcome to the Ignite community!
I think the best way to get started is to download Ignite and start playing
with examples. Once you get comfortable with the feature set, you should
take a look at our JIRA, WIKI, and GIT repository.
All Ignite resources, including information on how
The tests keep failing. It means that Alex's changes don't correlate
with an issue I'm observing in ignite-801.
Put the latest info in [1]
--
Denis
On 9/16/2015 8:55 AM, Denis Magda wrote:
The ticket already exists [1]
I've merged the latest changes from ignite-1.4 that should contain the
l
The ticket already exists [1]
I've merged the latest changes from ignite-1.4 that should contain the
latest Alex's fixes and running the tests for now.
Will send an update shortly.
--
Denis
[1] https://issues.apache.org/jira/browse/IGNITE-801
On 9/16/2015 8:43 AM, Alexey Goncharuk wrote:
I
I did not check those particular tests after both ignite-264 and
ignite-1482 were fixed. There might be something else left to fix, I will
check the tests tomorrow and will create an additional ticket with proper
description if something comes up.
2015-09-15 21:10 GMT-07:00 Dmitriy Setrakyan :
>
Igniters,
I was debugging the ignite-1239 ticket [1] and stumbled across a strange
behavior of IgniteCache#localPeek method. Namely, it peeks DHT cache only
if current node is either primary or backup. On a fast-changing topology
there may be a situation when neither primary nor a backup node is
c
Igniters,
I have come across IGNITE-1482 [1] which we have fixed in the upcoming 1.4
release. The issue we have fixed had to do with IgniteCache.replace(...)
operation not returning a correct value on cluster topology changes.
But a comment in the ticket states that data structures, like AtomicLo
On Tue, Sep 15, 2015 at 9:24 PM, Raul Kripalani wrote:
> On Tue, Sep 15, 2015 at 6:50 PM, Dmitriy Setrakyan <
> dsetrak...@gridgain.com>
> wrote:
>
> > Raul, should we have any documentation for these features on readme.io?
> >
>
> Sure, do I have access? (if I do, I've forgotten, sorry!)
>
Raul
Igniters,
There was a question on SO about using Ignite with ARM:
http://stackoverflow.com/questions/32592881/apache-ignite-arm-unsafe-getfloat-segmentation-fault
Does anyone have any experience with ARM to shed some light on the issue
user is having?
Thanks,
D.
Dmitry,
yes, test attached to the ticket.
On Wed, Sep 16, 2015 at 12:04 AM, Dmitriy Setrakyan wrote:
> Andrey,
>
> Do we have instructions to reproduce this issue?
>
> D.
>
> On Tue, Sep 15, 2015 at 9:35 PM, Andrey Gura wrote:
>
> > Guys,
> >
> > I'd run all Vert.x cluster manager tests (not o
Andrey,
Do we have instructions to reproduce this issue?
D.
On Tue, Sep 15, 2015 at 9:35 PM, Andrey Gura wrote:
> Guys,
>
> I'd run all Vert.x cluster manager tests (not only HA tests) with Ignite
> from ignite-1.4 branch and found that tests randomly hang on partition
> rebalancing. I think t
__
[23:13:17] / _/ ___/ |/ / _/_ __/ __/
[23:13:17] _/ // (7 7// / / / / _/
[23:13:17] /___/\___/_/|_/___/ /_/ /___/
[23:13:17]
[23:13:17] ver. 1.4.0-QASVK150901#20150915-sha1:3e762e25
[23:13:17] 2015 Copyright(C) Apache Software Foundation
[23:13:17]
[23:13:17] Ignite documentation: http://ignite.apac
Guys,
I'd run all Vert.x cluster manager tests (not only HA tests) with Ignite
from ignite-1.4 branch and found that tests randomly hang on partition
rebalancing. I think that this issue didn't reproduce with ignite-1.4
branch.
The problem is cluster manager implementation uses
Ignite.getOrCreate
Nicholas Dzwill created IGNITE-1493:
---
Summary: Fatal exception is thrown during queue instantiation when
using Ignite with an HP-UX machine.
Key: IGNITE-1493
URL: https://issues.apache.org/jira/browse/IGNITE-149
On Tue, Sep 15, 2015 at 6:50 PM, Dmitriy Setrakyan
wrote:
> Raul, should we have any documentation for these features on readme.io?
>
Sure, do I have access? (if I do, I've forgotten, sorry!)
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration sp
On Tue, Sep 15, 2015 at 8:36 PM, Raul Kripalani wrote:
> On Tue, Sep 15, 2015 at 5:12 PM, Yakov Zhdanov
> wrote:
>
> > Raul, how is your status with the streamer? I think there is no reason
> for
> > rush. We can put it to 1.5. Please let me know what you think.
> >
>
> Agree, there's no rush, b
On Tue, Sep 15, 2015 at 5:12 PM, Yakov Zhdanov wrote:
> Raul, how is your status with the streamer? I think there is no reason for
> rush. We can put it to 1.5. Please let me know what you think.
>
Agree, there's no rush, but I'll finish it this evening anyway. It's up to
the community whether t
Thanks Artem. It works !!
On Tue, Sep 15, 2015 at 7:34 PM, Artem Shutak wrote:
> I've found 'log4j-over-slf4j' and log4j are conflicts and leads to your
> error.
>
> I've added next exclusion to storm dependency and it fix the issue. Hope it
> helps.
>
>
> or
Raul, how is your status with the streamer? I think there is no reason for
rush. We can put it to 1.5. Please let me know what you think.
As far as release status here are the open tickets -
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20ignite-1.4%20A
Pavel Tupitsyn created IGNITE-1492:
---
Summary: Platform .Net: Set up FxCop project, fix/suppress warnings
Key: IGNITE-1492
URL: https://issues.apache.org/jira/browse/IGNITE-1492
Project: Ignite
I've found 'log4j-over-slf4j' and log4j are conflicts and leads to your
error.
I've added next exclusion to storm dependency and it fix the issue. Hope it
helps.
org.slf4j
log4j-over-slf4j
-- Artem --
On Tue, Sep 15, 2015
https://github.com/chandresh-pancholi/ignite.
i have commited the changes. Its a half baked implementation.
module - *storm.*
Thanks
On Tue, Sep 15, 2015 at 6:04 PM, chandresh pancholi <
chandreshpancholi...@gmail.com> wrote:
> Forking it from github. will update the thread once push the chang
Forking it from github. will update the thread once push the changes.
Thanks
On Tue, Sep 15, 2015 at 5:45 PM, chandresh pancholi <
chandreshpancholi...@gmail.com> wrote:
> While doing git push i am getting Auth error. Its not accepting git-hub
> profile.
>
>
> On Tue, Sep 15, 2015 at 5:08 PM, Ar
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/94
IGNITE-1491 Platform: Implement platform-dependent
PlatformContext.writeAsPortableObjectSafe
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/p
While doing git push i am getting Auth error. Its not accepting git-hub
profile.
On Tue, Sep 15, 2015 at 5:08 PM, Artem Shutak wrote:
> Hi Chandresh,
>
> It looks like for me you have different log4j versions at your classpath.
> How do you build your project? Did you copy-paste log4j jars by y
GitHub user iveselovskiy opened a pull request:
https://github.com/apache/ignite/pull/93
IG-1376: fixed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/iveselovskiy/ignite ignite-1376
Alternatively you can review and apply thes
Pavel Tupitsyn created IGNITE-1491:
---
Summary: Platform: Implement platform-dependent
PlatformContext.writeAsPortableObjectSafe
Key: IGNITE-1491
URL: https://issues.apache.org/jira/browse/IGNITE-1491
Yakov,
I would be happy if are able to merge all docs in a single place, but I
simply do not see how it is possible from usability perspective.
1) There are lots features which exists only in Java and make little or noe
sense in .Net/CPP. E.g., Mesos, YARN, Docker, IGFS, Hibernate, JDBC, almost
al
Hi Chandresh,
It looks like for me you have different log4j versions at your classpath.
How do you build your project? Did you copy-paste log4j jars by yourself?
It would be nice, if you commit and push a current state of your project at
your fork on github and point out on your fork, branch at f
I am implementing ignite-storm feature. log4j version is my project version.
org.apache.ignite
ignite-log4j
${project.version}
On Tue, Sep 15, 2015 at 4:36 PM, Gianfranco Murador <
murador.gianfra...@gmail.com> wrote:
> Hi chandresh,
> What are you trying to achieve? It seems yo
Hi chandresh,
What are you trying to achieve? It seems you have not set an appropriate
dependencies in your project .What version of log4j are you using?
Regards, Gianfranco
2015-09-15 12:54 GMT+02:00 chandresh pancholi <
chandreshpancholi...@gmail.com>:
> Hi Igniters,
>
> I am facing this issue
Hi Igniters,
I am facing this issue and i guess i am missing some dependency.
Please help!!
junit.framework.AssertionFailedError: *Exception in constructor:
testStormStreamer (java.lang.NoSuchMethodError:
org.apache.log4j.Category.getParent()Lorg/apache/log4j/Category*;
at
org.apache.ignite.testfr
I would like everyone to think over if all docs are in a single space.
Nobody wants to split binaries and codebase. Why split documentation?
Is there ability for readmeio user to set preferred snippet language? This
way user will not have to switch on each page.
--Yakov
2015-09-15 12:31 GMT+03:0
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/81
---
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 enable
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/87
---
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 enable
Let me create one. I will respond here when I am done.
D.
On Tue, Sep 15, 2015 at 1:12 AM, Vladimir Ozerov
wrote:
> Igniters,
>
> Does anyone know how what is the procedure of creating a new space in
> readme.io?
>
> On Mon, Sep 14, 2015 at 9:07 PM, Dmitriy Setrakyan
> wrote:
>
> > We should a
Ilya Suntsov created IGNITE-1490:
Summary: Memory leaks during load testing (+ nearcache)
Key: IGNITE-1490
URL: https://issues.apache.org/jira/browse/IGNITE-1490
Project: Ignite
Issue Type: B
Hi guys,
The MQTT streamer I'm working on will be ready this week. Hopefully as soon
as today or tomorrow.
It's not important for the 1.4 release, but it seems like it'll make the
timeline to get potentially merged.
Regards,
Raúl.
On 15 Sep 2015 00:05, "Yakov Zhdanov" wrote:
> Guys,
>
> Curren
Igniters,
Does anyone know how what is the procedure of creating a new space in
readme.io?
On Mon, Sep 14, 2015 at 9:07 PM, Dmitriy Setrakyan
wrote:
> We should also take into account whether Java users will be interested in
> .NET/C++ and vise versa. In my opinion, the users for .NET/C++ don't
Pavel Konstantinov created IGNITE-1489:
--
Summary: Usability issiues
Key: IGNITE-1489
URL: https://issues.apache.org/jira/browse/IGNITE-1489
Project: Ignite
Issue Type: Sub-task
Vladimir Ozerov created IGNITE-1487:
---
Summary: Exception is always thrown on normal code path when
connecting to IGFS from file system.
Key: IGNITE-1487
URL: https://issues.apache.org/jira/browse/IGNITE-1487
44 matches
Mail list logo
