#contributions

Collaborative Efforts on Rust Client Library Project

TLDR Jason provided Emmanuel and Luis with architecture guidelines for a Rust client library project. The team decided to use Github issues for project coordination and discussed the API structure. Jason invited Emmanuel to collaborate on Github.

31mo

Join the chat

Apr 22, 2021 (31 months ago)

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

07:10 PM

Awesome! I just gave Luis a walk-through of the general client library architecture - he just started working on a Rust client library. Would you like me to go over the architecture as well?

Photo of md5-85c4e6451ddac65d7a51485602a216e9

Emmanuel

09:16 PM

Could I also help out with the Rust client lib?

Photo of md5-93d99be24f465be4955422e8502f4081

Luis

09:38 PM

Hi Emmanuel

09:40

Luis

09:40 PM

Feel free to read the general guidelines that Jason provided in this channel.

This is the project: https://github.com/typesense/typesense-rust

Let me know if you have any ideas in how we can manage this project, if using Github Issues or something else

Jason

09:47 PM

Hi Emmanuel! Thank you for offering to help. Here are the architecture guidelines: https://typesense-community.slack.com/archives/C01UZEXF5FY/p1619118820005000

Luis I'll defer to you on identifying how to best coordinate efforts

Apr 23, 2021 (31 months ago)

Emmanuel

04:07 AM

Hey Luis.

GitHub issues is fine by me.

I had a few questions:

Anything in mind for implementation, I mean is the entire library going to be async, or will we be exposing a sync blocking API as an option?

Are we aiming for a runtime agnostic async API or maybe a tokio dependent one?

Luis

04:13 AM

I was thinking in surf in order to be runtime agnostic. We can start async and then expose a sync API as you said

04:28

Luis

04:28 AM

What do you think? I created two issues in Github. You can work on them and/or create new ones . It is late here, I will continue later.

03:15

Luis

03:15 PM

Jason could you invite Emmanuel as collaborator in the Github project? The github user is emmanuelantony2000

Jason

03:15 PM

Yup, hang on

03:18

Jason

03:18 PM

Done. Emmanuel you need to accept the invite here: https://github.com/typesense/typesense-rust/invitations

Emmanuel

03:19 PM

Thanks

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2779 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Troubleshooting Issues with DocSearch Hits and Scraper Configuration

Rubai encountered issues with search result priorities and ellipsis. Jason helped debug the issue and suggested using different versions of typesense-docsearch.js, updating initialization parameters, and running the scraper on a Linux-based environment. The issues related to hits structure and scraper configuration were resolved.

131

6mo

Introduction and Coordination for Dart Client Team

Jason introduces Harisaran to Masahiro and Harpreet to work on the Dart client and suggests GitHub issue tracking. Masahiro shares a wiki page and advises creating an issue before a PR.

31mo

Troubleshooting Typesense Docsearch Scraper Setup Issue

Vinicius experienced issues setting up typesense-docsearch-scraper locally. Jason identified a misconfiguration with the Typesense server after checking the .env file, and recommended using ngrok or port forwarding for development purposes. Vinicius successfully resolved the issue with port forwarding.

3mo

Issue with Search Duration on Typesense Database

Robert reported an issue about query time delay when adding a `filter_by` constraint in a large Typesense database. Kishore Nallan explained that this happens due to the order of operation and also promised to look into this issue further. Robert withdrew his interest in sponsoring the improvement due to moving from the project.

8mo

Discussing Search API Limitations and Solutions

Sidharth had problems with search API response limitations and sorting issues. Kishore Nallan suggested multi_search query and provided links for an updated version. After installation, some timeout and performance issues were encountered, partially resolved by adjusting client timeout values.

12mo