eyazan opened a new issue, #7308: URL: https://github.com/apache/hop/issues/7308
### What would you like to happen? Hello, We would like to request native OData connector support in Apache Hop. Many enterprise applications, especially SAP products and Microsoft-based systems, expose their data through OData services (OData V2 and V4). Currently, consuming OData data sources in Hop requires workarounds using generic REST calls, custom scripting, or intermediate layers. It would be very valuable to have a dedicated OData Input transform that could: Connect directly to OData endpoints. Support both OData V2 and OData V4. Automatically discover metadata from the $metadata endpoint. Browse and select available entity sets. Support authentication methods such as Basic Authentication, OAuth2, and Bearer Tokens. Handle pagination automatically. Support common OData query options: $select $filter $orderby $expand $top $skip Allow incremental loading based on date/time fields. Generate Hop metadata fields automatically from the OData schema. Before implementing such a feature, we would like to understand the recommended architecture within Apache Hop for consuming OData services. Would it be preferable to: Build a dedicated OData Input transform? Extend the existing REST Client capabilities? Create a generic framework for metadata-driven REST/OData integrations? We would appreciate feedback from the community on the best approach and whether there are already plans to support OData natively. Thank you for considering this feature request. ### Issue Priority Priority: 3 ### Issue Component Component: Hop Web -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
