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

    https://github.com/apache/spark/pull/4187#discussion_r23501242
  
    --- Diff: 
sql/core/src/main/scala/org/apache/spark/sql/parquet/ParquetConverter.scala ---
    @@ -426,6 +423,33 @@ private[parquet] class CatalystPrimitiveConverter(
         parent.updateLong(fieldIndex, value)
     }
     
    +/**
    + * A `parquet.io.api.PrimitiveConverter` that converts Parquet Binary to 
Catalyst String.
    + * Supports dictionaries to reduce Binary to String conversion overhead.
    + *
    + * Follows pattern in Parquet of using dictionaries, where supported, for 
String conversion.
    + *
    + * @param parent The parent group converter.
    + * @param fieldIndex The index inside the record.
    + */
    +private[parquet] class CatalystPrimitiveStringConverter(parent: 
CatalystConverter, fieldIndex: Int)
    +  extends CatalystPrimitiveConverter(parent, fieldIndex) {
    +
    +  private var dict: Array[String] = null
    --- End diff --
    
    I have a hard time believing this really matters (eg., if its actually hot, 
then the JIT will take care of it), but if we do care about this, should we 
recommend that people *always* use `private[this]`?? I have a hard time 
imaginging that anyone will ever need `private` instead.


---
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