Power BI obviously can't query ElasticSearch directly.But, I managed to query data from Power BI Desktop in different ways:

DAX (Custom Qury), with Web.Contents.

ASP.NET Service (Web).

CData ElasitcSearch ODBC.We also have CData Power BI Connector, which is a custom conntector. Unfortentlly, DirectQuery with Custom Connectors still supported only with Power BI Desktop (nieghter in Power BI Server / Power BI Server, as far as I can see). Linkhere.

I'm trying to query 4 indices, which means basically 800GB. Of course that my initial query will try to filter the documents needed (not bringing all the documents) and the fields needed (not bringing all the fields in every matching document), so not all 800GB will be imported. It is very slow to query many documents, as each request only get 10,000 documents in single request (paging/scrolling is applied to get all matching documents). However, caching it though Power BI data-set which refreshes every day is fine - if it works (haven't tried it yet). I'm affraid this data set would be too big, so maybe i'll store a seperate data set for each weekly index and merge them later.

How complex is to import the data to some SQL Server / Service Analaysis? Remember it's JSON documents and some of them are very complex.

Power BI obviously can't query ElasticSearch directly.But, I managed to query data from Power BI Desktop in different ways:

DAX (Custom Qury), with Web.Contents.

ASP.NET Service (Web).

CData ElasitcSearch ODBC.We also have CData Power BI Connector, which is a custom conntector. Unfortentlly, DirectQuery with Custom Connectors still supported only with Power BI Desktop (nieghter in Power BI Server / Power BI Server, as far as I can see). Linkhere.

I'm trying to query 4 indices, which means basically 800GB. Of course that my initial query will try to filter the documents needed (not bringing all the documents) and the fields needed (not bringing all the fields in every matching document), so not all 800GB will be imported. It is very slow to query many documents, as each request only get 10,000 documents in single request (paging/scrolling is applied to get all matching documents). However, caching it though Power BI data-set which refreshes every day is fine - if it works (haven't tried it yet). I'm affraid this data set would be too big, so maybe i'll store a seperate data set for each weekly index and merge them later.

How complex is to import the data to some SQL Server / Service Analaysis? Remember it's JSON documents and some of them are very complex.

Power BI obviously can't query ElasticSearch directly.But, I managed to query data from Power BI Desktop in different ways:

DAX (Custom Qury), with Web.Contents (ElasticSearch REST API).

CData ElasitcSearch ODBC.We also have CData Power BI Connector, which is a custom conntector. Unfortentlly, DirectQuery with Custom Connectors still supported only with Power BI Desktop (nieghter in Power BI Server / Power BI Server, as far as I can see). Linkhere.

ASP.NET Service (Web).

I'm trying to query 4 indices, which means basically 800GB. Of course that my initial query will try to filter the documents needed (not bringing all the documents) and the fields needed (not bringing all the fields in every matching document), so not all 800GB will be imported. It is very slow to query many documents, as each request only get 10,000 documents in single request (paging/scrolling is applied to get all matching documents). However, caching it though Power BI data-set which refreshes every day is fine - if it works (haven't tried it yet). I'm affraid this data set would be too big, so maybe i'll store a seperate data set for each weekly index and merge them later.

How complex is to import the data from ElasticSearch to some SQL Server / Analysis Service? Remember it's JSON documents and some of them are very complex. Is it possible that SQL Server / Analysis Service make a DirectQuery for me (using the ElasticSearch ODBC)?