Skip to content

Commit

Permalink
CI
Browse files Browse the repository at this point in the history
  • Loading branch information
VoicegainGithub authored and DrJJ committed Mar 4, 2024
1 parent 73051e0 commit 54716c3
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions voicegain_speech/api/meeting_api.py
Original file line number Diff line number Diff line change
Expand Up @@ -1340,7 +1340,7 @@ def asr_meeting_result_search_with_http_info(self, **kwargs): # noqa: E501
def asr_meeting_result_search_post(self, **kwargs): # noqa: E501
"""Advanced Search Meeting # noqa: E501
Search all Meeting Transcribe Sessions for a given Account - advanced version.</br> For pending sessions it will return progress information in the progress field.</br> By default only results from specified context are returned. This can be overridden by using `fromAllContexts` parameter.</br> The actual search query needs to be included in the body of the request (that is why this is a POST not a GET method).</br> The query is built as a tree, e.g., OR query to match any of two keywords can be represented like this: <pre> { \"type\" : \"OrQuery\", \"disjuncts\" : [ { \"type\" : \"EqTerm\", \"field\" : \"KEYWORD\", \"otherValue\" : \"java\" }, { \"type\" : \"EqTerm\", \"field\" : \"KEYWORD\", \"otherValue\" : \"python\" } ] } </pre> BTW, the same could be achieved using IN query: <pre> { \"type\" : \"InTerm\", \"field\" : \"KEYWORD\", \"otherValues\" : [\"java\", \"python\"] } </pre> Instead od relying on extracted Keywords, we can search for java or python using text query: <pre> { \"type\" : \"OrQuery\", \"disjuncts\" : [ { \"type\" : \"TxtSearchTerm\", \"field\" : \"TEXT\", \"txtQuery\" : \"java\" }, { \"type\" : \"TxtSearchTerm\", \"field\" : \"TEXT\", \"txtQuery\" : \"java\" } ] } </pre> This method supports [Pagination](#section/Pagination/Direct-pagination) # noqa: E501
Search all Meeting Transcribe Sessions for a given Account - advanced version.</br> For pending sessions it will return progress information in the progress field.</br> The actual search query needs to be included in the body of the request (that is why this is a POST not a GET method).</br> The query is built as a tree, e.g., OR query to match any of two keywords can be represented like this: <pre> { \"type\" : \"OrQuery\", \"disjuncts\" : [ { \"type\" : \"EqTerm\", \"field\" : \"KEYWORD\", \"otherValue\" : \"java\" }, { \"type\" : \"EqTerm\", \"field\" : \"KEYWORD\", \"otherValue\" : \"python\" } ] } </pre> BTW, the same could be achieved using IN query: <pre> { \"type\" : \"InTerm\", \"field\" : \"KEYWORD\", \"otherValues\" : [\"java\", \"python\"] } </pre> Instead od relying on extracted Keywords, we can search for java or python using text query: <pre> { \"type\" : \"OrQuery\", \"disjuncts\" : [ { \"type\" : \"TxtSearchTerm\", \"field\" : \"TEXT\", \"txtQuery\" : \"java\" }, { \"type\" : \"TxtSearchTerm\", \"field\" : \"TEXT\", \"txtQuery\" : \"java\" } ] } </pre> This method supports [Pagination](#section/Pagination/Direct-pagination) # noqa: E501
This method makes a synchronous HTTP request by default. To make an
asynchronous HTTP request, please pass async_req=True
>>> thread = api.asr_meeting_result_search_post(async_req=True)
Expand Down Expand Up @@ -1373,7 +1373,7 @@ def asr_meeting_result_search_post(self, **kwargs): # noqa: E501
def asr_meeting_result_search_post_with_http_info(self, **kwargs): # noqa: E501
"""Advanced Search Meeting # noqa: E501
Search all Meeting Transcribe Sessions for a given Account - advanced version.</br> For pending sessions it will return progress information in the progress field.</br> By default only results from specified context are returned. This can be overridden by using `fromAllContexts` parameter.</br> The actual search query needs to be included in the body of the request (that is why this is a POST not a GET method).</br> The query is built as a tree, e.g., OR query to match any of two keywords can be represented like this: <pre> { \"type\" : \"OrQuery\", \"disjuncts\" : [ { \"type\" : \"EqTerm\", \"field\" : \"KEYWORD\", \"otherValue\" : \"java\" }, { \"type\" : \"EqTerm\", \"field\" : \"KEYWORD\", \"otherValue\" : \"python\" } ] } </pre> BTW, the same could be achieved using IN query: <pre> { \"type\" : \"InTerm\", \"field\" : \"KEYWORD\", \"otherValues\" : [\"java\", \"python\"] } </pre> Instead od relying on extracted Keywords, we can search for java or python using text query: <pre> { \"type\" : \"OrQuery\", \"disjuncts\" : [ { \"type\" : \"TxtSearchTerm\", \"field\" : \"TEXT\", \"txtQuery\" : \"java\" }, { \"type\" : \"TxtSearchTerm\", \"field\" : \"TEXT\", \"txtQuery\" : \"java\" } ] } </pre> This method supports [Pagination](#section/Pagination/Direct-pagination) # noqa: E501
Search all Meeting Transcribe Sessions for a given Account - advanced version.</br> For pending sessions it will return progress information in the progress field.</br> The actual search query needs to be included in the body of the request (that is why this is a POST not a GET method).</br> The query is built as a tree, e.g., OR query to match any of two keywords can be represented like this: <pre> { \"type\" : \"OrQuery\", \"disjuncts\" : [ { \"type\" : \"EqTerm\", \"field\" : \"KEYWORD\", \"otherValue\" : \"java\" }, { \"type\" : \"EqTerm\", \"field\" : \"KEYWORD\", \"otherValue\" : \"python\" } ] } </pre> BTW, the same could be achieved using IN query: <pre> { \"type\" : \"InTerm\", \"field\" : \"KEYWORD\", \"otherValues\" : [\"java\", \"python\"] } </pre> Instead od relying on extracted Keywords, we can search for java or python using text query: <pre> { \"type\" : \"OrQuery\", \"disjuncts\" : [ { \"type\" : \"TxtSearchTerm\", \"field\" : \"TEXT\", \"txtQuery\" : \"java\" }, { \"type\" : \"TxtSearchTerm\", \"field\" : \"TEXT\", \"txtQuery\" : \"java\" } ] } </pre> This method supports [Pagination](#section/Pagination/Direct-pagination) # noqa: E501
This method makes a synchronous HTTP request by default. To make an
asynchronous HTTP request, please pass async_req=True
>>> thread = api.asr_meeting_result_search_post_with_http_info(async_req=True)
Expand Down

0 comments on commit 54716c3

Please sign in to comment.