The Red Hat Ecosystem Catalog is the official source for discovering and learning more about the Red Hat Ecosystem of both Red Hat and certified third-party products and services.
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.
By Altair Engineering Inc.
Graph Studio Unstructured solution has two main parts:
The Microservice Leader works in concert with the Graph Studio Agent and Graph Studio Unstructured to perform ingestion of unstructured data into RDF suitable for use in an Graph Studio Data Fabric. The Microservice Leader provides queuing and coordination functions for a cluster of Graph Studio Unstructured workers. Ingesting unstructured data with an Graph Studio Server requires the configuration and use of one or more Microservice Leader nodes.
The Graph Studio Unstructured Worker works in concert with the Microservice Leader and Graph Studio Agent to perform ingestion of unstructured data into RDF suitable for use in an Graph Studio Data Fabric. Graph Studio Unstructured supports extraction from plain text, HTML, PDF, Word, and Excel files, and creation of annotations based on regular expressions, a linked data knowledge base, or third-party annotators via a REST interface. Graph Studio Unstructured leverages Graph Studio's distributed microservice framework (via the Graph Studio Agent and Microservice Leader) to allow timely processing of large document sets. Use of Graph Studio Unstructured requires an appropriately licensed Graph Studio Server installation.
Project Status: stable
Operator Version: v1
When you deploy Graph Studio Unstructured using operator, following are the set of images used for actual deployments. We have given reference docker commands to download the latest releases for each of them below.
NOTE One needs to edit deploy/default_apps_v1_deployment_unstructured-operator.yaml, with right docker image details.
The following table lists the configurable parameters for Graph Studio Unstructured and their default values.(CR API Version: v1)
Parameter | Description | Default |
---|---|---|
metadata.name | Name of CR | au01 |
metadata.namespace | Namespace of CR | |
metadata.labels | Dictionary of (key: val) as labels of CR | |
spec.volumes | List of persistent volumes for Graph studio Unstructured | commented, please uncomment to add value |
spec.volumes.[i].name | Name for persistent volume | |
spec.volumes.[i].mountPath | Path where persistent volume should be mounted inside container | |
spec.volumes.[i].pv | Attributes to configure persistent volume, of type v1.PersistentVolume | |
spec.volumes.[i].pvc | Attributes to configure persistent volume claim, of type v1.PersistentVolumeClaim | |
spec.msLeader.nodeConfig.spec | Configuration specification for Graph studio Unstructured Leader pods | |
spec.msLeader.nodeConfig.spec.replicas | Number of pods for Graph studio Unstructured Leader | 1 |
spec.msLeader.nodeConfig.spec.serviceName | Name of headless service for Graph studio Unstructured | au--ms |
spec.msLeader.nodeConfig.spec.template.spec.serviceAccountName | Service account name for pods | unstructured-operator |
spec.msLeader.nodeConfig.spec.template.spec.containers.x.Name | Name of Graph stdio Unstructured Leader container | ms |
spec.msLeader.jvmMemory | Graph Studio Unstructured leader JVM memory | |
spec.msLeader.bootProperties | Graph Studio Unstructured leader specific boot properties | |
spec.auWorker.nodeConfig.spec | Configuration specification for Graph studio Unstructured Worker pods | |
spec.auWorker.nodeConfig.spec.replicas | Number of pods for Graph studio Unstructured Worker | 1 |
spec.auWorker.nodeConfig.spec.serviceName | Name of headless service for Graph studio Unstructured | au--w |
spec.auWorker.nodeConfig.spec.template.spec.serviceAccountName | Service account name for pods | unstructured-operator |
spec.auWorker.nodeConfig.spec.template.spec.containers.x.Name | Name of Graph studio Unstructured Worker container | w |
spec.auWorker.bootProperties | Graph studio Unstructured worker specific boot properties | |
spec.auWorker.jvmMemory | Graph studio Unstructured worker JVM memory | |
spec.bootProperties | Boot properties i.e. the environment variables for Graph studio Unstructured CR | commented, please uncomment to add value |
https://docs.cambridgesemantics.com/
The following information was extracted from the containerfile and other sources.
Summary | Graph Studio® Unstructured Operator, ubi9 Image |
Description | Graph Studio® Unstructured Operator lets a user deploy and manage life-cycle of Graph Studio® Unstructured via Graph Studio. |
Provider | Cambridge Semantics |
Maintainer | https://altair.com/customer-support |
The following information was extracted from the containerfile and other sources.
Repository name | Graph Studio® Unstructured Operator, ubi9 Image |
Image version | 3.1.3 |
Architecture | amd64 |
Use the following instructions to get images from a Red Hat container registry using registry service account tokens. You will need to create a registry service account to use prior to completing any of the following tasks.
First, you will need to add a reference to the appropriate secret and repository to your Kubernetes pod configuration via an imagePullSecrets field.
Then, use the following from the command line or from the OpenShift Dashboard GUI interface.
Use the following command(s) from a system with podman installed
Use the following command(s) from a system with docker service installed and running
Use the following instructions to get images from a Red Hat container registry using your Red Hat login.
For best practices, it is recommended to use registry tokens when pulling content for OpenShift deployments.
Use the following command(s) from a system with podman installed
Use the following command(s) from a system with docker service installed and running