|Number of watchers on Github||257|
|Number of open issues||3|
|Average time to close an issue||7 months|
|Average time to merge a PR||28 days|
|Open pull requests||2+|
|Closed pull requests||2+|
|Last commit||over 2 years ago|
|Repo Created||about 6 years ago|
|Repo Last Updated||over 1 year ago|
|Organization / Author||netflix|
|Do you use aegisthus? Leave a review!|
|View open issues (3)|
|View aegisthus activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Trendy new open source projects in your inbox! View examples
Aegisthus has been transitioned to maintenance mode. It is still used for ETL at Netflix for Cassandra 2.x clusters, but it will not be evolving further.
A Bulk Data Pipeline out of Cassandra. Aegisthus implements a reader for the SSTable format and provides a map/reduce program to create a compacted snapshot of the data contained in a column family.
Aegisthus is built via Gradle (http://www.gradle.org). To build from the command line: ./gradlew build
Please see the wiki or checkout the scripts directory to use our sstable2json wrapper for individual sstables.
To run the included tests from the command line: ./gradlew build
Copyright 2013 Netflix, Inc.
Licensed under the Apache License, Version 2.0 (the
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
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.
This is a fairly major rewrite. The idea is that the mapper will output Columns rather than rows. This way we can sort them correctly into the reducer so that we can handle RangeTombstones.
This also gives us several other benefits. One is that we can just send the Cassandra Atoms across to the reducer, which keeps us from having to process Json while in flight, avoiding encoding/decoding problems that we had previously on characters that didn't serialize into json without escaping.
Because of this the final output is now an SSTable. It just makes the whole process of incremental processing easier because we only support one fileformat rather than SSTables and Json.
To get back to Json we will add a new serialization format when we deprecate the old way of processing files.