Skip to Main Content
Spotfire Ideas Portal
ADD A NEW IDEA

Data Access

Showing 480 of 4332

Abort queries in data connections

Sometimes you realized the query you sent off is taking too long and/or was wrong. In that case you want to be able to abort the query to avoid data source overload. This is possible with information link based queries (there is a cancel button) b...
almost 5 years ago in Spotfire / Data Access 3 Future Consideration

Connector to Elasticsearch

Hello, Is a connector to ElasticStack planned in TIBCO Spotfire roadmap? To my mind, it could be interesting to connect Spotfire to Elastic. Thanks in advance. Best regards.
over 7 years ago in Spotfire / Data Access 5 Future Consideration

Support impersonation in Data Connections via WebPlayer

As per case 02092109 we understand that what is no problem with Data Connections + fat client, Information Links + fat client and Information Links + WebPlayer, is not supported for Data Connections + WebPlayer. If the solution to https://ideas.ti...
over 2 years ago in Spotfire / Data Access 0 Future Consideration

Be able to use Custom Connectors on Spotfire Cloud

One of the most powerful features of Spotfire are the connectors. Custom Connectors are not available for Tibco Cloud users so they can't use this functionality. Custom connectors should be installable for Tibco Cloud users
3 months ago in Spotfire / Data Access 0 Future Consideration

Add CLOB data type to Spotfire's supported data types

Ensuring future extensibility: CLOB is a common data type, and supporting it will enable your product to address a wider variety of use cases. More efficient data processing: Support for CLOB data types makes it easier to perform complex string op...
3 months ago in Spotfire / Data Access 0 Future Consideration

Support of SQL Complex Data Types (ARRAY, MAP, STRUCT)

In our databases (Oracle, Impala, ...) we use complex data types (ARRAYS, MAPS, STRUCTURES). Those data types are not supported today by Spotfire in-db connectors.
almost 8 years ago in Spotfire / Data Access 0 Future Consideration

Oracle databases with high number of schemas and tables, the loading time is very, very long and times out some time.

We have slow performance with some DB tools, which need long time to query Oracle data dictionary and that adding an Oracle hint /*+ RULE */ significantly speeded up e.g. SELECT /*+ RULE */ * from ALL_TAB_COLUMNS. Please provide the fix for this s...
over 2 years ago in Spotfire / Data Access 0 Future Consideration

Change default encoding to Unicode (UTF8) when replacing data table in Spotfire using Ironpython script

refer to the support ticket - 01862613 We have code in place which replaces data table based on dynamic parameter passing for multi clustered sql data. This works perfectly fine in english. But since because the encoding cannot be done before load...
over 4 years ago in Spotfire / Data Access 3 Future Consideration

Allow configuring user rights for information designer and data connections with identical right sets

Independet from whether data is accessed using information links or data connections a company would like to be able to control the user rights in an identical way. In our case we would like to be able to define three analyst levels where „setting...
almost 4 years ago in Spotfire / Data Access / Information Services 0 Future Consideration

Allow SQL queries to select columns based on Spotfire input

Certain data lake solutions are optimized for column access (e.g. Google's BigQuery). Trying to access a column in BQ using Spotfire fails because a string literal is the only option for the variable. If a second variable option was available that...
over 2 years ago in Spotfire / Data Access 0 Future Consideration