-
Notifications
You must be signed in to change notification settings - Fork 588
HDDS-10511. Support ByteBufferPositionedReadable in OzoneFSInputStream. #6372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
e8c5f80
HDDS-10511. Support ByteBufferPositionedReadable in OzoneFSInputStream.
ashishkr200 21c2c50
Fix old version issue
ashishkr200 84b72e3
Add stream capabilities for positional read
ashishkr200 3ebbaec
Fix review comments
ashishkr200 6e16c9a
Update test case
ashishkr200 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
92 changes: 92 additions & 0 deletions
92
...ozone/ozonefs-common/src/main/java/org/apache/hadoop/fs/ByteBufferPositionedReadable.java
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,92 @@ | ||
| /** | ||
| * Licensed to the Apache Software Foundation (ASF) under one | ||
| * or more contributor license agreements. See the NOTICE file | ||
| * distributed with this work for additional information | ||
| * regarding copyright ownership. The ASF licenses this file | ||
| * to you under the Apache License, Version 2.0 (the | ||
| * "License"); you may not use this file except in compliance | ||
| * with the License. You may obtain a copy of the License at | ||
| * | ||
| * http://www.apache.org/licenses/LICENSE-2.0 | ||
| * | ||
| * Unless required by applicable law or agreed to in writing, software | ||
| * distributed under the License is distributed on an "AS IS" BASIS, | ||
| * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
| * See the License for the specific language governing permissions and | ||
| * limitations under the License. | ||
| */ | ||
| package org.apache.hadoop.fs; | ||
|
|
||
| import java.io.EOFException; | ||
| import java.io.IOException; | ||
| import java.nio.ByteBuffer; | ||
|
|
||
| import org.apache.hadoop.classification.InterfaceAudience; | ||
| import org.apache.hadoop.classification.InterfaceStability; | ||
|
|
||
| /** | ||
| * FIXME: Hack: This is copied from Hadoop 3.3.6. Remove this interface once | ||
| * we drop Hadoop 3.1, 3.2 support. | ||
| * Implementers of this interface provide a positioned read API that writes to a | ||
| * {@link ByteBuffer} rather than a {@code byte[]}. | ||
| * | ||
| * @see PositionedReadable | ||
| * @see ByteBufferReadable | ||
| */ | ||
| @InterfaceAudience.Public | ||
| @InterfaceStability.Evolving | ||
| public interface ByteBufferPositionedReadable { | ||
| /** | ||
| * Reads up to {@code buf.remaining()} bytes into buf from a given position | ||
| * in the file and returns the number of bytes read. Callers should use | ||
| * {@code buf.limit(...)} to control the size of the desired read and | ||
| * {@code buf.position(...)} to control the offset into the buffer the data | ||
| * should be written to. | ||
| * <p> | ||
| * After a successful call, {@code buf.position()} will be advanced by the | ||
| * number of bytes read and {@code buf.limit()} will be unchanged. | ||
| * <p> | ||
| * In the case of an exception, the state of the buffer (the contents of the | ||
| * buffer, the {@code buf.position()}, the {@code buf.limit()}, etc.) is | ||
| * undefined, and callers should be prepared to recover from this | ||
| * eventuality. | ||
| * <p> | ||
| * Callers should use {@link StreamCapabilities#hasCapability(String)} with | ||
| * {@link StreamCapabilities#PREADBYTEBUFFER} to check if the underlying | ||
| * stream supports this interface, otherwise they might get a | ||
| * {@link UnsupportedOperationException}. | ||
| * <p> | ||
| * Implementations should treat 0-length requests as legitimate, and must not | ||
| * signal an error upon their receipt. | ||
| * <p> | ||
| * This does not change the current offset of a file, and is thread-safe. | ||
| * | ||
| * @param position position within file | ||
| * @param buf the ByteBuffer to receive the results of the read operation. | ||
| * @return the number of bytes read, possibly zero, or -1 if reached | ||
| * end-of-stream | ||
| * @throws IOException if there is some error performing the read | ||
| */ | ||
| int read(long position, ByteBuffer buf) throws IOException; | ||
|
|
||
| /** | ||
| * Reads {@code buf.remaining()} bytes into buf from a given position in | ||
| * the file or until the end of the data was reached before the read | ||
| * operation completed. Callers should use {@code buf.limit(...)} to | ||
| * control the size of the desired read and {@code buf.position(...)} to | ||
| * control the offset into the buffer the data should be written to. | ||
| * <p> | ||
| * This operation provides similar semantics to | ||
| * {@link #read(long, ByteBuffer)}, the difference is that this method is | ||
| * guaranteed to read data until the {@link ByteBuffer} is full, or until | ||
| * the end of the data stream is reached. | ||
| * | ||
| * @param position position within file | ||
| * @param buf the ByteBuffer to receive the results of the read operation. | ||
| * @throws IOException if there is some error performing the read | ||
| * @throws EOFException the end of the data was reached before | ||
| * the read operation completed | ||
| * @see #read(long, ByteBuffer) | ||
| */ | ||
| void readFully(long position, ByteBuffer buf) throws IOException; | ||
| } | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will use the ByteBufferPositionedReadable interface defined in hadoop-common directly. This file can be removed. Is there dependency problem for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem is that some of the acceptance tests run with Hadoop 3.2 runtime which does not have this API.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This interface is added in Hadoop 3.3, so the older hadoop version client fails to load ozone fs jar. This file can be removed when we drop support for older hadoop version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. Oh, there are comments explaining this.