curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cammckenzie <>
Subject [GitHub] curator pull request: CURATOR-173
Date Mon, 23 Feb 2015 21:41:38 GMT
Github user cammckenzie commented on the pull request:
    @dkesler That's a good point, and I guess is going to be an inherent flaw with any implementation
that does not persist the schema somewhere. I guess that persisting the lock schema to ZK
would be a possibility but it seems a bit over engineered. Perhaps your static approach is
the best for now, and we can retrofit something else down the track if we have new locking
implementations that have dynamic schemas.
    I'll hopefully get another chance to look at your patch in a bit more detail today.

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 enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message