Apache Parquet
Persistent Collection
Our great sponsors
Apache Parquet | Persistent Collection | |
---|---|---|
4 | 4 | |
2,398 | 746 | |
2.5% | - | |
9.2 | 6.6 | |
3 days ago | about 1 month ago | |
Java | Java | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Apache Parquet
-
How-to-Guide: Contributing to Open Source
Apache Parquet
-
parquet-tools
This go implementation, other than common advantages from go itself (small single executable, support multiple platforms, speed, etc.), has some neat features compare with Java parquet tool and Python one like:
-
Writing Apache Parquet Files
Hi, I've been trying to write parquet files on android for the past couple of days, and have really been struggling to find a solution. My original hypothesis was to just use the java parquet implementation (https://github.com/apache/parquet-mr), but I've since realized that not all java libraries play well with Android. I've gone through essentially dependency hell trying to franken-fit the library into my project, and imported as much as i could before hitting walls such as this one (https://github.com/mockito/mockito/issues/841).
-
pqrs: A parquet-tools replacement in Rust using Apache Arrow
Like many of you probably do, I tend to work with Parquet files a lot. parquet-tools has been my tool of choice for inspecting parquet files, but that has been deprecated recently. So, I created a replacement for it using Rust and Apache Arrow.
Persistent Collection
-
I had a great experience with Scala and hopefully it will get more popular
So does Java! Also, kotlinx.collections is still not stable and I don't think they are intending to make it so any time soon.
-
What’s so great about functional programming anyway?
> If you are using containers, always, always, always use immutable containers from Google Guava unless you have an exceptionally good reason.
I actually prefer pcollections: https://github.com/hrldcpr/pcollections
AtomicReference + immutable data types is a really nice way to program in Java, and is basically the way most Clojure programs are written.
- Why Java's Records Are Better* Than Lombok's Data and Kotlin's Data Classes
-
Libraries, Frameworks and Technologies you would NOT recommend
You might consider persistent collections instead of immutable collections, I believe it is more optimized https://github.com/hrldcpr/pcollections
What are some alternatives?
Protobuf - Protocol Buffers - Google's data interchange format
Big Queue - A big, fast and persistent queue based on memory mapped file.
Apache Thrift - Apache Thrift
tape - A lightning fast, transactional, file-based FIFO for Android and Java.
Apache Avro - Apache Avro is a data serialization system.
SBE - Simple Binary Encoding (SBE) - High Performance Message Codec
Apache Orc - Apache ORC - the smallest, fastest columnar storage for Hadoop workloads
dexx - Persistent (immutable) collections for Java and Kotlin
Wire - gRPC and protocol buffers for Android, Kotlin, Swift and Java.