Hi,
> Im still very interested in understand some of the design chooses oak
> core team had taken and why . For the long lived snapshots what is use
> case for this and also I like to understand how indexes are sync between
> nodes and the role of a oak leader and how the leader node election
>
Hi Team ,
Im still very interested in understand some of the design chooses oak
core team had taken and why . For the long lived snapshots what is use case
for this and also I like to understand how indexes are sync between nodes
and the role of a oak leader and how the leader node election
Hi Marcel , thanks for the information . I would love to understand the use
cases for having long lived snapshots in oak . Would you be able for
provide specific examples or functions within oak that needs this
capability ?
On Wed, Dec 19, 2018 at 12:43 AM Marcel Reutegger
wrote:
> Hi,
>
> On
Hi,
On 18.12.18, 01:55, "ems eril" wrote:
> 1) Is this a blocking call ? And any plans for callback or java future
> support?
Yes, Clusterable.isVisible() is a blocking call and you can give it a timeout.
There are no plans right now to add an async variant of this feature.
> 2) Is there any
Thank Marcel this is very helpful . Couple of questions I have with this
interface
1) Is this a blocking call ? And any plans for callback or java future
support?
2) Is there any JCR level API we can use as its currently very low level ?
If not is Sling have any plans to use this ?
3) Any reason
Hi Matt ,
Yes your correct, the job is triggered by consumer listening to kafka
queue . But to you earlier statement that this is not a Oak issue I have to
disagree . In Mongo you can
control write concern and make replication synchronize but we cannot do
something similar in Oak .
Thanks
On
Hi Matt ,
I was looking for more details on the inner workings . I came across
this https://markmail.org/message/jbkrsmz3krllqghr where it mentioned that
changes in the cluster would eventually appear across other nodes and this
is not a mongo specific issue but something oak has introduced .
Hi Emily,
Content is stored in Oak in two different configurable storage services.
This is a bit of an oversimplification, but basically the structure of
content repository - the content tree, nodes, properties, etc. - is stored
in a Node Store [0] and the binary content is stored in a Blob Store
