[
https://issues.apache.org/jira/browse/PARQUET-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17792814#comment-17792814
]
ASF GitHub Bot commented on PARQUET-2405:
-----------------------------------------
amousavigourabi opened a new pull request, #1230:
URL: https://github.com/apache/parquet-mr/pull/1230
Make sure you have checked _all_ steps below.
### Jira
- [x] My PR addresses the following [Parquet
Jira](https://issues.apache.org/jira/browse/PARQUET/) issues and references
them in the PR title. For example, "PARQUET-1234: My Parquet PR"
- https://issues.apache.org/jira/browse/PARQUET-XXX
- In case you are adding a dependency, check if the license complies with
the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
### Tests
- [x] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
### Commits
- [x] My commits all reference Jira issues in their subject lines. In
addition, my commits follow the guidelines
from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue
reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Style
- [x] My contribution adheres to the code style guidelines and Spotless
passes.
- To apply the necessary changes, run `mvn spotless:apply
-Pvector-plugins`
### Documentation
- [x] In case of new functionality, my PR adds documentation that describes
how to use it.
- All the public functions and the classes in the PR contain Javadoc
that explain what it does
> Include logic for a fallback CodecFactory implementation
> --------------------------------------------------------
>
> Key: PARQUET-2405
> URL: https://issues.apache.org/jira/browse/PARQUET-2405
> Project: Parquet
> Issue Type: New Feature
> Components: parquet-mr
> Reporter: Atour Mousavi Gourabi
> Priority: Major
>
> Now that CodecFactories are pluggable in the read/write API, a fallback
> CodecFactory implementation should be included. This would allow users to
> more easily implement their own partially delegating CodecFactory for, for
> example, hardware accelerating a codec they expect to encounter a lot,
> without failing on codecs they did not implement themselves. For these cases,
> the fallback implementation could delegate to the default
> (Direct)CodecFactory, or any other implementation of their liking.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
