iReport Ultimate Guide - Nimsoft Library
iReport Ultimate Guide - Nimsoft Library iReport Ultimate Guide - Nimsoft Library
iReport Ultimate GuideFigure 11-31 Spring-based Hibernate connectionNow that a Hibernate connection is available, use an HQL query to select the data to print. You can use HQL in the same waythat you use SQL: open the Report query dialog box and choose HQL as the query language from the combo box at the top ofthe window (see Figure 11-32).200
Data Sources and Query ExecutersFigure 11-32 The HQL and the HQL mapping toolWhen you enter an HQL query, iReport tries to retrieve the available fields. According to the UR documentation,the field mappings are resolved as follows:• If the query returns one object per row, a field mapping can be one of the following:• If the object’s type is a Hibernate entity or component type, the field mappings are resolved as the property names ofthe entity/component. If a select alias is present, it can be used to map a field to the whole entity/component object.• Otherwise, the object type is considered scalar, and only one field can be mapped to its value.• If the query returns a tuple (object array) per row, a field mapping can be one of the following:• A select alias. The field will be mapped to the value corresponding to the alias.• A property name prefixed by a select alias and a “.”. The field will be mapped to the value of the property for theobject corresponding to the alias. The type corresponding to the select alias has to be an entity or component.If you don’t understand this field mapping information, simply accept the fields listed by iReport when the query isparsed.iReport provides a mapping tool to map objects and attributes to report fields. The objects (or JavaBeans) available in eachrecord are listed in the combo box on top of the object tree.To add a field from the tree, select the corresponding node and click the Add selected field(s) button.11.6.10 Using a Hadoop Hive ConnectionUR provides a way to use Hive in your reports. Unlike traditional databases, Hadoop systems support huge amountsof data, generally called big data. But this capability has a cost: high latency with access times between 30 seconds and 2minutes.Because of the latency, reports based on Hadoop-Hive data sources are best suited to be run in the background or tobe scheduled. For example, the report could be run at 6 a.m. and the HTML or PDF could be exported and stored foranyone wanting to access the report during the day.201
- Page 149 and 150: TemplatesFigure 9-12Preview of repo
- Page 151 and 152: SubreportsCHAPTER 10 SUBREPORTSSubr
- Page 153 and 154: SubreportsFigure 10-3Subreport elem
- Page 155 and 156: SubreportsFigure 10-4Subreport Para
- Page 157 and 158: SubreportsFigure 10-7Just a list of
- Page 159 and 160: SubreportsFigure 10-11 Subreport Wi
- Page 161 and 162: SubreportsFigure 10-14 The final re
- Page 163 and 164: Subreports3. Click the Add button t
- Page 165 and 166: Subreports10.4 Using the Subreport
- Page 167 and 168: SubreportsFigure 10-21 Subreport co
- Page 169 and 170: SubreportsFigure 10-23 Setting Subr
- Page 171 and 172: Data Sources and Query ExecutersCHA
- Page 173 and 174: Data Sources and Query Executers•
- Page 175 and 176: Data Sources and Query ExecutersFig
- Page 177 and 178: Data Sources and Query ExecutersFig
- Page 179 and 180: Data Sources and Query ExecutersFig
- Page 181 and 182: Data Sources and Query ExecutersFig
- Page 183 and 184: Data Sources and Query ExecutersFig
- Page 185 and 186: Data Sources and Query ExecutersFig
- Page 187 and 188: Data Sources and Query Executers•
- Page 189 and 190: Data Sources and Query ExecutersAft
- Page 191 and 192: Data Sources and Query ExecutersIns
- Page 193 and 194: Data Sources and Query Executerspub
- Page 195 and 196: Data Sources and Query ExecutersFig
- Page 197 and 198: Data Sources and Query ExecutersFig
- Page 199: Data Sources and Query Executersbe
- Page 203 and 204: Data Sources and Query ExecutersWhe
- Page 205 and 206: Data Sources and Query ExecutersCod
- Page 207 and 208: Data Sources and Query ExecutersPre
- Page 209 and 210: Data Sources and Query ExecutersFig
- Page 211 and 212: Data Sources and Query Executersspe
- Page 213 and 214: Data Sources and Query Executers•
- Page 215 and 216: Data Sources and Query Executersof
- Page 217 and 218: Data Sources and Query ExecutersThi
- Page 219 and 220: Data Sources and Query ExecutersCod
- Page 221 and 222: Data Sources and Query ExecutersIf
- Page 223 and 224: ChartsCHAPTER 12 CHARTSUR provides
- Page 225 and 226: ChartsFigure 12-3Chart selection wi
- Page 227 and 228: ChartsFigure 12-6Dataset configurat
- Page 229 and 230: settings). These four fields have t
- Page 231 and 232: ChartsFigure 12-10 Chart Theme Desi
- Page 233 and 234: ChartsFigure 12-12 Example chart th
- Page 235 and 236: Run your report. iReport should dis
- Page 237 and 238: Charts1. First create a report.Figu
- Page 239 and 240: Charts4. Right-click on the chart a
- Page 241 and 242: Flash ChartsCHAPTER 13 FLASH CHARTS
- Page 243 and 244: Flash ChartsThe layout properties f
- Page 245 and 246: Flash ChartsThe following figure sh
- Page 247 and 248: Flash ChartsTable 13-2Entity IDs of
- Page 249 and 250: Flash ChartsTable 13-3Entity expres
<strong>iReport</strong> <strong>Ultimate</strong> <strong>Guide</strong>Figure 11-31 Spring-based Hibernate connectionNow that a Hibernate connection is available, use an HQL query to select the data to print. You can use HQL in the same waythat you use SQL: open the Report query dialog box and choose HQL as the query language from the combo box at the top ofthe window (see Figure 11-32).200