[jira] [Created] (IGNITE-2670) Add ability to perfom mass operations

Pavel Konstantinov created IGNITE-2670: -- Summary: Add ability to perfom mass operations Key: IGNITE-2670 URL: https://issues.apache.org/jira/browse/IGNITE-2670 Project: Ignite Issue

Re: C++ / C# Clients?

Both, C++ and C# APIs are included with Ignite download. Links to the documentation can be found on the Ignite website. On Tue, Feb 16, 2016 at 12:14 PM, Mailingliste wrote: > Hi guys, > > > > I was just wondering where to find the promised C++ and C# client? > > > >

[jira] [Created] (IGNITE-2669) IgniteCache.replace() returns false instead of true when there is only one node

Valentin Kulichenko created IGNITE-2669: --- Summary: IgniteCache.replace() returns false instead of true when there is only one node Key: IGNITE-2669 URL: https://issues.apache.org/jira/browse/IGNITE-2669

[jira] [Created] (IGNITE-2667) Allow to start caches in PRIVATE and ISOLATED deployment modes when BinaryMarshaller is used

Denis Magda created IGNITE-2667: --- Summary: Allow to start caches in PRIVATE and ISOLATED deployment modes when BinaryMarshaller is used Key: IGNITE-2667 URL: https://issues.apache.org/jira/browse/IGNITE-2667

C++ / C# Clients?

Hi guys, I was just wondering where to find the promised C++ and C# client? http://apache-ignite-developers.2346864.n4.nabble.com/C-and-NET-td2403.html Many thanks Wiesi ;)

[jira] [Created] (IGNITE-2666) Node is not stopped when RingMessageWorker is interrupted

Denis Magda created IGNITE-2666: --- Summary: Node is not stopped when RingMessageWorker is interrupted Key: IGNITE-2666 URL: https://issues.apache.org/jira/browse/IGNITE-2666 Project: Ignite

[GitHub] ignite pull request: ignite-2649 added failing example

GitHub user VladimirErshov opened a pull request: https://github.com/apache/ignite/pull/489 ignite-2649 added failing example ignite-2649 added failing example You can merge this pull request into a Git repository by running: $ git pull https://github.com/VladimirErshov/ignite

[GitHub] ignite pull request: Ignite 2610 - Fixed excessive memory usage in...

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/488 Ignite 2610 - Fixed excessive memory usage in TTL manager You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2610

[jira] [Created] (IGNITE-2665) NPE in GridCacheIoManager

Sergey Kozlov created IGNITE-2665: - Summary: NPE in GridCacheIoManager Key: IGNITE-2665 URL: https://issues.apache.org/jira/browse/IGNITE-2665 Project: Ignite Issue Type: Bug Affects

[jira] [Created] (IGNITE-2664) Cache.invokeAll() return a map with BinaryObjects instead of user objects.

Artem Shutak created IGNITE-2664: Summary: Cache.invokeAll() return a map with BinaryObjects instead of user objects. Key: IGNITE-2664 URL: https://issues.apache.org/jira/browse/IGNITE-2664 Project:

Re: Externalizable in cache

Thanks, And sorry for a little bit confusing test I provided. 2016-02-16 13:46 GMT+02:00 Vladimir Ozerov : > Myron, > Thank you for pointing this. it looks like we violate stream contract > because regular Java ObjectOutputStream will return -1 in this case. > Forwarding

[jira] [Created] (IGNITE-2663) ODBC: Add protocol version to protocol packet header.

Igor Sapego created IGNITE-2663: --- Summary: ODBC: Add protocol version to protocol packet header. Key: IGNITE-2663 URL: https://issues.apache.org/jira/browse/IGNITE-2663 Project: Ignite Issue

Re: Externalizable in cache

Alex, In ObjectOutputStream if you read byte array and still have some other data in the stream, it will return you -1. So as I understand, from user perspective it is normal to wait for -1. What do you think? Vladimir. On Tue, Feb 16, 2016 at 2:54 PM, Alexey Goncharuk <

[jira] [Created] (IGNITE-2662) .NET Core support

Pavel Tupitsyn created IGNITE-2662: -- Summary: .NET Core support Key: IGNITE-2662 URL: https://issues.apache.org/jira/browse/IGNITE-2662 Project: Ignite Issue Type: New Feature

[GitHub] ignite pull request: IGNITE-2643: Removed ODBC memory leak. Added ...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/487 IGNITE-2643: Removed ODBC memory leak. Added maxConcurrentCursorsPerConnection param to OdbcConfiguration. You can merge this pull request into a Git repository by running: $ git pull

Re: NoopSwapSpaceSpi and dynamically started caches

I think, yes --Yakov 2016-02-16 14:19 GMT+03:00 Konstantin Margorin : > Should we use optional=false in @IgniteSpiConsistencyChecked ? > > On Tue, Feb 16, 2016 at 1:15 PM, Dmitriy Setrakyan > wrote: > > > Sounds good to me. > > > > On Tue, Feb 16, 2016

Re: Externalizable in cache

Agree that this should be fixed. However, from the end-user perspective this should never be an issue because at some point in future Ignite might need to append some extra bytes to the Externalizable object layout, thus reading beyond that limit will break the unmarshalling process. If, by the

