react-odata
react-odata copied to clipboard
Batch Request for long filter queries
My filter query is getting too long in the url and throwing an error. How can I use batch processing in the current format? Are there other ways to get around?
Any examples would help.
Sorry I've not used batch processing (yet) and this do not have a work around. It's been on my list of items to look into but have not had time yet.
On Tue, Jan 2, 2018, 5:52 PM SNV [email protected] wrote:
My filter query is getting too long in the url and throwing an error. How can I use batch processing in the current format? Are there other ways to get around?
Any examples would help.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/techniq/react-odata/issues/1, or mute the thread https://github.com/notifications/unsubscribe-auth/AAK1RFvwV4N7ux-a0kBhiJRl4a46kt8Mks5tGrNHgaJpZM4RRK-k .
Thanks for a prompt response. I found couple of solution out of which atleast one worked:
- In the odata API I increased the maxQueryString="2097151" and that resolved the error.
- Another thing is there is a MaxNodeCount in odata which can be set in the configuration to allow long filters (I haven't tried it yet)
Hey! Is that still a case? :D
@TheAifam5 I'm afraid it is. I've also recently been using GraphQL recently so I'm not sure I'll be fixing this. Welcome to review a PR though.