Pentaho报告connectionFactory添加了新方法但没有描述
我正在我的网络应用程序中将我的 pentaho 报告从 3.6.1 升级到 3.8.0。当我更新所有必要的 jar 文件时，我的一个实现 ConnectionProvider 的类中出现了一个编译错误。下面是我的课。
public class DataSourceConnectionProvider implements ConnectionProvider
{
....
}
该错误表明我的类应该实现 getConnectionHash() 方法，因为它是在 ConnectionProvider 接口中定义的。但3.6.1版本中没有。所以我有点困惑他们为什么添加它以及如何在我的课堂上实现它。
I am in process of upgrading my pentaho reporting from 3.6.1 to 3.8.0 in my web application. when I updated all necessary jar files, I got one compilation error in one of my class which implements ConnectionProvider. following is my class.
public class DataSourceConnectionProvider implements ConnectionProvider
{
....
}
The error is saying that my class should implement getConnectionHash() method as it is defined in ConnectionProvider interface. but It was not there in 3.6.1 version. so I am bit confused why they have added it and how to implement it in my class.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
此方法返回一个可比较且可散列的对象，并在数据源缓存期间使用。它允许我们构建某种键来检测连接定义中的更改，同时许多报告在同一 JVM 中运行。
缓存实现本身不知道各种数据源的任何细节，“ConnectionHash”允许我们将结果集分开。
我的基本实现只是返回一个 ArrayList，其中添加了所有相关的连接属性。
简单的示例如何以及在哪里需要它：
假设您有一个连接到数据库的 JDBC 数据源，其中存在多个具有相同表结构的模式，例如在多租户环境中，每个租户都有自己的模式。
对于“SELECT * FROM CUSTOMERS WHERE COUNTRY = ${country-parameter}”这样的查询，数据源将根据执行查询的租户返回不同的数据集。 “连接哈希”、“查询名称”和“查询中使用的参数”的总和现在形成一个唯一标识符，我们可以使用它来存储并稍后从缓存中查找结果集。
This method returns a object that is comparable and hashable and is used during the caching of datasources. It allows us to build some sort of key to detect changes in the connection definition while many reports run within the same JVM.
The cache implementation itself does not know any of the details of the various datasources and the "ConnectionHash" allows us keep result-sets separate.
My basic implementation of it simply returns a ArrayList with all relevant connection properties added to it.
Simple example how and where it is needed:
Imagine you have a JDBC datasource that connects to a database where several schemas with the same table structures exists, for example in a multi-tenant environment where each tenant has his own schema.
With a query like "SELECT * FROM CUSTOMERS WHERE COUNTRY = ${country-parameter}" the datasource will return different datasets based on which tenant performs the query. The sum of "connection-hash", "query-name" and "parameter used in the query" now forms a unique identifier that we can use to store and later lookup the resultset from the cache.