Monthly Downloads: 626
Programming language: Elixir
License: Apache License 2.0
Latest version: v0.13.2

panoramix alternatives and similar packages

Based on the "ORM and Datamapping" category.
Alternatively, view panoramix alternatives based on common mentions on social networks and blogs.

Do you think we are missing an alternative of panoramix or a related project?

Add another 'ORM and Datamapping' Package



Build Status

An open-source client library for sending requests to Apache Druid from applications written in Elixir. The project uses HTTPoison as an HTTP client for sending queries.

Getting Started

Add Panoramix as a dependency to your project.

defp deps do
    {:panoramix, ">= 0.12.0 and < 1.0.0"}


Panoramix requires a Druid Broker profile to be defined in the configuration of your application.

config :panoramix,
  request_timeout: 120_000,
  query_priority:  0,
  broker_profiles: [
    default: [
      base_url:       "https://druid-broker-host:9088",
      cacertfile:     "path/to/druid-certificate.crt",
      http_username:  "username",
      http_password:  "password"
  • request_timeout: Query timeout in millis to be used in [Context](context-druid-doc-link) of all Druid queries.
  • query_priority: Priority to be used in [Context](context-druid-doc-link) of all Druid queries.

The cacertfile option in the broker profile names a file that contains the CA certificate for the Druid broker. Alternatively you can specify the certificate as a string in PEM format (starting with -----BEGIN CERTIFICATE-----) in the cacert option.


Build a query like this:

use Panoramix

q = from "my_datasource",
      query_type: "timeseries",
      intervals: ["2019-03-01T00:00:00+00:00/2019-03-04T00:00:00+00:00"],
      granularity: :day,
      filter: dimensions.foo == "bar",
       aggregations: [event_count: count(), 
                      unique_id_count: hyperUnique(:user_unique)]  

And then send it:

Panoramix.post_query(q, :default)

Where :default is a configuration profile pointing to your Druid server.

The default value for the profile argument is :default, so if you only need a single configuration you can omit it:


Response example:

     "result" => %{
       "event_count" => 7544,
       "unique_id_count" => 43.18210933535
     "timestamp" => "2019-03-01T00:00:00.000Z"
     "result" => %{
       "event_count" => 1051,
       "unique_id_count" => 104.02052398847
     "timestamp" => "2019-03-02T00:00:00.000Z"
     "result" => %{
       "event_count" => 4591,
       "unique_id_count" => 79.19885795313
     "timestamp" => "2019-03-03T00:00:00.000Z"

You can also build a JSON query yourself by passing it as a map to post_query:

Panoramix.post_query(%{queryType: "timeBoundary", dataSource: "my_datasource"})


You can check correctness of your configuration by requesting status from Druid Broker. A successfull response will look like this.

iex(1)> Panoramix.status(:default)
   "memory" => %{...},
   "modules" => [...],
   "version" => "0.13.0"


We'd love to accept your contributions in a form of patches, bug reports and new features!

Before opening a pull request please make sure your changes pass all the tests.


Except as otherwise noted this software is licensed under the [Apache License, Version 2.0]((http://www.apache.org/licenses/LICENSE-2.0))

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at


Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

The code was Copyright 2018-2019 Game Analytics Limited and/or its affiliates.

*Note that all licence references and agreements mentioned in the panoramix README section above are relevant to that project's source code only.