Hi Timotheé,
yes I think this is valuable - the idea of the discovery API is to abstract
the discovery and if we can benefit in certain scenarios from already
available mechanism/information I think it makes totally sense to use that
instead of adding the same on top of it.
Right now, the
Hi,
+1 for distribution of properties via S3, makes perfect sense. Perhaps
abstracting behind an API so that any low latency globally distributed
storage provider could be used.
Not sure about discovery. Although [0] described the AWS VM, it
doesn't, without further validation describe if the
Konrad Windszus created SLING-3547:
--
Summary: Default handling for numerical types on Sling Models
broken
Key: SLING-3547
URL: https://issues.apache.org/jira/browse/SLING-3547
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994953#comment-13994953
]
Carsten Ziegeler commented on SLING-3525:
-
[~jhoh] Could you provide the full
Hi,
2014-05-12 9:02 GMT+01:00 Ian Boston i...@tfd.co.uk:
Hi,
+1 for distribution of properties via S3, makes perfect sense. Perhaps
abstracting behind an API so that any low latency globally distributed
storage provider could be used.
Yes, discussing this offline with Felix, an alternative
If the usecase is only for Discovery it might be simpler to run Apache
Zookeeper [1] and use Apache Curator [2] as noted in SLING-2939.
While running on AWS one can possibly use Netflix Exhibitor [3] which
manages the Zookeeper instances and backup there state in S3.
The benefit of this approach
Hi Chetan,
On Thu, May 8, 2014 at 1:24 AM, Chetan Mehrotra
chetan.mehro...@gmail.com wrote:
On Wed, May 7, 2014 at 11:29 AM, Carsten Ziegeler cziege...@apache.org
wrote:
Therefore I think we should move this bundle from its current place in the
contrib section to the bundles section.
Whats
[
https://issues.apache.org/jira/browse/SLING-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-3489:
---
Assignee: Carsten Ziegeler
Fix the instructions on how to launch/deploy the demos
[
https://issues.apache.org/jira/browse/SLING-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-3117:
---
Assignee: Robert Munteanu
Node order changes made in .content.xml files are not persisted
[
https://issues.apache.org/jira/browse/SLING-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993559#comment-13993559
]
Robert Munteanu commented on SLING-2635:
*
[
https://issues.apache.org/jira/browse/SLING-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-3116.
Resolution: Fixed
* http://svn.apache.org/viewvc?view=revisionrevision=1593959 implemented
For completeness, here's my +1 ( non-binding )
On Tue, May 6, 2014 at 12:26 PM, Robert Munteanu romb...@apache.org wrote:
We're missing one binding vote, can someone else please take a look?
Robert
On Tue, May 6, 2014 at 9:16 AM, Carsten Ziegeler cziege...@apache.org wrote:
+1
2014-05-05
Github user asfgit closed the pull request at:
https://github.com/apache/sling/pull/14
---
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
Robert Munteanu created SLING-3552:
--
Summary: Update minimum requirement to Eclipse Kepler
Key: SLING-3552
URL: https://issues.apache.org/jira/browse/SLING-3552
Project: Sling
Issue Type:
I'd agree with Chetan and Ian here in that S3 sounds feasible for
persisting properties in a topology (rather than relying on the
non-persistent nature of discovery-properties). The implementation of
discovery itself I see as a separate discussion.
Cheers,
Stefan
On 5/12/14 1:00 PM, Chetan
[
https://issues.apache.org/jira/browse/SLING-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-3493:
---
Assignee: Carsten Ziegeler
Javashell demo doesn't work
---
[
https://issues.apache.org/jira/browse/SLING-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili resolved SLING-3548.
Resolution: Fixed
fixed in r1593249
Replication queue servlet doesn't use the queue
[
https://issues.apache.org/jira/browse/SLING-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995180#comment-13995180
]
Robert Munteanu commented on SLING-3116:
*
[
https://issues.apache.org/jira/browse/SLING-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sechyn updated SLING-3516:
---
Attachment: ChildResourceInjectorPatch.diff
sorry for that. i have created and attached a new diff
[
https://issues.apache.org/jira/browse/SLING-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995095#comment-13995095
]
Carsten Ziegeler commented on SLING-3493:
-
[~bosschaert] Thanks for the work and
[
https://issues.apache.org/jira/browse/SLING-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3529.
-
Resolution: Fixed
Move startup handling to a separate bundle
[
https://issues.apache.org/jira/browse/SLING-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995163#comment-13995163
]
Justin Edelson commented on SLING-3516:
---
Please do not include formatting changes in
[
https://issues.apache.org/jira/browse/SLING-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sechyn updated SLING-3516:
---
Attachment: (was: ChildResourceInjectorPatch.txt)
Sling Models Resource Child List Injector
[
https://issues.apache.org/jira/browse/SLING-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995106#comment-13995106
]
ASF GitHub Bot commented on SLING-3459:
---
Github user asfgit closed the pull request
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/488/
GitHub user kwin opened a pull request:
https://github.com/apache/sling/pull/16
SLING-3547, add test for numerical defaults (both boolean and long,
test exposing the wrong behaviour of numerical defaults in Sling Models
You can merge this pull request into a Git repository by
See https://builds.apache.org/job/sling-trunk-1.7/489/changes
[
https://issues.apache.org/jira/browse/SLING-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3489.
-
Resolution: Fixed
Thanks for your work and patch, David. It's applied with rev 1593967
[
https://issues.apache.org/jira/browse/SLING-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993870#comment-13993870
]
Robert Munteanu commented on SLING-3551:
*
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/492/
30 matches
Mail list logo