Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Amazon CloudSearch Document Service API support #134

Closed
jhnlsn opened this issue Jul 16, 2013 · 5 comments
Closed

Amazon CloudSearch Document Service API support #134

jhnlsn opened this issue Jul 16, 2013 · 5 comments
Labels
feature-request A feature should be added or improved.

Comments

@jhnlsn
Copy link

jhnlsn commented Jul 16, 2013

Any plans on adding support for documents/batch api in the SDK?
@jhnlsn jhnlsn closed this as completed Jul 16, 2013
@jhnlsn jhnlsn reopened this Jul 16, 2013
@lsegal
Copy link
Contributor

lsegal commented Jul 20, 2013

I'll mark this as a feature suggestion for supporting the document service portion of Amazon CloudSearch's API.

@techpines
Copy link

@lsegal +1

The main part of the Cloud Search API that a typical user would want to automate would be the document service portion. The other parts of the API aren't as important for automation. How often are you going to be updating indexes, creating domains etc.? The bulk of operations are going to be searches and updates to documents, neither of which are in the current API.

Cheers

@lsegal lsegal mentioned this issue Jan 14, 2014
Closed
@jaketrent
Copy link

+1 !

@lsegal lsegal mentioned this issue Feb 12, 2014
Closed
@lsegal lsegal closed this as completed in aa73f96 Jun 26, 2014
lsegal added a commit that referenced this issue Jun 26, 2014
@lsegal
Tag release v2.0.4
126656a 
References:
  #134, #297, #308, #310, #311
@lsegal
Copy link
Contributor

lsegal commented Jun 26, 2014

The above release should now have support for search/upload in the AWS.CloudSearchDomain service object.

@lock
Copy link

lock bot commented Sep 30, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked as resolved and limited conversation to collaborators Sep 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
feature-request A feature should be added or improved.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lsegal @jhnlsn @jaketrent @techpines