Github user rxin commented on a diff in the pull request:

    https://github.com/apache/spark/pull/2753#discussion_r19438149
  
    --- Diff: 
network/common/src/main/java/org/apache/spark/network/buffer/ManagedBuffer.java 
---
    @@ -0,0 +1,70 @@
    +/*
    + * 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.spark.network.buffer;
    +
    +import java.io.IOException;
    +import java.io.InputStream;
    +import java.nio.ByteBuffer;
    +
    +/**
    + * This interface provides an immutable view for data in the form of 
bytes. The implementation
    + * should specify how the data is provided:
    + *
    + * - {@link FileSegmentManagedBuffer}: data backed by part of a file
    + * - {@link NioManagedBuffer}: data backed by a NIO ByteBuffer
    + * - {@link NettyManagedBuffer}: data backed by a Netty ByteBuf
    + *
    + * The concrete buffer implementation might be managed outside the JVM 
garbage collector.
    + * For example, in the case of {@link NettyManagedBuffer}, the buffers are 
reference counted.
    + * In that case, if the buffer is going to be passed around to a different 
thread, retain/release
    + * should be called.
    + */
    +public abstract class ManagedBuffer {
    +
    +  /** Number of bytes of the data. */
    +  public abstract long size();
    +
    +  /**
    +   * Exposes this buffer's data as an NIO ByteBuffer. Changing the 
position and limit of the
    +   * returned ByteBuffer should not affect the content of this buffer.
    +   */
    +  public abstract ByteBuffer nioByteBuffer() throws IOException;
    --- End diff --
    
    maybe comment on in the future, everything in spark should just operate on 
ManagedBuffer abstraction and we should deprecate nio bytebuffer.


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to