Issues with ARM 32bit Typesense Compilation
TLDR sane had issues running Typesense on a 32bit ARM. Kishore Nallan proposed using the 'v0.23' branch with ARM modifications. sane agreed to try the solution.
Jan 26, 2022 (24 months ago)
sane
05:53 AM
Kishore Nallan
06:05 AMsane
06:23 AMsane
06:23 AMsane
06:23 AMsane
06:25 AMcurl "http://localhost:8108/collections/books/documents/0" -H "X-TYPESENSE-API-KEY: xyz" -v
* Trying 127.0.0.1:8108...
* Connected to localhost (127.0.0.1) port 8108 (#0)
> GET /collections/books/documents/0 HTTP/1.1
> Host: localhost:8108
> User-Agent: curl/7.81.1-DEV
> Accept: /
> X-TYPESENSE-API-KEY: xyz
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Connection: keep-alive
< content-type: application/json; charset=utf-8
< transfer-encoding: chunked
<
* Connection #0 to host localhost left intact
{"author":"Author1","id":"0","ratings":24,"title":"Book 1"}
Kishore Nallan
06:26 AMsane
06:26 AMsane
06:28 AMKishore Nallan
06:28 AMsane
06:28 AMsane
06:28 AMsane
06:30 AMdiff --git a/src/main/main.cpp b/src/main/main.cpp
index 34381be..91a6c98 100644
--- a/src/main/main.cpp
+++ b/src/main/main.cpp
@@ -19,10 +19,11 @@ int main(int argc, char* argv[]) {
system("rm -rf /tmp/typesense-data && mkdir -p /tmp/typesense-data");
Store *store = new Store(state_dir_path);
+ std::atomic<bool> quit;
CollectionManager & collectionManager = CollectionManager::get_instance();
- collectionManager.init(store, 4, "abcd");
- collectionManager.load();
+ collectionManager.init(store, 4, "abcd", quit);
+ //collectionManager.load();
std::vector<field> fields_to_index = {
field("lang", field_types::STRING, true),
sane
06:30 AMKishore Nallan
06:30 AMv0.23 branch. That's where I added a bunch of ARM related changes to get it compile for ARM 64.sane
06:31 AMKishore Nallan
06:31 AMsane
06:33 AM
Typesense
Indexed 3015 threads (79% resolved)
Similar Threads
Troubleshooting Typesense Connection Issue and Data Retrieval
Felix encountered issues connecting to a server-created typesense and retrieving data collections. Kishore Nallan and Jason provided guidance, highlighting errors in the original code and suggesting changes to the URL and curl command.
Issue Resolution and Upgrade Problems in Typesense Version 0.26rc16
Ankit reported an issue with Typesense, which was addressed by Kishore Nallan and Jason. However, Ankit experienced difficulties while trying to upgrade, with the server status showing as "Not ready or lagging" 503. The resolution remains incomplete.
Trouble with DocSearch Scraper and Pipenv Across Multiple OSs
James ran into errors when trying to build Typesense DocSearch Scraper from scratch, and believes itโs because of a bad Pipfile.lock. Jason attempted to replicate the error, and spent hours trying to isolate the issue but ultimately fixed the problem and copied his bash history for future reference. The conversation touches briefly on the subject of using a virtual machine for testing.
Troubleshooting 400 Error When Upgrading Typesense Firestore Extension
Orion experienced a `400` error after updating the Typesense Firestore extension, causing issues with cloud functions. They traced the issue back to a data type conflict in their Typesense collection schema after updating. With help from Jason and Kishore Nallan, they resolved the issue by recreating the collection.
ARM Support for Typesense on AWS Graviton Servers
Tatu inquires on ARM support for Typesense. Kishore Nallan informs it's on the roadmap with end of year completion. After some troubleshooting, they successfully test an ARM build, preparing it for the 0.23 release.