ArangoDB

1

ArangoDB Java Drivers

6.13.0

Download - https://mvnrepository.com/artifact/com.arangodb/arangodb-java-driver/6.13.0

Note: Latest version is 6.14.0.

Community

3.x

Supported

Enterprise

3.x

Supported

Connection validate

SELECT.USAGE

Crawling

Select, Usage, Reference, and execution

Profiling

No permission 

Crawling

Databases

-

Collections

-

Collection Attributes

All data types in ArangoDB

Graphs

-

Views

-

Edge Collections

Collections Profiling

Row Count, Columns Count, View Sample data

-

Collections Attributes Profiling

Min, Max, Null Count, Distinct Count, Top 50 values

Full Profiling

Supported

-

Sample Profiling

Supported

-

Collection Lineage

Supported

Collection Attributes Lineage

Supported

Lineage Sources

Graphs, Views, Edge Collections

Connection Type

-

Select ArangoDB connector.

License Type

Mandatory

In a license type, the permissions are specified based on the customer's requirements. The user can select the license type as Standard or Auto Lineage.  

The connector license is categorized into

(i) Standard: The standard connectors have a Crawler Profiler feature and may not have Auto Lineage functionality. It will not build the lineage for the selected database.

(ii) Auto Lineage: Auto lineage connectors have Auto Lineage functionality in addition to the Crawling and Profiling feature. It will build the lineage for the selected database. See, License Types for more information. By default, the License type is displayed as ‘Auto Lineage’. 

Connection Name

Mandatory

Enter the name of the connection, the connection name specified in the Connection Name textbox will be a reference to the ArangoDB connector in the OvalEdge application.

Environment

The environment aims to help users understand that the new connection can be established to that configured environment (development, production, and QA). From the dropdown, select the desired environment such as Production, QA, and Prod. 

Server

Mandatory

This is the hostname of the ArangoDB server (TCP/IP server).  

Port

Mandatory

It is a TCP/IP port to use if the server is not a local host.  By default, port number 8529 related to the MySQL database is available. If needed, a new port number can be provided.

Username

Mandatory

This credential will authenticate the access of the database. By default, the username to authenticate the database is displayed. If required, users can manually enter the user credential to access the required database of MySQL connector.  

Password

The password is mandatory for users other than Root users.

Plug-in Server

Enter the server name if you are running this as a plugin.

Plug-in Port

Enter the Port number on which the plugin is running.

Default Governance Roles

The admin will select a specific user or a team from the governance roles (Steward, Custodian, Owner) that get assigned to the data asset.  The dropdown list displays all the configured users (single user or a team) as per the configurations made in the Security > Governance Roles page.  

No of Archive objects

It is the count of the number of last modifications made in the metadata data of a Remote/source. By default, the number of archive objects is set to disable mode. Click on the Archive toggle button and enter the number of objects you wish to archive.

For example, if you update the count as 4 in the ‘No. of archive object’ field, and then the connection is crawled. It will provide the last 4 changes that occurred in the remote/source of the connector. You can observe these changes in the ‘version’ column of the ‘Metadata Changes’ module. 

Select Bridge 

The bridge enables users to import schemas from physical databases using JDBC. The client workstation that runs the bridge must be configured with the correct parameter values.

The Bridge ID will be shown in the Bridge dropdown menu when bridges are configured and added, or it will be displayed as "NO BRIDGE". 

Tables, Views, and Columns

Select the checkbox to crawl the tables, views, and columns existing in the ArangoDB Connector into the OvalEdge.

Note: By default, the checkbox for Tables, Views, and Columns is selected.

Procedures, Functions, Triggers, Views Source Codes

Crawler Rules: Include Regex

Enter the specific schema, table, views, and column names that start with, end with, or have middle characters that are included for crawling.

Crawler Rules: Exclude Regex

Enter the specific schema, table, views, and column names that start with, end with, or have middle characters that are excluded for crawling.

Profiler Configurations Settings

Details

Tables and Columns

Select the checkbox to profile the tables and columns that exist in the ArangoDB Connector into the OvalEdge.

Note: By default, the checkbox for Tables and Columns is selected.

Views and Columns

Select the checkbox to profile the views and columns that exist in the ArangoDB Connector in the OvalEdge.

Note: By default, the checkbox for Views and Columns is selected.

columns

Description

Order

Order is the sequence in which the profiling is done. 

Day

Enter the day of the week profiling is set to run.

Start/End Time

Enter the start and end time at which profiling is set to perform.

Number of Threads

Thread is a process where a query is executed on a database to do single or multiple tasks. The number of threads determines the number of parallel queries executed on the data source. 

Profile Type

There are four main types of data profiling. 

• Sample Profiling runs the profile on a given sample size. The data on columns (like Min, Max, Distinct, Null Count, etc.) will be different compared to full profiles as we calculate them only on sample size. The sample profile is based on two main values. To execute a sample profile, select the profile type as “Sample” and enter a sample profile size(count of records to be profiled).

Row Count Constraint

If set to true, it enables the data rule profiling.

Row Count Limit

Enter the number of rows of data to be profiled. 

Sample Profile Size

Enter the total number of rows to be included in profiling.

Query Timeout

Enter the length of time in seconds to allow the query to run on a remote database before timing out.