Federica Santillo

Hi team, When upgrading Spotfire Server from 14.0.0 to 14.0.5 the Server fails to start because the database version does not get updated as required. We have a deployment through Helm, so the upgrade is performed without running the upgradetool but directly changing the image version in the values.yaml. Any help? Here the error trace: Spotfire Server 14.0.5 LTS (Build Version: 74.5.15312.57819, Build Date: 2024-09-12, Build ID: 58b27d9, Database Schema Version: 494) 2024-11-27T12:54:59.398842307+04:00 Using log configuration file logging-debug.properties 2024-11-27T12:54:59.404392629+04:00 Using hostname: 172.22.206.230 2024-11-27T12:55:02.139358403+04:00 Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary. Error connecting to the specified data source: Trying to connect to a database with an incompatible version. 2024-11-27T12:56:05.373507011+04:00 The detected database schema version is: '493'. 2024-11-27T12:56:05.373517249+04:00 The required database schema version is: '494'. If I try to manually change the SN_VERSION inside the database from 493 to 494 the Server starts fine.

Hi David, the one for Couchbase seems similar to mine. My dataset is exactly as I posted it few comments ago and the issue happens only when I try to query "awards.award" (this one is a string in the db). It does not happen if I query all the others data. I added though the two lines for table-expression-pattern and procedure-expression-pattern but the outcome is still the same.

Hi David, I can only access Spotfire server log and I attach here the full file. The request that failed is at time 2024-11-12T10:38:18. server(6).log

@Olivier Keugue Tadaa This is the data source template <jdbc-type-settings> <type-name>MongoDB</type-name> <driver>mongodb.jdbc.MongoDriver</driver> <connection-url-pattern>jdbc:mongodb://&lt;host&gt;:&lt;port3307&gt;/&lt;database&gt;</connection-url-pattern> <supports-catalogs>false</supports-catalogs> <supports-schemas>false</supports-schemas> <supports-procedures>false</supports-procedures> <ping-command>db.runCommand({ping: 1})</ping-command> <column-name-pattern>$$name$$</column-name-pattern> <table-name-pattern>$$name$$</table-name-pattern> <schema-name-pattern>$$name$$</schema-name-pattern> <catalog-name-pattern>$$name$$</catalog-name-pattern> <procedure-name-pattern>$$name$$</procedure-name-pattern> <column-alias-pattern>$$name$$</column-alias-pattern> </jdbc-type-settings> The drive used is the latest version of mongodb_unityjdbc_full.jar

