app-search-kotlin

This is an open-source JVM client for Elastic App Search implemented in Kotlin.

Contents

• Getting started
• Dependencies
• Versioning and Compatibility with App Search
• Usage
• Implementation Considerations
• Missing Features
• Java Compatibility
• Issues and Contributions
• License

Getting Started

To install app-search-kotlin you can add it in your dependencies. Below you can see a Gradle example.

 implementation("com.github.itasyurt:app-search-kotlin:$app-search-version")

Dependencies

• Java 11
• Kotlin 1.3

Following Dependencies are used by app-search-kotlin and added in the classpath.

• Jackson
• Apache Http Client

Versioning and Compatibility

This client is developed and tested against App Search Version 7.8, but should be compatible with any 7.x version.

The suffixes like `alpha00X denote the internal versioning.

Usage

In the following sections you can see how client functionalities can be used. Formula 1 Drivers are used as the example domain in the code snippeys. You canrefer to the official API Reference for a complete documentation of the features.

Instantiating a Client

Documentation assumes tha Elastic App Search is up and running on http://localhost:3002. Following code segment shows how a client can be initialized

val client = DefaultClient(url = "http://localhost:3002", apiKey = "<your_key>")
 

DefaultClient is the default implementaion of the Client interface. Each API in App Search is considered as separate interfaces that can be accessed and called via the client. You can see the details on the APIs in the following sections.

Engines

Creating an Engine

client.engines.create(Engine("f1-drivers"))

Deleting an Engine

client.engines.delete("f1-drivers")

Getting an Engine

val engine= client.engines.get("f1-drivers")

Listing Engines

val enginesResponse = client.engines.list(Pagination(current = 1, size = 3))
enginesResponse.results.forEach(::println)

If you don't pass a pagination parameter, default pagination is current=1, size=20.

Documents

App Search Documents are considered as Map<String,Any> objects and referred by a typealias.

Creating and Patching Documents

val doc1 = mapOf(Pair("id","HAM"), Pair("name","Lewis Hamilton"))
val doc2 = mapOf(Pair("id","LEC"),Pair("name","Charles Leclerc"))
client.documents.create(engineName="f1-drivers", doc1, doc2)
val doc3 = mapOf(Pair("id","LEC"), Pair("dob",1997))
client.documents.patch(engineName="f1-drivers", doc3)

Note that documents are passed as varargs.

Getting and Listing Documents

val docs = client.documents.get(engineName = "f1-drivers", "HAM", "BOT", "VER")
docs.results.forEach(::println)

val docList = client.documents.list(engineName = "f1-drivers", Pagination(2,20))
docList.results.forEach(::println)

Deleting Documents

val deletionResult = client.documents.delete(engineName = "f1-drivers", "GRO")

Search

Creating a Search Request

Search requests be creating a SearchRequest object. Following components can be added in a search request:

• Query
• Pagination
• Grouping
• Facets
• Filters
• Boosts
• Search Fields
• Result Fields

Below you can see a sample search request, for the complete reference you can refer to official App Search Documentation.

val facets = mapOf(
    Pair("dob", listOf(RangeFacet(ranges = listOf(Range(from = null, to = 1990), Range(from = 1991))))),
    Pair("team", listOf(ValueFacet()))
)
val filters = CompositeFilter(
    all= listOf(
        ValueFilter("nationality",values = listOf("GB","DE")),
        RangeFilter("height", from = 168))
)


val request = SearchRequest(query = "Ferrari", facets = facets, filters = filters)

Performing a Search

Once you create a SearchRequest object, you can use the search client to perform a search.

val req:SearchRequest = createSearchRequest() 
val searchResponse = client.search.search(engineName = "f1-drivers",searchRequest = req)
searchResponse.results.forEach(::println)
searchResponse.facets?.forEach(::println)

SearchResponse consists of results and facets that you can iterate on along with the metadata information.

Performing a Multi-Search

Multiple search requests can be passed to a multisearch request as a list. Response is a list of SearchResponse objects.

val response = client.search.multisearch(engineName = "f1-drivers", listOf(req1, req2))
response.forEach {println(it.results)}

Search Settings

Search Settings is formed by following components:

• Search Fields
• Result Fields
• Boosts

You can see composition of an example SearchSettings object below. Please refer to the official documentation for the comprehensive set of settings.

val fields = mapOf(
    Pair("name", SearchWeight(10)),
    Pair("team", SearchWeight(2)),
    Pair("bio", SearchWeight(0.2))
)

val resultFields = mapOf(
    Pair("name", ResultField()),
    Pair("bio", ResultField(snippet = Snippet(100)))
)
val boosts = mapOf(Pair("name", listOf(ValueBoost(value = listOf("Hamilton")))))
val settings = SearchSettings(searchFields = fields, resultFields = resultFields, boosts = boosts)

Client enables create/reset and get operations on SearchSettings as follows:

client.searchSettings.update(engineName = "f1-drivers", settings=settings)
client.searchSettings.reset(engineName = "f1-drivers")
val retrieved = client.searchSettings.get(engineName = "f1-drivers")

Schemas

Client enables programmatic management of Engine Schemas. Schemas are designed as a Map<String, FieldType> . Key is the field name whereas the value is an enum that refers to the App Search Field Types namely:

• Text
• Number
• Date
• Geolocation

In the sample code below you can see how schemas are managed.

// Create
val schema = Schema(
    fields = mapOf(
        Pair("name", FieldType.TEXT),
        Pair("dob", FieldType.DATE)
    )
)
client.schemas.update(engineName = "f1-drivers", schema)
val schema2 = client.schemas.get(engineName = "f1-drivers")
schema2.fields.forEach { println("${it.key} ${it.value}")}

Synonyms

Client facilitates CRUD operations on Synonym Sets as you can see in the example code below:

// Create
val synonymSet= client.synonyms.create(engineName = "f1-drivers", listOf("ferrari","tifosi"))
// Update
client.synonyms.update(engineName = "f1-drivers",synonymSet.id, listOf("ferrari","horse", "tifosi"))
// Get
val retrievedSynonyms = client.synonyms.get(engineName = "f1-drivers", synonymSet.id)
// Delete
client.synonyms.delete(engineName = "f1-drivers", synonymSet.id)
// List(with optional pagination)
val synonymSets= client.synonyms.list(engineName = "f1-drivers")
synonymSets.results.forEach(::println)

Curations

Client facilitates CRUD operations on Curations as you can see in the example code below:

// Create
val curation = Curation(queries = listOf("champion"), promoted = listOf("HAM"), hidden = listOf("RAI"))
val curId = client.curations.create(engineName = "f1-drivers", curation)

// Update
val curation2 = Curation(queries = listOf("champion"), promoted = listOf("HAM"))
client.curations.update(engineName = "f1-drivers", curationId = curId, curation=curation2)

// Get
val retrievedCuration = client.curations.get(engineName = "f1-drivers", curId)
// List(with optional pagination)
val curations = client.curations.list(engineName = "f1-drivers")
// Delete
val deleted = client.curations.delete(engineName = "f1-drivers", curId)

Suggestions

Client facilitates search suggestion passing a query prefix along with field names. You can see an example below:

val sug = client.suggestions.suggest(engineName = "f1-drivers", SuggestionsRequest(query = "fer", fields = listOf("team", "name")))
sug.suggestions.forEach(::println)

Implementation Considerations

• Domain objects are modeled based on the API reference using Jackson annotations as much as possible.
• Optional parameters are either considered nullable or default arguments (such as pagination).
• Meta Information is considered as a generic Map<String,Any>.

Missing Features

Following features are missing in the current implementation.

• HTTPS connection
• API Logs API
• LogSettings API
• Analytics API
• Clicks API
• Credentials API
• Meta Engines API

Java Compatibility

app-search-kotlin is functionally compliant with Java (11). However the implementation does not take Java Interoperability as the primary concern. For example, default arguments are not provided for Java Clients. A builder or wrapper can be added in the upcoming versions to ensure convenience for Java clients.

Issues and Contributions

• You can use the Issues Tab to report issues/ feature requests.
• For contribution, feel free to create a PR.

License

Apache 2.0