Dear Hoppiasts, It was only a matter of time before someone asked about services on Hop Server. This week that time came and I implemented HOP-2577 <https://issues.apache.org/jira/browse/HOP-2577> which went much faster than I anticipated. It's just so easy to add more metadata and plug in new code. For those interested, the documentation is here <http://hop.apache.org/manual/latest/hop-server/web-service.html>.
What was uncovered was the need to add configuration details to the Hop Server. Up until now it's been designed to be doing just fine on its own. The metadata and variables the server needs it receives from clients like Hop GUI and Hop Run that want to run something on it. However, now that we're deploying stand-alond services on Hop Server we might want to consider optional configuration options. For now I added an option called metadata_folder which allows you to add metadata specifically for the "Web Service" service. I would love to come up with something more generic and with a wider user-case. Should we allow the server to cater for one specific environment (project) or multiples? Should we throw errors if a client runs a pipeline from project "A" on a server configured for project "B"? Too many questions so I would love your input. The thing is that it won't be long before someone asks about porting the JDBC driver to a pipeline and then we might as well have a more general answer. Cheers, Matt -- Neo4j Chief Solutions Architect *✉ *[email protected] ☎ +32486972937
