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

Connector: Typesense [Destination] #2004

Open
alarbada opened this issue Dec 10, 2024 · 1 comment
Open

Connector: Typesense [Destination] #2004

alarbada opened this issue Dec 10, 2024 · 1 comment
Assignees
@alarbada
Labels
connector:destination Request for a destination connector triage Needs to be triaged

Comments

@alarbada
Copy link

Resource name

Typesense

Resource link

https://typesense.org/

Connector type

Destination

Expected connector behavior

It should be able to write structured data.

We already have an elastic search connector, but typesense is a popular easy to use alternative. It has 21.4k github stars as of writing.
@alarbada alarbada added the triage Needs to be triaged label Dec 10, 2024
@alarbada alarbada self-assigned this Dec 10, 2024
This was referenced Dec 10, 2024
Open
Open
@hariso hariso removed this from Conduit Main Dec 11, 2024
@hariso hariso added the connector:destination Request for a destination connector label Dec 11, 2024
@hariso
Copy link
Contributor

hariso commented Dec 11, 2024

FYI I've added this (and other connector requests) to our internal connectors' project where we prioritize all connector requests. We'll let you know once we figure when we're going to work on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alarbada alarbada

Labels
connector:destination Request for a destination connector triage Needs to be triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hariso @alarbada