Repository: lens Updated Branches: refs/heads/master 9cdb9f9ae -> 406122776
LENS-744 : Fix server component documentation format Project: http://git-wip-us.apache.org/repos/asf/lens/repo Commit: http://git-wip-us.apache.org/repos/asf/lens/commit/40612277 Tree: http://git-wip-us.apache.org/repos/asf/lens/tree/40612277 Diff: http://git-wip-us.apache.org/repos/asf/lens/diff/40612277 Branch: refs/heads/master Commit: 406122776ed6539735a0bdac1b973227bd0c8615 Parents: 9cdb9f9 Author: Raju Bairishetti <[email protected]> Authored: Tue Aug 25 13:36:35 2015 +0530 Committer: Raju Bairishetti <[email protected]> Committed: Tue Aug 25 13:36:35 2015 +0530 ---------------------------------------------------------------------- src/site/apt/admin/server-components.apt | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/lens/blob/40612277/src/site/apt/admin/server-components.apt ---------------------------------------------------------------------- diff --git a/src/site/apt/admin/server-components.apt b/src/site/apt/admin/server-components.apt index 98c536c..b3f91bc 100644 --- a/src/site/apt/admin/server-components.apt +++ b/src/site/apt/admin/server-components.apt @@ -31,6 +31,7 @@ Lens server components * Lens services ** Session Management + All operations in Lens are performed in the context of a session. This would essentially be the first thing a client would need before any operation can be be performed in the lens system. Session management component facilitates creation, session specific configuration management, session resource management @@ -40,6 +41,7 @@ Lens server components the session. ** Schema Management + This component allows for cubes, fact tables, dimension tables and storages to be managed. While Storages can be managed only by the administrator, other objects can be managed directly by the lens users. Lens currently extends and uses Hive Metastore for managing lens objects. Lens server has to be configured appropriately to point @@ -48,12 +50,14 @@ Lens server components storage administration. ** Data Availability Management + Once schema is registered with Lens through the Schema management API, data can be made available in the form of partitions. The Lens data availability management (logical component) manages the partitions available for each fact and maintains an active timeline of data. This can be consulted by the query execution and managment components. Like the Schema management component, Lens currently uses the Hive metastore for data availability management as well. ** Query life cycle management + Servicing user queries over cubes, fact, dimension or native tables across different storages by choosing the best storage and execution engine is the most critical capability of the lens. Lens maintains state of queries submitted and tracks the progress through the system and also maintains a history of queries submitted and the its status. Unique query handle is issued to each @@ -61,16 +65,19 @@ Lens server components used for performing various analysis on the actual usage. ** Query schedule management (in progress) + Lens should allow for users to schedule their queries with some periodicity. This scheduling capability should allow users to express the time schedule. Additionally Lens server would apply gating criteria based on data availability. Also any throttling that needs to be effected would be considered before a scheduled query moves into running state. ** Metrics Registry + Lens today includes support for instrumenting various functions at a server level and at a query level through gauges and metrics. This can be used to understand the performance characteristics of the lens server and a single query. ** Pluggable query drivers + Lens server allows pluggable execution drivers for running queries. Available execution engines are Hive and JDBC. For configuring Hive as an execution engine, administrator should configure the HiveServer2 end point. More details on configuring multiple drivers will be covered in {{{./config-server.html} configuration guide}} - +