Hi David, I'm using Spotfire 14.0.0. The problem seems to be due to a field in MongoDB that contains an array of objects: Spotfire is not able to retrieve it. For all the other fields the solution was just to flatter the data using a flattened aggregation query. For example, to retrieve the following data: db.testCollection.find() [ { _id: 1, name: { first: 'John', last: 'Backus' } } ] The query should be something like this: SELECT _id, name.first, name.last FROM testCollection; But for field with the following structure it seems that there's no way to handle it in Spotfire (or I haven't found it yet): db.testCollection.find() [ { name: { first: 'John', last: 'Backus' }, awards: [ { award: 'W.W. McDowell Award', year: 1967, by: 'IEEE Computer Society' }, { award: 'National Medal of Science', year: 1975, by: 'National Science Foundation' }, { award: 'Turing Award', year: 1977, by: 'ACM' }, { award: 'Draper Prize', year: 1993, by: 'National Academy of Engineering' } ] } ]

Hi David, thank you for your reply. I created the data source template through the Configuration Tool, following this old post form the community https://community.spotfire.com/forums/topic/1586-connecting-spotfire-to-mongo-via-jdbc-and-info-links/. After deleting and creating again the data source xml I managed to finally see the table structure, but even if in the Information Designer I can fetch the columns names, when trying to execute the query Spotfire see the content as one unique json and returns the following error: InformationModelServiceException at Spotfire.Dxp.Services: Failed to execute query: Unsupported JDBC data type in query result: hashmap/JSON (HRESULT: 80131509)

Hi team, I managed to connect from Spotfire 14.0.0 to MongoDB through Information Designer, by created a custom data source template. I can see the collection I have in Mongo but I cannot fetch its columns and the data inside. The data source validation shows that everything is ok, but when I try to create the default information model I get the following error: Error message: An issue occurred while creating the default model. It may be partially constructed. The <unknown element> has some invalid content. InformationModelException at Spotfire.Dxp.Data: Error(s) found during validation. (HRESULT: 80131500) Stack Trace: at Spotfire.Dxp.Data.InformationModel.InternalInformationModelManager.AddElement(InformationModelElement element, Boolean ignoreWarnings) at Spotfire.Dxp.Data.InformationModel.InternalInformationModelManager.TryAddElementWithNameResolution(String suggestedName, ElementProducer elementProducer, Boolean ignoreWarnings, NameConflictStrategy conflictStrategy, InformationModelElement& createdElement) at Spotfire.Dxp.Data.InformationModel.DataSourceITable.CreateDefaultModelCore(LibraryItem saveFolder, Set`1 extraItemPaths, InternalLibraryManager libraryManager, InternalInformationModelManager internalInformationModelManager, LibraryItemMetadataSettings settings, Dictionary`2 properties, NameConflictStrategy conflictStrategy) at Spotfire.Dxp.Data.InformationModel.DataSourceItem.<>c_DisplayClass55_0.<CreateDefaultModel>b_0() at Spotfire.Dxp.Framework.ApplicationModel.Progress.ExecuteSubtask(String title, ProgressOperation operation) at Spotfire.Dxp.Data.InformationModel.DataSourceItem.CreateDefaultModel(LibraryItem saveFolder, Set`1 extraItemPaths, InternalLibraryManager libraryManager, InternalInformationModelManager internalInformationModelManager, LibraryItemMetadataSettings settings, Dictionary`2 properties, NameConflictStrategy conflictStrategy) at Spotfire.Dxp.Data.InformationModel.InternalInformationModelManager.CreateDefaultModel(LibraryItem saveFolder, IEnumerable`1 dataSources, IEnumerable`1 dataSourceItems, LibraryItemMetadataSettings settings, NameConflictStrategy conflictStrategy) at Spotfire.Dxp.Forms.Data.InformationDesigner.DesignerForm.<>c_DisplayClass73_0.<CreateDefaultModel>b_0() at Spotfire.Dxp.Framework.ApplicationModel.Progress.<>c_DisplayClass22_0.<Start>b_0() at Spotfire.Dxp.Framework.ApplicationModel.MonitorableProgress.Start[T](Func`1 action) at Spotfire.Dxp.Forms.Application.FormsProgressService.ProgressThread.<DoOperationLoop>b__11_0() InformationModelServiceException at Spotfire.Dxp.Services: Error(s) found during validation. (HRESULT: 80131509) Stack Trace: at Spotfire.Dxp.Services.WcfSoapService`2.InvokeService[T](Func`1 serviceMethod, String customMethodNameForLogging) at Spotfire.Dxp.Data.InformationModel.InternalInformationModelManager.AddElement(InformationModelElement element, Boolean ignoreWarnings)

Thank you Olivier!

Hi Olivier, Yes I confirm that we have the certificate stored in a volume. That's why we were not expecting to "lose" it during the upgrade. Correct, I am not able to find the jdk folder in the installation directory (see the img attached).

Hi @Olivier Keugue Tadaa, Thank you for your reply. Yes I already opened a support ticket (#02306223). The problem when I try to reinstall the certificate is that I m not able to find any jdk folder in the installation dir to run the keytool command as required by the official doc https://docs.tibco.com/pub/spotfire_server/14.0.0/doc/html/TIB_sfire_server_tsas_admin_help/server/topics/installing_ca_certificates.html.

Hi, We have Spotfire deployed on a K8s cluster (on-prem solution) and customer is asking for any official document for a rolling update strategy.

Hello team, After upgrading from 12 to 14 we are experiencing issues with LDAP authentication and users are no longer able to login. When we attempt to connect to LDAP from the Spotfire configuration tool we get the following message: We already checked with the LDAP team that the LDAP URL is correct and the service is listening on port 636, so we tried a curl command to the LDAP server from the spotfire server pod and it seems to have issues with the certificate even though in the /tomcat/certs folder I can see that the certificate is imported as jks: Any idea on how to solve this? Thank you