> > Which caused some issues with the BI tool I'm using, Tableau. It would > show the table under tables, but when selected would throw an exception. > Removing the "TEMPORARY" appears to address that problem. > Hmm, can you provide the exception? We made some changes in 1.3 specifically to allow BI tools to see temporary tables, so I'd like to know if this is not working correctly.
> I do have one remaining concern. If one wants to reflect realtime > updates, using this approach, will they show up? I wold think I would need > to issue a "REFRESH TABLE tableName" when an update occurs; is that > correct? If I have a streaming job that is updating a set of tables, and > issues the REFRESH TABLE as the final step in the pipeline do you know if > the changes will be reflected in the referenced data by Tableau session? I > need to try that next, just thought you or someone on the forum may know > answer. > The cached metadata (and any refreshing that is done) is handled on a per SQLContext basis. So, if your streaming job is running on the same SQL context as your JDBC server then this would work. Otherwise you will need to call it manually from the context you are reading from. We could also consider adding an option to disable caching if you think that would be useful.