Re: Externalizable in cache

Myron, Thank you for pointing this. it looks like we violate stream contract because regular Java ObjectOutputStream will return -1 in this case. Forwarding to dev list. Igniters, As Myron mentioned, out implementation of ObjectInput returns 0 when performing ObjectInput.read(byte[]) and there is

Re: NoopSwapSpaceSpi and dynamically started caches

Should we use optional=false in @IgniteSpiConsistencyChecked ? On Tue, Feb 16, 2016 at 1:15 PM, Dmitriy Setrakyan wrote: > Sounds good to me. > > On Tue, Feb 16, 2016 at 2:13 AM, Yakov Zhdanov > wrote: > > > Let's require that all nodes should have

[jira] [Created] (IGNITE-2661) CPP: Add documentation for Apache Ignite C++

Igor Sapego created IGNITE-2661: --- Summary: CPP: Add documentation for Apache Ignite C++ Key: IGNITE-2661 URL: https://issues.apache.org/jira/browse/IGNITE-2661 Project: Ignite Issue Type: Task

Re: Grid behavior at key deserialization failure during rebalancing

Done https://issues.apache.org/jira/browse/IGNITE-2660 On Tue, Feb 16, 2016 at 12:58 PM, Dmitriy Setrakyan wrote: > Anton, > > If there is no deserialization for binary marshaller, then I would treat it > as a low priority issue. We should file a ticket and get to it when

[jira] [Created] (IGNITE-2660) Correct Grid behavior at key deserialization failure during rebalancing

Anton Vinogradov created IGNITE-2660: Summary: Correct Grid behavior at key deserialization failure during rebalancing Key: IGNITE-2660 URL: https://issues.apache.org/jira/browse/IGNITE-2660

Re: NoopSwapSpaceSpi and dynamically started caches

Sounds good to me. On Tue, Feb 16, 2016 at 2:13 AM, Yakov Zhdanov wrote: > Let's require that all nodes should have same swap space SPI. I think we > can put @GridSpiConsistencyChecked on file swap space SPI (any other > suggestions?). > > --Yakov > > 2016-02-15 23:31

Re: NoopSwapSpaceSpi and dynamically started caches

Let's require that all nodes should have same swap space SPI. I think we can put @GridSpiConsistencyChecked on file swap space SPI (any other suggestions?). --Yakov 2016-02-15 23:31 GMT+03:00 Konstantin Margorin : > Probably I can handle this ticket, but I want to clarify one

Re: Grid behavior at key deserialization failure during rebalancing

Anton, If there is no deserialization for binary marshaller, then I would treat it as a low priority issue. We should file a ticket and get to it when it becomes more critical. D. On Tue, Feb 16, 2016 at 12:37 AM, Anton Vinogradov wrote: > Dmitry, > > I found such

[jira] [Created] (IGNITE-2659) AssertionError in DirectByteBufferStreamImplV2

Avihai Berkovitz created IGNITE-2659: Summary: AssertionError in DirectByteBufferStreamImplV2 Key: IGNITE-2659 URL: https://issues.apache.org/jira/browse/IGNITE-2659 Project: Ignite

[GitHub] ignite pull request: Ignite 2641

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/486 Ignite 2641 You can merge this pull request into a Git repository by running: $ git pull https://github.com/dkarachentsev/ignite ignite-2641 Alternatively you can review and apply

[jira] [Created] (IGNITE-2658) .NET: NHibernate Second Level Cache

Pavel Tupitsyn created IGNITE-2658: -- Summary: .NET: NHibernate Second Level Cache Key: IGNITE-2658 URL: https://issues.apache.org/jira/browse/IGNITE-2658 Project: Ignite Issue Type: New

[jira] [Created] (IGNITE-2657) .NET: SqlDependency for cache items

Pavel Tupitsyn created IGNITE-2657: -- Summary: .NET: SqlDependency for cache items Key: IGNITE-2657 URL: https://issues.apache.org/jira/browse/IGNITE-2657 Project: Ignite Issue Type: New

[jira] [Created] (IGNITE-2656) Documentation on debugging and fixing the reasons of node disconnection from the cluster

Denis Magda created IGNITE-2656: --- Summary: Documentation on debugging and fixing the reasons of node disconnection from the cluster Key: IGNITE-2656 URL: https://issues.apache.org/jira/browse/IGNITE-2656

Re: Remove GridBoundedConcurrentLinkedHashMap and replace its usages with ConcurrentLinkedHashMap

This ticket is more about shaping up the code and will not have any visible effect on the system. These two classes are very similar and I doubt if inheritance that has been introduced there adds any value since ConcurrentLinkedHashMap already has maxSize property. Anyway, it should be a pretty

Re: Grid behavior at key deserialization failure during rebalancing

Dmitry, I found such behavior at GridCacheRebalancingUnmarshallingFailedSelfTest. Seems we always unmarshalling keys at supply message handling in case of OptimizeMarshaller used. Also it happens when BinaryMarshaller used but key class implements Externalizable. On Mon, Feb 15, 2016 at 10:43