Official support to connect to MongoDB via JDBC

Hi Christian! Yes, this is indeed a universal need for connectors. Please vote and comment on the idea of having Spotfire Server connectivity for connectors here.

Hi Thomas,

the main point here is to support Mongo via JDBC (i.e. via Information Designer centrally from the Spotfire server) and not only via ODBC which always requires an installation on all client machines.

Best, Christian

MongoDB is supported when using the Spotfire Connector for MySQL in combination with the ODBC driver for MongoDB Connector for BI.

It's also supported when using the legacy Open from database functionality in combination with the ODBC driver from Simba which is shipped with the Spotfire Server.

It would be good to have this issue corrected in order to achieve full functionality.

Same requirement came from one of our customer from TSCE

We could finally solve the weird caching issues we had. In order to turn Mongo collections into a relational structure Spotfire automatically creates a mapping xml file in the tomcat folder on the Spotfire server once you have created a data source in Information Designer.

If you change something in the structure of your collection you need to follow these steps in order to be able to reflect it in Spotfire:

1. Delete the xml mapping file on the Spotfire server 
2. Create a table alias for the data source.  Once the table alias is expanded a new xml mapping file is created on the server and the alias will reflect the updated structure of the Mongo collection.
3. You can delete the table alias again
4. Refreshing the original data source in Information Designer will now also reflect the new structure
5. You can now go ahead and create new Column objects and update the Info Links according to the updated structure

It would be very beneficial if steps 1-3 would not be needed and if refreshing the data source in Information Designer would directly update the xml file on the sever.