Algolia Search is a hosted full-text, numerical, and faceted search engine capable of delivering realtime results from the first keystroke. The Algolia Search API Client for Java lets you easily use the Algolia Search REST API from your Java code.
You can find the full reference on Algolia's website.
-
- Builder
- JSON & Jackson2
- Async & Future
If you're using Maven, add the following dependency to your pom.xml
file:
<dependency>
<groupId>com.algolia</groupId>
<artifactId>algoliasearch</artifactId>
<version>[2,]</version>
</dependency>
For the Async version use this:
<dependency>
<groupId>com.algolia</groupId>
<artifactId>algoliasearch-async</artifactId>
<version>[2,]</version>
</dependency>
On Google AppEngine use this:
<dependency>
<groupId>com.algolia</groupId>
<artifactId>algoliasearch-appengine</artifactId>
<version>[2,]</version>
</dependency>
In 30 seconds, this quick start tutorial will show you how to index and search objects.
You first need to initialize the client. For that you need your Application ID and API Key. You can find both of them on your Algolia account.
APIClient client = new ApacheAPIClientBuilder("YourApplicationID", "YourAPIKey").build();
For the Async version
AsyncAPIClient client = new AsyncHttpAPIClientBuilder("YourApplicationID", "YourAPIKey").build();
For Google AppEngine
APIClient client = new AppEngineAPIClientBuilder("YourApplicationID", "YourAPIKey").build();
Without any prior configuration, you can start indexing contacts in the contacts
index using the following code:
class Contact {
private String firstname;
private String lastname;
private int followers;
private String company;
//Getters/Setters ommitted
}
Index<Contact> index = client.initIndex("contacts", Contact.class);
index.addObject(new Contact()
.setFirstname("Jimmie")
.setLastname("Barninger")
.setFollowers(93)
.setCompany("California Paint"));
index.addObject(new JSONObject()
.setFirstname("Warren")
.setLastname("Speach")
.setFollowers(42)
.setCompany("Norwalk Crmc"));
If you prefer the async version:
AsyncIndex<Contact> index = client.initIndex("contacts", Contact.class);
index.addObject(new Contact()
.setFirstname("Jimmie")
.setLastname("Barninger")
.setFollowers(93)
.setCompany("California Paint"));
index.addObject(new JSONObject()
.setFirstname("Warren")
.setLastname("Speach")
.setFollowers(42)
.setCompany("Norwalk Crmc"));
You can now search for contacts using firstname, lastname, company, etc. (even with typos):
//Sync version
// search by firstname
System.out.println(index.search(new Query("jimmie")));
// search a firstname with typo
System.out.println(index.search(new Query("jimie")));
// search for a company
System.out.println(index.search(new Query("california paint")));
// search for a firstname & company
System.out.println(index.search(new Query("jimmie paint")));
//Async version
// search by firstname
System.out.println(index.search(new Query("jimmie")).get());
// search a firstname with typo
System.out.println(index.search(new Query("jimie")).get());
// search for a company
System.out.println(index.search(new Query("california paint")).get());
// search for a firstname & company
System.out.println(index.search(new Query("jimmie paint")).get());
Settings can be customized to tune the search behavior. For example, you can add a custom sort by number of followers to the already great built-in relevance:
//Sync & Async version
index.setSettings(new IndexSettings().setCustomRanking(Collections.singletonList("desc(followers)")));
You can also configure the list of attributes you want to index by order of importance (first = most important):
Note: Since the engine is designed to suggest results as you type, you'll generally search by prefix. In this case the order of attributes is very important to decide which hit is the best:
//Sync & Async version
index.setSettings(new IndexSettings().setSearchableAttributes(
Arrays.asList("lastname", "firstname", "company")
);
Note: If you are building a web application, you may be more interested in using our JavaScript client to perform queries.
It brings two benefits:
- Your users get a better response time by not going through your servers
- It will offload unnecessary tasks from your servers
<script src="https://cdn.jsdelivr.net/algoliasearch/3/algoliasearch.min.js"></script>
<script>
var client = algoliasearch('ApplicationID', 'apiKey');
var index = client.initIndex('indexName');
// perform query "jim"
index.search('jim', searchCallback);
// the last optional argument can be used to add search parameters
index.search(
'jim', {
hitsPerPage: 5,
facets: '*',
maxValuesPerFacet: 10
},
searchCallback
);
function searchCallback(err, content) {
if (err) {
console.error(err);
return;
}
console.log(content);
}
</script>
The v2 of the api client, uses a builder to create the APIClient object. If you are on a regular JVM (not android, not Google App Engine), use the ApacheAPIClientBuilder
, if you are on Google App Engine use the AppEngineAPIClientBuilder
. If you fancy Future
, use the AsyncHttpAPIClientBuilder
.
As for Android, please use the Android API Client
JSON & Jackson2
All the serialization/deserialization is done with Jackson2. You can add your custom ObjectMapper with the method setObjectMapper
of the builder.
Changing it might result in unexpected result. You can find the one used in the interface com.algolia.search.Defaults.DEFAULT_OBJECT_MAPPER
.
All methods of the AsyncAPIClient
are exactly the same as the APIClient
but returns CompletableFuture<?>
. All other classes are prefixes with Async
. You can also pass a optional ExecutorService
to the build
of the AsyncHttpAPIClientBuilder
.
- Need help? Ask a question to the Algolia Community or on Stack Overflow.
- Found a bug? You can open a GitHub issue.