Kustov query language
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgerYSFvf-MGSObf3Nlm9n2Xdp7bqJB0rDemPG6XKg9TAtcqEpZfqQkbtZVtKrj7X-_MGN1feN8GNAJ1q7MdNpdChUJ6JAciSSfUghpj7Lk0o3r-F_xdDsrpFmkdbrimqYA0Y7jwkjK0MF_PJ3PN5yqp6U8FyWgWffd50_QxQq7Nvl6XgUdBRqiAVut/s320/kusto%20query.png)
In this post I would be talking about my experiences of learning KQL (Kustov query language). I started with this document Kusto Query Language (KQL) overview | Kusto . From the documentation I get to know that it's a query language used for analytics purposes and uses up schema entities quite similar to SQL i.e., having database, tables, column. Then, document further talks about Kusto query which is basically a read only query for processing data. Types of querying: KQL supports 3 types of query statements. These are basically Let, Set, Tabular. Tabular: This is the most common way of querying. In this format a table is provided as an input and table is also taken up as output. Query consists of lot of operands which are connected by pipe (|). I know it's too much but let's take a look at a query and this would be crystal clear. In this query we can see StormEvents is provided as input and then there are lot of operands which are connected using pipe (|). These pip...