c3f4d48dfa
Add XML documentation, and fix an issue in EquiJoin code generation |
||
---|---|---|
Documentation | ||
Sources | ||
.gitignore | ||
LICENSE | ||
README.md | ||
azure-pipelines.yml |
README.md
Introduction
Trill is a high-performance one-pass in-memory streaming analytics engine from Microsoft Research. It can handle both real-time and offline data, and is based on a temporal data and query model. Trill can be used as a streaming engine, a lightweight in-memory relational engine, and as a progressive query processor (for early query results on partial data).
Getting Started
Building Trill
- Of course, the sources are right here!
- Clone the Repo and make sure you have Visual Studio 2017 installed
- Open
Trill.sln
solution available in./Sources
with Visual Studio 2017 - Build Trill
Samples using Trill
If you don't want to compile Trill yourself, you can get binaries from our NuGet feed. Samples of Trill usage are available at our samples repository. Make sure you start from the Hello World sample to get confident with Trill.
Learn More
- Announcement blog post.
- The Trill paper appeared at VLDB.
- An article on Trill appeared in the IEEE Data Engineering Bulletin.
- The Trill technical report.
- Additional documents located in the /Documentation directory
Contact/Feedback
You can create Git issues in this repo, or contact the team using this email.
Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.