Prerequisites
To use Looker Studio with the Ocient System, you must have this software:- Ocient System — Use the latest version.
- A Google account with login credentials.
Connect to Ocient
Follow these steps to connect Looker Studio to your Ocient System.Open Looker Studio and start a data source.
- Go to https://lookerstudio.google.com/ and sign in.
- On the home page, select:
- Create > Data source, or
- From an open report, Resource > Manage added data sources > Add a data source.
Select the Ocient Community Connector.
- In the connector gallery, go to the Partner Connectors section.
- Find and select the Ocient DB connector.
Complete the configuration page by entering text in the fields. On the configuration page, select the Allow to be modified checkbox next to each field to modify it.This table contains descriptions for each field.
| Field | Description |
|---|---|
| Hostname | Hostname or IP address of the Ocient SQL Node. |
| Database | Database name in the Ocient System. |
| User | Ocient username. |
| Password | Password for the Ocient username. |
| Table | Ocient table name (schema.table). |
| Row Limit | LIMIT value to add to queries. |
| Date Range Column Name | Column name for the DATE or TIMESTAMP column in the WHERE clause. |
| Sort Column | Column name for the ORDER BY clause. |
| Sort Order | Sort order with the option of ASCENDING or DESCENDING. |
| Unnest Option | Specifies if array columns are unnested. |
| Custom Query | A query that overrides the query generated by the connector. The Looker data source panel shows only the columns included in this query. In this mode, Looker Studio infers column data types from the sample output, and not a DESCRIBE TABLE SQL statement. |
- Select Connect.
- Select Allow when Looker Studio prompts you with “Allow parameter sharing?.
Looker Studio uses autocomplete in its filter tool, which can impact date or time filtering for records older than 28 days.To fix this issue, navigate to the Looker filter control and set Show suggested values to
off.Ocient Data Types in Looker Studio
The connector represents Ocient data types using the closest approximation supported by Looker Studio. The inference of data types happens in Looker Studio in these ways:- In normal mode, the connector generates data types from the table schema produced by a
DESCRIBE TABLESQL statement. - In custom query mode, Looker Studio infers data types from sample output.
| Ocient Data Type | Looker Studio Data Type | Limitations |
|---|---|---|
| BOOLEAN | BOOLEAN | None |
| TINYINT, SMALLINT, INT, BIGINT, DOUBLE, FLOAT, DECIMAL | NUMBER | None |
| CHAR VARCHAR BINARY HASH IPV4 IP UUID VARBINARY TIME | TEXT | None |
| POINT LINESTRING POLYGON | TEXT | Looker Studio Community Connectors can use latitude or longitude coordinates, but they do not support native WKT geospatial types. |
| DATE | YEAR_MONTH_DAY | None |
| TIMESTAMP | YEAR_MONTH_DAY_SECOND | None |
| CHAR[], VARCHAR[], BINARY[], HASH[], IPV4[], IP[], UUID[], VARBINARY[], TUPLE[] | TEXT | Looker Studio does not support arrays or tuples as a native data type. The connector represents container data types as textual strings. For arrays, use the Unnest Option configuration field to flatten array columns for analytics. For tuples, use the Custom Query field to extract the tuple elements. Setting the Unnest Option field does not work for flattening tuples. |

