Extra new line shows up in the Import API response, which affects JSONL parsing in client libraries about typesense HOT 10 CLOSED

I’ve been getting this exact issue on our self hosted cluster as well! We’re on 0.25.2, currently with three nodes in our cluster.

works well locally with ”same” data, single node. But close to everytime gives the json parse error when trying to import prod data from MongoDB to typesense.

Really nice to see a solution/explanation to this! Thanks to everyone involved! 🙏🏼

cant wait for final 0.26.0 now! 😎

thank you for an absolutely awesome piece of software!

from typesense.

We do have users using 0.26.0.rc49 in production, so should be safe to use it.

Latest version of typesense-js is also compatible with it.

from typesense.

We're at least 3-4 weeks out. We don't have a fixed release schedule, since we want to make sure we give enough time for users to give us feedback and iron out any issues before a GA release.

from typesense.

@jasonbosco You guys are awesome!

from typesense.

@ffager83 The patch for this is already in 0.26.0.rc49.

You should see this version when you go to Cluster Configuration > Modify in Typesense Cloud.

from typesense.

@ffager83 The patch for this is already in 0.26.0.rc49.

You should see this version when you go to Cluster Configuration > Modify in Typesense Cloud.

Thanks for your quick reply and quick fix!

But as briefly mentioned before, we’re using a self hosted and self configured Typesense cluster. Running inside our exsisting AWS infra. So not using Typesense Cloud.

But yes, we could update to the newer version, shouldnt be an issue. 👍🏼

Still being marked as an RC, do you consider it being stable enough and production ready as compared to 0.25.2?
And also is the current node/javascript client compatible with it? (1.7.2 if I remember correctly)

I will take a closer look at the new version today and play around with it. 😎

from typesense.

Is there any planned date for the final release of v0.26.0?

from typesense.

Hey @jasonbosco any update on v26 ? I can try upgrading to 0.26.0.rc49 but I like to wait for the docs to come out 😅

from typesense.

We've expanded the scope of 0.26.0 a bit more, so we're still at least a month out unfortunately.

That said, 0.26.0.rc54 is stable and we have high traffic users using it successfully in production. So you can already start using that.

from typesense.

Released in v26

from typesense.