Product Selector

Fusion 5.12
    Fusion 5.12

    Kaltura V2Connector Configuration Reference

    The Kaltura V2 connector uses the Kaltura Java API client to retrieve data stored in Kaltura.

    The v1.4.0 version of this connector is only compatible with Fusion 5.9.4 and later when using security trimming. The v1.4.0 connector version uses Graph Security Trimming and not regular security trimming. It is imperative to treat this as a new connector, as configurations do not transfer over due to disparities between newer versions and previous ones. A full crawl is mandatory.

    Setup

    To set up the Kaltura connector, you’ll need to retrieve your User ID, User Secret, and Partner ID which can be found in the Kaltura Management Console.

    Document field list

    This section provides the list of fields in the document, and the source endpoint for each field.

    Field Source endpoint

    conversionQuality

    createdAt

    creditUrl

    creditUserName

    dataUrl

    description

    duration

    flavorParamsIds

    id

    isTrimDisabled

    mediaDate

    mediaType

    msDuration

    name

    objectType

    rank

    searchProviderId

    searchProviderType

    searchTex

    sourceType

    sourceVersion

    streams

    tags

    thumbnailUrl

    totalRank

    updatedAt

    userId

    votes

    /api_v3/service/media/action/get

    category_id

    category_name

    category_fullName

    category_owner

    /api_v3/service/category/action/get

    metadata

    /api_v3/service/metadata_metadata/action/get

    Remote connectors

    V2 connectors support running remotely in Fusion versions 5.7.1 and later. Refer to Configure Remote V2 Connectors.

    Below is an example configuration showing how to specify the file system to index under the connector-plugins entry in your values.yaml file:

    additionalVolumes:
- name: fusion-data1-pvc
    persistentVolumeClaim:
    claimName: fusion-data1-pvc
- name: fusion-data2-pvc
    persistentVolumeClaim:
    claimName: fusion-data2-pvc
additionalVolumeMounts:
- name: fusion-data1-pvc
    mountPath: "/connector/data1"
- name: fusion-data2-pvc
    mountPath: "/connector/data2"

    You may also need to specify the user that is authorized to access the file system, as in this example:

    securityContext:
    fsGroup: 1002100000
    runAsUser: 1002100000

    Configuration

    When entering configuration values in the UI, use unescaped characters, such as \t for the tab character. When entering configuration values in the API, use escaped characters, such as \\t for the tab character.

    Kaltura connector

    properties - Properties

    Plugin specific properties.

    authenticationProperties - Authentication Settings

    endpoint - string

    Kaltura endpoint

    >= 1 characters

    Default: https://www.kaltura.com/

    userId - string

    User ID

    >= 1 characters

    userSecret - string

    Administrator Secret

    >= 1 characters

    partnerId - number

    Partner ID

    >= -2147483648

    <= 2147483647

    exclusiveMinimum: false

    exclusiveMaximum: false

    Multiple of: 1

    proxyProperties - Proxy Settings

    proxy - string

    Proxy

    proxyPort - number

    Proxy port

    >= -2147483648

    <= 2147483647

    exclusiveMinimum: false

    exclusiveMaximum: false

    Multiple of: 1

    applicationProperties - Application Settings

    filteredName - string

    Media name must contain this string to be indexed

    excludedIds - array[string]

    List of media ids that will not be indexed

    pageSize - number

    Number of objects fetched per request during item discovery

    >= 1

    <= 2147483647

    exclusiveMinimum: false

    exclusiveMaximum: false

    Default: 100

    Multiple of: 1

    security - Graph security filtering configuration

    enabled - boolean

    Enable query-time security-trimming

    Default: true

    id - stringrequired

    A unique identifier for this Configuration.

    >= 1 characters

    Match pattern: ^[a-zA-Z0-9_-]+$

    pipelineId - stringrequired

    Name of the IndexPipeline used for processing output.

    >= 1 characters

    Match pattern: ^[a-zA-Z0-9_-]+$

    parserId - string

    The Parser to use in the associated IndexPipeline.

    Match pattern: ^[a-zA-Z0-9_-]+$

    description - string

    Optional description

    <= 125 characters

    diagnosticLogging - boolean

    Enable diagnostic logging; disabled by default

    Default: false

    coreProperties - Core Properties

    Common behavior and performance settings.

    fetchSettings - Fetch Settings

    System level settings for controlling fetch behavior and performance.

    numFetchThreads - number

    Maximum number of fetch threads; defaults to 5. This setting controls the number of threads that call the Connectors fetch method. Higher values can, but not always, help with overall fetch performance.

    >= 1

    <= 500

    exclusiveMinimum: false

    exclusiveMaximum: false

    Default: 5

    Multiple of: 1

    indexingThreads - number

    Maximum number of indexing threads; defaults to 4. This setting controls the number of threads in the indexing service used for processing content documents emitted by this datasource. Higher values can sometimes help with overall fetch performance.

    >= 1

    <= 10

    exclusiveMinimum: false

    exclusiveMaximum: false

    Default: 4

    Multiple of: 1

    pluginInstances - number

    Maximum number of plugin instances for distributed fetching. Only specified number of plugin instances will do fetching. This is useful for distributing load between different instances.

    <= 500

    exclusiveMinimum: false

    exclusiveMaximum: false

    Default: 0

    Multiple of: 1

    fetchResponseScheduledTimeout - number

    The maximum amount of time for a response to be scheduled. The task will be canceled if this setting is exceeded.

    >= 1000

    <= 500000

    exclusiveMinimum: false

    exclusiveMaximum: false

    Default: 300000

    Multiple of: 1

    indexingInactivityTimeout - number

    The maximum amount of time to wait for indexing results (in seconds). If exceeded, the job will fail with an indexing inactivity timeout.

    >= 60

    <= 691200

    exclusiveMinimum: false

    exclusiveMaximum: false

    Default: 86400

    Multiple of: 1

    pluginInactivityTimeout - number

    The maximum amount of time to wait for plugin activity (in seconds). If exceeded, the job will fail with a plugin inactivity timeout.

    >= 60

    <= 691200

    exclusiveMinimum: false

    exclusiveMaximum: false

    Default: 600

    Multiple of: 1

    indexMetadata - boolean

    When enabled the metadata of skipped items will be indexed to the content collection.

    Default: false

    indexContentFields - boolean

    When enabled, content fields will be indexed to the crawl-db collection.

    Default: false

    asyncParsing - boolean

    When enabled, content will be indexed asynchronously.

    Default: false