IGNITE-1144 has been fixed so at least that obstacle is out of the way :-)
On 2/24/2016 9:10 AM, Denis Magda wrote:
> The community has already faced with the issue that the binary mode is
> not supported for data structures.
>
https://issues.apache.org/jira/browse/IGNITE-2339>
> I've linked this ticket into IGNITE-2701.
>
> --
> Denis
>
> On 2/23/2016 4:29 AM, Valentin Kulichenko wrote:
>> +1 to this change. It sounds like a very important feature for
>> collocated
>> queues, especially after [1] is fixed.
>>
>> [1]
https://issues.apache.org/jira/browse/IGNITE-1144>>
>> -Val
>>
>> On Sat, Feb 20, 2016 at 3:42 AM, Pavel Tupitsyn <
[hidden email]>
>> wrote:
>>
>>> 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
>>> <
[hidden email]>
>>> wrote:
>>>
>>>> Igniters,
>>>>
>>>> Currently we don't have binary mode (withKeepBinary) in Data
>>>> Structures
>>>> (Queue, AtomicReference).
>>>> Are there any plans for implementing this, or may be a workaround?
>>>>
>>>> Lack of binary mode prevents us from implementing IgniteQueue in .NET
>>>> (.NET types in most cases can't be deserialized in Java).
>>>>
>>>> AtomicReference is already implemented, and it works because values
>>>> are
>>>> wrapped in GridCacheAtomicReferenceValue. So there is inconsistent
>>> behavior
>>>> between data structures.
>>>>
>>>> Thoughts?
>>>>
>>>> --
>>>> --
>>>> Pavel Tupitsyn
>>>> GridGain Systems, Inc.
>>>> www.gridgain.com
>>>>
>>>
>>>
>>> --
>>> --
>>> Pavel Tupitsyn
>>> GridGain Systems, Inc.
>>> www.gridgain.com
>>>
>
Locked
