GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/504
IGNITE-2654
Just for demonstration, do not merge.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ilantukh/ignite ignite-2654
Alternatively you
Hello.
Patch for https://issues.apache.org/jira/browse/IGNITE-2650 is available.
Please review.
On Thu, Feb 18, 2016 at 2:10 PM, Konstantin Margorin
wrote:
> Yakov, thank you. Sounds good. I'll do this way.
>
> On Thu, Feb 18, 2016 at 1:43 PM, Yakov Zhdanov
> wrote:
>
>> Konstantin,
>>
>> Her
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/480
---
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
Semen Boikov created IGNITE-2698:
Summary: CacheKeyConfiguration is used only with BinaryMarshaller
Key: IGNITE-2698
URL: https://issues.apache.org/jira/browse/IGNITE-2698
Project: Ignite
Iss
Nikolay Tikhonov created IGNITE-2699:
Summary: Starvation when
CacheEntryListenerConfiguration.isSynchronous is true
Key: IGNITE-2699
URL: https://issues.apache.org/jira/browse/IGNITE-2699
Project
We can use some hacks (which do not seem to be a good solutions to me):
1. throw exception from startStopwatch() if start time has already been
inited. Ugly since currently this method does not throw any error.
2. check if resources have already been injected to SPI before doing new
injection. Not
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/500
---
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
It's a standard (including format and algorithms) to share in-memory data
between several big data platforms.
In my understanding, it is like placing data in in-memory columns in Parquet
and being able to use it in Kudu without serializing/deserializing.
-Roman
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/505
IGNITE-2621 .NET: Fix compute in mixed-platform cluster
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-2621
Alternat
Ilya Lantukh created IGNITE-2700:
Summary: GridClosureProcessor internal closures are [de]serialized
by OptimizedMarshaller even if BinaryMarshaller is configured
Key: IGNITE-2700
URL: https://issues.apache.org/ji
Pavel Tupitsyn created IGNITE-2701:
--
Summary: Binary mode in Data Structures
Key: IGNITE-2701
URL: https://issues.apache.org/jira/browse/IGNITE-2701
Project: Ignite
Issue Type: Improvement
No replies, so I've created an issue:
https://issues.apache.org/jira/browse/IGNITE-2701
On Thu, Feb 18, 2016 at 3:06 PM, Pavel Tupitsyn
wrote:
> Igniters,
>
> Currently we don't have binary mode (withKeepBinary) in Data Structures
> (Queue, AtomicReference).
> Are there any plans for implementin
Vladimir Ozerov created IGNITE-2702:
---
Summary: .NET: Support compact footers in binary format.
Key: IGNITE-2702
URL: https://issues.apache.org/jira/browse/IGNITE-2702
Project: Ignite
Issue
Vladimir Ozerov created IGNITE-2703:
---
Summary: .NET: Dynamically registered classes must use binary
serialization if possible.
Key: IGNITE-2703
URL: https://issues.apache.org/jira/browse/IGNITE-2703
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/506
IGNITE-2700
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ilantukh/ignite ignite-2700
Alternatively you can review and apply these changes a
Igniters,
I'm currently working on the ODBC driver. It connects by TCP to the
OdbcProcessor
on the node side. OdbcProcessor is enabled by default and it starts TCP
server on the
specific TCP port or throws exception if the port is busy.
The problem is that such behavior breaks tests that start mo
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/433
---
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
Igor Sapego created IGNITE-2704:
---
Summary: CPP: Disable ODBC in tests configuration to prevent tests
with multiple nodes from failing.
Key: IGNITE-2704
URL: https://issues.apache.org/jira/browse/IGNITE-2704
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/507
IGNITE-2704: Disabled ODBC for core tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/isapego/ignite ignite-2704
Alternatively you can rev
Hey guys
I was looking at a Camel issue this morning.
https://issues.apache.org/jira/browse/CAMEL-9458
It appears that camel-ignite doesn't install properly in Karaf. Looking at
it further, it seems that Ignite's OSGi module doesn't install in Karaf,
directly. I've copied the output from that
Raul, can you please help with the issue?
--Yakov
2016-02-20 18:03 GMT+03:00 John D. Ament :
> Hey guys
>
> I was looking at a Camel issue this morning.
>
> https://issues.apache.org/jira/browse/CAMEL-9458
>
> It appears that camel-ignite doesn't install properly in Karaf. Looking at
> it furth
How about outputting warning like and keep retrying in a background thread?
warning - "Failed to bind ODBC processor TCP server to port (retrying every
2 sec) [port=ABC]
--Yakov
2016-02-20 17:38 GMT+03:00 Igor Sapego :
> Igniters,
>
> I'm currently working on the ODBC driver. It connects by TCP
What's about to use the port range like TcpDiscoveryVmIpFinder?
On Sat, Feb 20, 2016 at 6:22 PM, Yakov Zhdanov wrote:
> How about outputting warning like and keep retrying in a background thread?
>
> warning - "Failed to bind ODBC processor TCP server to port (retrying every
> 2 sec) [port=ABC]
Not sure if it works. DB connection string should have certain port afaik.
--Yakov
2016-02-20 18:26 GMT+03:00 Sergey Kozlov :
> What's about to use the port range like TcpDiscoveryVmIpFinder?
>
> On Sat, Feb 20, 2016 at 6:22 PM, Yakov Zhdanov
> wrote:
>
> > How about outputting warning like and
This would be a difficult issue to solve because of circular references.
Can we in the mean time just make sure that none of Ignite internal objects
are externalizable, so we don’t purposely force this situation onto our
users?
D.
On Fri, Feb 19, 2016 at 7:15 PM, Valentin Kulichenko <
valentin.ku
It sounds to me that it does not store it’s own data, but allows to process
data from somewhere else, right? If yes, will I be able to take Ignite data
with Arrow and convert it to a columnar format for some other processing?
On Sat, Feb 20, 2016 at 2:48 AM, Roman Shtykh
wrote:
> It's a standard
Val,
I think Ignite Serialization should follow the approach similar to what Java
serialization does: it can transparently and consistently handle both
Serializable and Externalizable classes. It can do it because it relies on a
single class - ObjectOutputStream - to do serialization (and a sin
Andrey, you are absolutely right. I was suggesting a quick fix, which in my
view, would fix most of the issues. In the long term, we should fix the
binary serialization to work the way you are describing.
D.
On Sat, Feb 20, 2016 at 9:26 AM, Andrey Kornev
wrote:
> Val,
>
> I think Ignite Seriali
Hey John,
Yeah, this is expected. Ignite uses some packages only available in the
Oracle JDK (proprietary Sun packages).
Karaf doesn't export the sun.nio.ch package by default from bundle 0
(system bundle).
You need to add it to the jre.properties file manually in the Karaf etc
directory. Then y
Raul,
To my knowledge Ignite can run under OpenJDK as well. Would this package be
required in OpenJDK?
D.
On Sat, Feb 20, 2016 at 11:24 AM, Raul Kripalani wrote:
> Hey John,
>
> Yeah, this is expected. Ignite uses some packages only available in the
> Oracle JDK (proprietary Sun packages).
>
>
That's the million dollar question - I think we should approach the
Arrow people and get a conversation going. We want to be ahead of the
curve, not behind it - Arrow seems to be making quite a stir, not to
mention that it was fast-tracked to mature project status apparently
solely based on the
Agree. Feel free to initiate a discussion on the Arrow list and cross-copy
this list. I will also think about it some more and will propose something
next week.
On Sat, Feb 20, 2016 at 12:13 PM, Dood@ODDO wrote:
> That's the million dollar question - I think we should approach the Arrow
> people
Pavel Tupitsyn created IGNITE-2705:
--
Summary: .NET: Add a test to verify ToolsVersion in project and
solution files
Key: IGNITE-2705
URL: https://issues.apache.org/jira/browse/IGNITE-2705
Project: Ig
Looks like the sun.nio.ch package is included in OpenJDK:
http://hg.openjdk.java.net/jdk8/jdk8/jdk/file/tip/src/share/classes/sun/nio/ch/ServerSocketChannelImpl.java.
But my bet is that Karaf doesn't export it by default because it is not
part of the standard JRE spec.
Raúl.
On 20 Feb 2016 20:0
Denis Magda created IGNITE-2706:
---
Summary: GridHandleTable stores object at incorrect index
Key: IGNITE-2706
URL: https://issues.apache.org/jira/browse/IGNITE-2706
Project: Ignite
Issue Type: B
35 matches
Mail list logo
