what is the status on ARM 32bit?
# community-help
s
what is the status on ARM 32bit?
k
We plan to publish 64 bit arm for the next release. No plans to support 32 bit arm yet.
s
okay
I compiled typesense for arm 32 bit
but I am unable to get search results
I am getting document by id curl "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"}
k
Maybe try running the binary via valgrind to see if any errors are flagged for searching.
s
but search is getting blocked after collection->search in do_search
I placed a log right at the start of Collection::search function....but that log is not printing...
k
What branch are using?
s
default
master
also I had to modify main.cpp to get it compiled diff --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),
any comment on this? 👀
k
Try using
v0.23
branch. That's where I added a bunch of ARM related changes to get it compile for ARM 64.
s
okay...I'll try
k
I think it should work from that branch. I was able to compile on AWS Graviton instance and run it fine.
s
ohk...I'll try