[
https://issues.apache.org/jira/browse/JCLOUDS-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377586#comment-14377586
]
Ignasi Barrera commented on JCLOUDS-849:
The DeploymentApi calls are direct calls
[
https://issues.apache.org/jira/browse/JCLOUDS-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1435#comment-1435
]
Akos Hajnal commented on JCLOUDS-769:
-
As far as I know, in S3, you can use part
[
https://issues.apache.org/jira/browse/JCLOUDS-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated JCLOUDS-769:
Labels: multipart s3 (was: )
Upload blob from stream
---
[
https://issues.apache.org/jira/browse/JCLOUDS-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377702#comment-14377702
]
Bhathiya Supun commented on JCLOUDS-849:
Hi fabio,
I think there won't be any
[
https://issues.apache.org/jira/browse/JCLOUDS-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated JCLOUDS-769:
Affects Version/s: 1.8.1
Upload blob from stream
---
Key:
[
https://issues.apache.org/jira/browse/JCLOUDS-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377619#comment-14377619
]
fabio martelli commented on JCLOUDS-849:
Hi Ignasi, thank you for your prompt
[
https://issues.apache.org/jira/browse/JCLOUDS-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377565#comment-14377565
]
fabio martelli commented on JCLOUDS-849:
Hi, working on this issue I found a
[
https://issues.apache.org/jira/browse/JCLOUDS-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377735#comment-14377735
]
fabio martelli commented on JCLOUDS-849:
Hi Bhathiya, the conflict would be on
[
https://issues.apache.org/jira/browse/JCLOUDS-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377758#comment-14377758
]
Andrew Gaul commented on JCLOUDS-769:
-
This is tricky to implement since jclouds
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Go to
http://8f9f01aa921ee2fd31c9-54b9bade39cf00b7396782e42750d03f.r67.cf5.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/130#issuecomment-85720357
Go to
http://2824a28fd3dd3fddcb8d-dbd2c979c28bf73721663176c4e36725.r61.cf5.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/129#issuecomment-85720194
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
@demobox Can this be closed?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/63#issuecomment-85717848
[
https://issues.apache.org/jira/browse/JCLOUDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated JCLOUDS-631:
Labels: filesystem (was: )
Slowdown of putBlob operation for the FileSystem provider
Merged.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/131#issuecomment-85720599
[
https://issues.apache.org/jira/browse/JCLOUDS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated JCLOUDS-847:
Labels: performance (was: )
S3 poor upload performance
--
[
https://issues.apache.org/jira/browse/JCLOUDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated JCLOUDS-631:
Labels: filesystem performance (was: filesystem)
Slowdown of putBlob operation for the
[
https://issues.apache.org/jira/browse/JCLOUDS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated JCLOUDS-847:
Priority: Major (was: Minor)
S3 poor upload performance
--
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
We should not address this with hacks in karaf. We have a bunch of JIRA issues
tracking these and should address it in core:
https://issues.apache.org/jira/browse/JCLOUDS-193
https://issues.apache.org/jira/browse/JCLOUDS-635
https://issues.apache.org/jira/browse/JCLOUDS-648
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
[
https://issues.apache.org/jira/browse/JCLOUDS-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14378753#comment-14378753
]
Andrew Gaul commented on JCLOUDS-769:
-
[~knl] You might want to push this for review
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Superseded by #705
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/565#issuecomment-85716224
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
What do you mean by continue working on it? I assume you are not planning to
merge it when we consider that the request is open since Nov 30, 2013. So does
it make sense to continue working on it?
---
Reply to this email directly or view it on GitHub:
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
If no one who knows Karaf cares to merge this, I'll just go ahead and close it
on April 3. I'd rather close it unmerged than risk breaking Karaf in some weird
way I'm not prepared to deal with.
---
Reply to this email directly or view it on GitHub:
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
Thanks for the pull request but it's release week in jclouds and that means
it's time to clean up the PR queue. This PR will be over 6 months old as of
April 1. If you intend to continue work on it, please make a comment by April
2. Otherwise it will be closed on April 3.
---
Reply to this
@limorbortman Apologies for the lack of feedback. We're about releasing 1.9.0
and the master branches are frozen. We expect to have it out by the end of the
week, and we'll get back to the pending PRs.
---
Reply to this email directly or view it on GitHub:
[
https://issues.apache.org/jira/browse/JCLOUDS-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14378097#comment-14378097
]
Nikola Knezevic commented on JCLOUDS-769:
-
So, I mad some rudimentary, local
[
https://issues.apache.org/jira/browse/JCLOUDS-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14378097#comment-14378097
]
Nikola Knezevic edited comment on JCLOUDS-769 at 3/24/15 4:28 PM:
@nacx No worries. Thanks. Good luck with the 1.9.0 release!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/143#issuecomment-85589488
+
+public abstract class ForwardingBlobStore extends ForwardingObject
+ implements BlobStore {
+ private final BlobStore blobStore;
+
+ public ForwardingBlobStore(BlobStore blobStore) {
+ this.blobStore = checkNotNull(blobStore);
+ }
+
+ protected BlobStore delegate() {
Hi @nacx, @everett-toews and @zack-shoylev
can you please take a look?
Thanks
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/697#issuecomment-85372414
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/713
-- Commit Summary --
* Add ForwardingBlobStore
* Add ReadOnlyBlobStore
-- File Changes --
A
blobstore/src/main/java/org/jclouds/blobstore/util/ForwardingBlobStore.java
54 matches
Mail list logo
