You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
HTTP Storage Plugin OversizedAllocationException when field present in page 1 is absent in page 2 #2896
Describe the bug
When Apache Drill is configured with the HTTP storage plugin, and INDEX pagination mode is enabled, and the HTTP service configured with that plugin includes a field in all records from page 1, but that field is absent in page 2, a query that spans into page 2 results in an OversizedAllocationException.
Modify the Python3 HTTP server, commenting out line 46 and fixing indentation on line 47.
Restart the Python3 HTTP server and issue the query again from step 4.
Observe that now the error does not occur and result span into page 2.
Expected behavior
Drill is supposed to be resilient to flexible schemas with certain limitations. It should be reasonable for a field to be absent on some pages and present on others, or documentation should indicate the contrary. This would result in the response including the data from page 2 and not producing an exception. If this will not be supported the exception should indicate the issue with the result schema, not indicate that a buffer cannot be expanded.
Additional notes: Omitting the limit 15 clause results in the query succeeding (reading all pages). Adding an order by foo_id clause causes the query to fail in the same way as it failed with the limit 15 clause.
Activity
hyperbolix commentedon Mar 26, 2024
Additional notes: Omitting the
limit 15clause results in the query succeeding (reading all pages). Adding anorder by foo_idclause causes the query to fail in the same way as it failed with thelimit 15clause.cgivre commentedon Mar 27, 2024
Ok... this is really weird. This query only seems to fail if the limit is between 13 and 19. It works if the limit is 12 or 20-22.