Hey all, is anyone else seeing import failing when...
# randomt
Todd Tarsi
05/18/2023, 3:14 PMHey all, is anyone else seeing import failing when it wasn’t prior? I’m not sure if we’ve made any changes, but we’re unable to import a single document for about a week now. I’ve raised a Github issue here to allow for reproduction and such, but I wasn’t sure if anyone else is encountering this:
https://github.com/typesense/typesense/issues/1025
k
Kishore Nallan
05/18/2023, 3:20 PMCan you please post a fully reproduceable JS snippet we can run? It should create a collection and try importing a sample document which produces the error.
t
Todd Tarsi
05/18/2023, 3:44 PM@Kishore Nallan - Thank you for the fast response wowie!
Reproduction script is uploaded to github. Should be runnable if you’ve got a basic typesense docker node on 8108 and the npm module for typesense.
Todd Tarsi
05/18/2023, 4:20 PMOkay, I’ve reduced down the schema. It’s booleans. Booleans appear to cause an issue in parsing. Is there some way I should format them from the API? Did I miss something?
Todd Tarsi
05/18/2023, 4:50 PM@Kishore Nallan - Hey, it turned out I just needed to explicitly declare the boolean in the schema. So uh, my bad I think. I will say we had an auto * type of field, so I thought this would be okay, but also this case turned out to be an easy fix.
k
Kishore Nallan
05/18/2023, 4:54 PMThanks for the details. But it still should not crash. We will look..
t
Todd Tarsi
05/18/2023, 5:25 PMMy mistake, fail not crash. Sorry for the run around you two.
👍 1
Todd Tarsi
05/18/2023, 5:27 PMAh! My schema had an invalid auto field, so it wasn’t picking it up. Made perfect sense, thank you so much @Kishore Nallan and @Jason Bosco!
👍 1