diff --git a/.nojekyll b/.nojekyll new file mode 100644 index 0000000000..e69de29bb2 diff --git a/404.html b/404.html new file mode 100644 index 0000000000..82b5e64e5f --- /dev/null +++ b/404.html @@ -0,0 +1,1769 @@ + + + +
+ + + + + + + + + + + + + + + + + + +If this is your first contribution to open source, you can follow this tutorial or check this video series to learn about the contribution workflow with GitHub.
+We always have tickets labeled ‘good first issue’ and ‘help wanted’. These are a great starting point if you want to contribute. Don’t hesitate to ask questions in the Amundsen Slack channel about the issue if you are not sure about the strategy to follow.
+The easiest way you can contribute to Amundsen is by creating issues. First, search the issues section of the Amundsen repository in case a similar bug or feature request already exists. If you don’t find it, submit your bug, question, proposal or feature request. They will remain closed until sufficient interest, e.g. 👍 reactions, has been shown by the community.
+Before sending a pull request with significant changes, please use the issue tracker to discuss the potential improvements you want to make. This can help us send you to a solution, a workaround, or an RFC (request for comments item in our RFC repo).
+We have created a community roadmap where you can vote on plans for next releases. However, we are open to hearing your ideas for new features!
+For that, you can create an issue and select the “Feature Proposal” template. Fill in as much information as possible, and if you can, add responses to the following questions:
+To start contributing to Amundsen, you need to set up your machine to develop with the project. For that, we have prepared a developer guide that will guide you to set up your environment to develop locally with Amundsen.
+Once you have your environment set and ready to go, you can check our documentation and the project’s community roadmap to see what’s coming.
+ + + + + + + + + +The following diagram shows the overall architecture for Amundsen. +
+The frontend service serves as web UI portal for users interaction. +It is Flask-based web app which representation layer is built with React with Redux, Bootstrap, Webpack, and Babel.
+The search service proxy leverages Elasticsearch’s search functionality (or Apache Atlas’s search API, if that’s the backend you picked) and +provides a RESTful API to serve search requests from the frontend service. This API is documented and live explorable through OpenAPI aka “Swagger”. +Currently only table resources are indexed and searchable. +The search index is built with the databuilder elasticsearch publisher.
+The metadata service currently uses a Neo4j proxy to interact with Neo4j graph db and serves frontend service’s metadata. +The metadata is represented as a graph model: + +The above diagram shows how metadata is modeled in Amundsen.
+Amundsen provides a data ingestion library for building the metadata. At Lyft, we build the metadata once a day +using an Airflow DAG (examples).
+In addition to “real use” the databuilder is also employed as a handy tool to ingest some “pre-cooked” demo data used in the Quickstart guide. This allows you to have a supersmall sample of data to explore so many of the features in Amundsen are lit up without you even having to setup any connections to databases etc. to ingest real data.
+ + + + + + + + + +{"use strict";/*!
+ * escape-html
+ * Copyright(c) 2012-2013 TJ Holowaychuk
+ * Copyright(c) 2015 Andreas Lubbe
+ * Copyright(c) 2015 Tiancheng "Timothy" Gu
+ * MIT Licensed
+ */var Va=/["'&<>]/;qn.exports=za;function za(e){var t=""+e,r=Va.exec(t);if(!r)return t;var o,n="",i=0,a=0;for(i=r.index;i