PurviewGlossaries.ImportGlossaryTermsViaCsv Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Import Glossary Terms from local csv file.
public virtual Azure.Operation<BinaryData> ImportGlossaryTermsViaCsv (Azure.WaitUntil waitUntil, string glossaryGuid, Azure.Core.RequestContent content, bool? includeTermHierarchy = default, Azure.RequestContext context = default);
abstract member ImportGlossaryTermsViaCsv : Azure.WaitUntil * string * Azure.Core.RequestContent * Nullable<bool> * Azure.RequestContext -> Azure.Operation<BinaryData>
override this.ImportGlossaryTermsViaCsv : Azure.WaitUntil * string * Azure.Core.RequestContent * Nullable<bool> * Azure.RequestContext -> Azure.Operation<BinaryData>
Public Overridable Function ImportGlossaryTermsViaCsv (waitUntil As WaitUntil, glossaryGuid As String, content As RequestContent, Optional includeTermHierarchy As Nullable(Of Boolean) = Nothing, Optional context As RequestContext = Nothing) As Operation(Of BinaryData)
Parameters
- waitUntil
- WaitUntil
Completed if the method should wait to return until the long-running operation has completed on the service; Started if it should return after starting the operation. For more information on long-running operations, please see Azure.Core Long-Running Operation samples.
- glossaryGuid
- String
The globally unique identifier for glossary.
- content
- RequestContent
The content to send as the body of the request.
- context
- RequestContext
The request context, which can override default behaviors on the request on a per-call basis.
Returns
Exceptions
glossaryGuid
or content
is null.
glossaryGuid
is an empty string, and was expected to be non-empty.
Remarks
Schema for Response Body
:
{
id: string,
status: "NotStarted" | "Succeeded" | "Failed" | "Running",
createTime: string,
lastUpdateTime: string,
properties: {
importedTerms: string,
totalTermsDetected: string
},
error: {
errorCode: number,
errorMessage: string
}
}
Schema for Response Error
:
{
requestId: string,
errorCode: string,
errorMessage: string
}