-
Notifications
You must be signed in to change notification settings - Fork 1.6k
support for the no-metadata parameter in /exp #4629
Copy link
Copy link
Closed
Labels
BugIncorrect or unexpected behaviorIncorrect or unexpected behaviorGood first issueA great place to get familiar with the codebaseA great place to get familiar with the codebaseHelp wantedAssistance or additional information is wantedAssistance or additional information is wantedREST APIIssues or changes relating to the HTTP endpointsIssues or changes relating to the HTTP endpoints
Description
To reproduce
According to docs the REST interface accept nm parameter which says:
Skips the metadata section of the response when set to true.
However, it has no effect for me. I can see the parameter is set, but it's never read.
QuestDB version:
8.0.0
OS, in case of Docker specify Docker and the Host OS:
irrelevant
File System, in case of Docker specify Host File System:
irrelevant
Full Name:
Jaromir Hamala
Affiliation:
QuestDB
Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?
- Yes, I have
Additional context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
BugIncorrect or unexpected behaviorIncorrect or unexpected behaviorGood first issueA great place to get familiar with the codebaseA great place to get familiar with the codebaseHelp wantedAssistance or additional information is wantedAssistance or additional information is wantedREST APIIssues or changes relating to the HTTP endpointsIssues or changes relating to the HTTP endpoints