Skip to content

Commit 83c5dc3

Browse files
committed
WIP
1 parent ad80d64 commit 83c5dc3

File tree

1 file changed

+9
-12
lines changed

1 file changed

+9
-12
lines changed

README.md

Lines changed: 9 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,21 @@
1-
21
> DISCLAIMER: This is a fork of [Airbnb's Chronon repo](github.com/airbnb/chronon) with the same Apache-2 license.
32
>
43
> ### What are the main differences?
54
> - Additional Connectors: BigQuery, Hudi, Glue, Iceberg, BigTable, Dynamo, Pub/Sub etc.
6-
> - Version upgrades to core libraries like spark, flink, thrift etc
5+
> - Version upgrades to core libraries like spark, flink, thrift etc.
76
> - Performance optimizations to backfill and serving.
8-
> - Compiler has a specialized gcp and aws runners, and compiles the whole repo
9-
> - Support for temporally accurate label attribution
7+
> - Compiler has specialized gcp and aws runners, and compiles the whole repo.
8+
> - Support for temporally accurate label attribution.
109
>
11-
> ### Why are we open-sourcing this?
12-
> We are opening up this repository, **NOT** to compete with the original repo, but to
13-
> - help out organizations that have asked us for the connectors we have built.
14-
> - make it easy for our customers to security review the binaries used by the zipline platform
10+
> ### Intended Use
11+
> This repository is built and deployed as part of the [Zipline](https://zipline.ai) platform.
12+
> It can also be used and self-hosted freely by anyone.
1513
>
16-
> ### Why not upstream it?
17-
> We have made changes to the kvstore interface and the thrift api - so upstreaming is not easy.
18-
> But you are more than welcome to pick changes from this repo and upstream them.
14+
> ### Relationship to Chronon
15+
> Updates to Chronon are picked and merged into this repo on a regular basis, and improvements made to this repository
16+
> can be merged upstream into the main repository.
1917
>
2018
> ### How to use it?
21-
> Unless you need any of the differing aspects mentioned above, you should use the original repo.
2219
> Docs are coming soon. If you want to use it before we get our docs in order, please reach out to us ([email protected]).
2320
2421
---

0 commit comments

Comments
 (0)