ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Can Ignite native persistence used with 3rd party persistence?
Date Sun, 14 Jan 2018 02:46:43 GMT
Cross-sending to dev@.

Alexey,

This issue is marked to be fixed for 2.4 which is planned to be released in
a couple of weeks. Do you think you will be able to close this issue before
the release?

D.


On Mon, Dec 18, 2017 at 9:51 AM, Alexey Goncharuk <
alexey.goncharuk@gmail.com> wrote:

> Created the ticket: https://issues.apache.org/jira/browse/IGNITE-7235
>
> 2017-12-15 16:16 GMT+03:00 Alexey Goncharuk <alexey.goncharuk@gmail.com>:
>
>> Ray,
>>
>> With the current API it is impossible to get a reliable integration of
>> Ignite native persistence with 3rd party persistence. The reason is that
>> first, CacheStore interface does not have methods for 2-phase commit,
>> second, it would require significant changes to the persistence layer
>> itself to make a consistent crash recovery.
>>
>> We could allow setting the cache store interface with write-through from
>> primary nodes, but in this case, it would be a user's responsibility to
>> verify that the cache store is consistent with the Ignite cluster. We will
>> try to enable and document it in ignite 2.4.
>>
>> --AG
>>
>> 2017-12-01 14:13 GMT+03:00 Andrey Mashenkov <andrey.mashenkov@gmail.com>:
>>
>>> Hi Ray,
>>>
>>>
>>>> One more question here, how can a update or new inserts back-propagate
>>>> to
>>>> Ignite when another application(not ignite) writes to
>>>> persistence(hbase)?
>>>
>>>
>>> It is not supported.
>>>
>>>
>>>
>>> On Fri, Dec 1, 2017 at 12:08 PM, Ray <rayliu@cisco.com> wrote:
>>>
>>>> http://apache-ignite-users.70518.x6.nabble.com/Two-persisten
>>>> t-data-stores-for-a-single-Ignite-cluster-RDBMS-and-Ignite-n
>>>> ative-td18463.html
>>>>
>>>> Found a similar case here, I think I'll try Slava's suggestions first.
>>>>
>>>> One more question here, how can a update or new inserts back-propagate
>>>> to
>>>> Ignite when another application(not ignite) writes to
>>>> persistence(hbase)?
>>>>
>>>> For example, Ignite and hbase both have one entry for now.
>>>> When another application adds an entry to hbase, now hbase has two
>>>> entries.
>>>> Can Ignite be notified and load the newly added entry automatically?
>>>>
>>>> From the document, it looks like the data can only be propagated from
>>>> Ignite
>>>> to persistence, not the other way around.
>>>>
>>>>
>>>>
>>>> --
>>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Andrey V. Mashenkov
>>>
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message