From: Wido den Hollander <wido@42on.com>
To: Sage Weil <sweil@redhat.com>, Daniel Hsueh <dchsueh@alumni.uwaterloo.ca>
Cc: ceph-devel@vger.kernel.org, wido@widodh.nl
Subject: Re: any reason why multiple ranged-reads not currently supported in rados-java?
Date: Sat, 16 Aug 2014 20:12:42 +0200 [thread overview]
Message-ID: <53EF9F1A.5090201@42on.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1408150839460.966@cobra.newdream.net>
On 08/15/2014 05:40 PM, Sage Weil wrote:
> On Fri, 15 Aug 2014, Daniel Hsueh wrote:
>> Hello,
>>
>> I'm looking at the Java librados JNA-based API, and note that ranged
>> reads (rados_create_read_op, rados_release_read_op,
>> rados_read_op_read, rados_read_op_operate) are not currently
>> accessible to a Java program.
>>
>> Are there any difficulties in implementing access to these calls? If
>> it is straightforward, I'll implement them myself and contribute back
>> to the github repository.
>
> My guess is this was just an oversight. A patch / pull request wiring
> this up would be awesome.
>
Indeed. I was a bit lazy and implemented what I needed at the time of
writing rados-java.
A pull request is welcome, or just create a issue in the tracker on
http://tracker.ceph.com/
Thanks!
> Thanks!
> sage
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Wido den Hollander
42on B.V.
Phone: +31 (0)20 700 9902
Skype: contact42on
next prev parent reply other threads:[~2014-08-16 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 15:33 any reason why multiple ranged-reads not currently supported in rados-java? Daniel Hsueh
2014-08-15 15:40 ` Sage Weil
2014-08-16 18:12 ` Wido den Hollander [this message]
2014-08-18 15:52 ` Daniel Hsueh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53EF9F1A.5090201@42on.com \
--to=wido@42on.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dchsueh@alumni.uwaterloo.ca \
--cc=sweil@redhat.com \
--cc=wido@widodh.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.