Legacy Product

Fusion 5.10
    Fusion 5.10

    Kaltura V2 Connector Configuration Reference

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

    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.

    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

    description - string

    Optional description

    <= 125 characters

    pipeline - stringrequired

    Name of the IndexPipeline used for processing output.

    >= 1 characters

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

    diagnosticLogging - boolean

    Enable diagnostic logging; disabled by default

    Default: false

    parserId - string

    The Parser to use in the associated IndexPipeline.

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

    coreProperties - Core Properties

    Common behavior and performance settings.

    fetchSettings - Fetch Settings

    System level settings for controlling fetch behavior and performance.

    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

    indexContentFields - boolean

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

    Default: false

    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

    indexMetadata - boolean

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

    Default: false

    numFetchThreads - number

    Maximum number of fetch threads; defaults to 20.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: 20

    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 instanceswill do fetching. This is useful for distributing load between different instances.

    <= 500

    exclusiveMinimum: false

    exclusiveMaximum: false

    Default: 0

    Multiple of: 1

    id - stringrequired

    A unique identifier for this Configuration.

    >= 1 characters

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

    properties - Properties

    Plugin specific properties.

    authenticationProperties - Authentication

    endpoint - string

    Kaltura endpoint

    >= 1 characters

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

    userId - string

    User ID

    >= 1 characters

    userSecret - string

    User Secret

    >= 1 characters

    partnerId - number

    Partner ID

    >= -2147483648

    <= 2147483647

    exclusiveMinimum: false

    exclusiveMaximum: false

    Multiple of: 1

    proxyProperties - Proxy

    proxy - string

    Proxy

    proxyPort - number

    Proxy port

    >= -2147483648

    <= 2147483647

    exclusiveMinimum: false

    exclusiveMaximum: false

    Multiple of: 1

    applicationProperties - Application

    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 - Security filtering configuration

    enabled - boolean

    Enable query-time security-trimming

    Default: true

    collectionId - string

    Id of the collection to be used for storing ACL records. If not specified, ACL collection name will be generated automatically using pattern '<datasource_id>_access_control_hierarchy'.