2.0.1-rc2

• no changes

2.0.1-rc1

This attempts to address a major bug in the Zentity request handling, and also introduces some breaking changes around model names.

2.0.0

The first release of this FinTech Studios forks brings no (intended) breaking changes over the upstream's 1.6.1 release and adds some new features, namely bulk requests. It does add some new required permissions that must be accepted on installation.

Bulk Requests

The Resolution API now exposes two new endpoints, POST /_zentity/resolution/_bulk and POST /resolution/{entity_type}/_bulk for submitting multiple resolution jobs in a single request. They follow a similar newline delimited JSON (NDJSON) request body to the Elasticsearch Bulk API, with repeating pairs of metadata and body objects on separate lines. The new bulk endpoints accept all the same request query parameters as the non-bulk versions and optionally allow overriding on a per-job basis in the metadata object.

Ex:

// Mixed entity type requests
POST /_zentity/resolution/_bulk?_score
{ "entity_type": "organization" }
{ "terms": ["Appl"] }
{ "entity_type": "location" }
{ "terms": ["New York"] }
{ "entity_type": "person" }
{ "terms": ["Jane Doe"] }


// Single entity type, w/ param override for just first job
POST /_zentity/resolution/organization/_bulk?_score
{ "_explanation": true, /*..*/ }
{ "terms": ["Appl"] }
{}
{ "terms": ["New York Nets"] }
{}
{ "terms": ["Google Inc"] }

Other Features

Configuration File

Zentity can now be configured (though not set up) at installation time with custom configuration via a zentity.yml file in the standard ES_PATH_CONF directory.

The format is:

# Where zentity stores system information
index:
  name: string
  default_number_of_shards: number
  default_number_of_replicas: number

# Concurrency control for resolution requests
resolution:
  max_concurrent_jobs: number
  max_concurrent_jobs_per_request: number

Uninstallation/ Teardown Route

Similar to how Zentity can be set up through the POST /_zentity/_setup, the Zentity resources can now be removed through a DELETE /_zentity/_setup route. This is helpful when overriding the index name for an installation, so end-users don't have to know any Zentity internals to clean it up.

Deprecations

• The /_zentity route is now deprecated for all methods besides GET. Support for others will be removed in a future version.

2.0.0-rc3

🚀 Features

• refactor: use TreeSet and TreeMap vs HashSet and HashMap (#23): @austince

Other

2.0.0-rc2

🚀 Features

• feat(config): parameterize model index config (#19): @austince
• feat(setup): add a uninstall route (#21): @austince

📚 Docs

• docs(README): update download link (#18): @austince

🐛 Bugs

• fix(resolution): initialize jackson, minimize reflection, use privileges (#22): @austince

💻 CI

• ci: update changelog pr template (#17): @austince
• ci: add docker compose setup for local testing (#20): @austince

Other

2.0.0-rc1

🚀 Features

• feat: add bulk resolution support
  • PR: #4

💻 CI

• ci: ensure changelog config is present, add docs section
  • PR: #15

Other

• refactor: internal overhaul
  • PR: #2
• feat: upgrade es to require 7.7 >= <= 7.10, update test data
  • PR: #3
• feat(resolution): multi-entity-type bulk support
  • PR: #5
• ci: add release workflow, test on more versions of es
  • PR: #6
• ci: only release on tags, only create one release
  • PR: #7
• docs: expand CONTRIBUTING.md
  • PR: #8
• ci: use rc release nomenclature, add release guide
  • PR: #9
• ci: document tag format, correct copy location
  • PR: #10
• ci: fix asset path
  • PR: #11
• ci: store artifact name, properly extract ref
  • PR: #12
• ci: properly mark prereleases
  • PR: #13
• ci: add changelog builder config
  • PR: #14
• ci: fix changelog config json, remove duplicate es version
  • PR: #16

1.6.0

• no changes

1.6.0-rc9

• no changes

1.6.0-rc8

• no changes

1.6.0-rc10

• no changes