3 results found

1. Allow customer to stick with one minor OpenSearch version for an extended period

   As a DB admin
   I want to stick w a minor OS version until I have done all my testing with the new minor versions to make sure it does not break anything
   so that I can confidently upgrade my OS.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Pending Review  ·  0 comments  ·  Aiven for OpenSearch®  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Should have You must login first! Must have You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Support and/or adopt PGSync to help users maintain real-time sync between Postgres and Opensearch

   As an OpenSearch and Postgres user
   I want to easily keep these databases in sync
   so that I can provide low latency, high throughput full text search that doesn't impact my transactional database.

   Ever since search engines were invented, developers have struggled with keeping their system of records (typically relational databases like Oracle, Postgres, MySQL, etc) in sync with the search engine. Batch oriented processes are often not real-time enough resulting in poor user experiences where the search results don't return the same information as what's represented in the system of record. Event-oriented solutions such as writing updates from the app layer to Kafka which are then consumed by multiple databases can result in consistency issues and data stores becoming wildly out of sync, requiring a full re-index.

   PGSync could be a helpful tool to address this common challenge: https://pgsync.com/

   As an OpenSearch and Postgres user
   I want to easily keep these databases in sync
   so that I can provide low latency, high throughput full text search that doesn't impact my transactional database.

   Ever since search engines were invented, developers have struggled with keeping their system of records (typically relational databases like Oracle, Postgres, MySQL, etc) in sync with the search engine. Batch oriented processes are often not real-time enough resulting in poor user experiences where the search results don't return the same information as what's represented in the system of record. Event-oriented solutions such as writing updates from the… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Pending Review  ·  0 comments  ·  Aiven for OpenSearch®  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Should have You must login first! Must have You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Ability to change refresh interval for Index using Terraform

   As a DBRE
   I want to change the index refresh interval from a default value to some non-default value as a part of our latency optimization. With that, I would like this ability through IAC and control through our codebase.

   The idea here is to control this value from IAC and in more organized fashion.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Pending Review  ·  0 comments  ·  Aiven for OpenSearch®  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Should have You must login first! Must have You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close