Natural Language API

Part of the GCP Processor package

Our processor family for GCP's Natural Language API leverages the API's ability to parse and categorize information from strings of text. Some features include identifying the sentiment of a sentence, pulling names and locations out of a phrase, and much more.

Common Properties

Common properties are properties that are shared between all Natural Language processors This means every Natural Language processor will include these properties, plus whatever additional properties the individual processors add.

Properties whose names are in bold and italic are required.

  • GCP Credentials Provider Service - A reusable provider controller service that stores GCP credentials. If this is not set, you will need to put in whatever relevant credentials information manually into their respective properties.

  • Project ID - the ID of the GCP project your services reside within

  • Number of Retries - the amount of times the processor can retry a failed request before failing the FlowFile

  • Proxy host - IP address or hostname of the proxy to be used

  • Proxy port - The proxy's port number

  • HTTP Proxy Username - The username for the proxy

  • HTTP Proxy Password - The password for the proxy

  • Proxy Configuration Service - A reusable controller service that packages the proxy information for multiple uses

  • Destination - A dropdown input that determines what part of the outgoing FlowFile will contain the output information. The value can be set to one of the following:

    • flowfile-body: the data will be put to the FlowFile body. Additionally, the FlowFile's mime.type property will be set to application/json

    • flowfile-attribute: the data will be put to an attribute, whose name depends on the processor. This name is listed on the processor's documentation page.

  • Data Access Location - Dropdown list that specifies what part of the FlowFile the data should be read from. The value can be set to one of the following

    • flowfile-body: the data will be taken from the body of the flowfile

    • flowfile-attribute: the data will be taken from the attribute specified in the Raw Data Attribute property

  • Raw Data Attribute - Specifies which FlowFile attribute to pull the raw data string from if the Data Access Location attribute is set to flowfile-attribute

Last updated