Skip navigation links
org.apache.druid.catalog.model.table

Class HttpInputSourceDefn

When the template is used, the format is optional: it can be provided either with the table spec or at runtime, depending on what the user wants to accomplish. In the above, where the ".json" is encoded in the template, it makes sense to include the format with the spec. If the template was "http://example.com/data/{}", and the data comes in multiple formats, it might make sense to specify the format in the query. In this case, the table spec acts more like a connection.

If the template is not used, then the uris property must be provided in the table spec, along with the corresponding format.

The above semantics make a bit more sense when we realize that the spec can also provide a user name and password. When those are provided, then the input source must name a single site: the one for which the credentials are valid. Given this, the only table spec that makes sense is one where the URI is defined: either as a template or explicitly.

When used as an ad-hoc function, the user specifies the uris and optional user name and password: the template is not available (or useful) in the ad-hoc case.

Table function parameters are cleaned up relative to the input source field names to make them a bit easier to use.

Skip navigation links

Copyright © 2011–2023 The Apache Software Foundation. All rights reserved.