Profiler - known issues

Support questions related to CloverETL Data Profiler, a data profiling application for the CloverETL family.

jurban
Posts: 162
Joined: Fri Jul 20, 2007 9:25 am

Profiler - known issues

Postby jurban » Mon Oct 24, 2011 12:46 pm

Dear CloverETL Profiler users,

this topic describes known issues of CloverETL Profiler, especially during the beta testing phase.

Thank you for understanding,

Your CloverETL Profiler team.
Jaroslav Urban
CloverCARE Support
CloverETL | Rapid Data Integration

Visit us online at http://www.cloveretl.com

jurban
Posts: 162
Joined: Fri Jul 20, 2007 9:25 am

Re: Known issues

Postby jurban » Mon Oct 24, 2011 1:10 pm

Export to XML on Mac

platform: OSX
affected version: 0.9.0-beta1

On Mac, clicking on the "Export to XML" button in the Reporting Console does not ask to save the XML to a file, but the browser tries to display the XML itself. However it does not show the contents of the XML, just a blank page.

Workaround: the above behavior occurs only in the browser that is internal to the CloverETL Profiler. So to export the XML, open the Reporting Console in a new browser window via an action in the toolbar, please see attached screenshot. In the external browser window, the XML is saved to a file correctly.
Attachments
open external browser.png
open external browser.png (31.6 KiB) Viewed 4072 times
Jaroslav Urban
CloverCARE Support
CloverETL | Rapid Data Integration

Visit us online at http://www.cloveretl.com

jurban
Posts: 162
Joined: Fri Jul 20, 2007 9:25 am

Re: Known issues

Postby jurban » Mon Oct 24, 2011 2:50 pm

Internal browser in some Linux distributions

The internal browser used on Linux needs XUL Runner (please see installation instructions). However, some Linux distributions provide only a too new version of XUL Runner (>=2.0). If you're encountering issues with the internal browser, please make sure you have a supported version installed (1.9.X at most). In case you have multiple versions installed you can point CloverETL Profiler to the correct installation by adding "-Dorg.eclipse.swt.browser.XULRunnerPath=/path/to/xulrunner" (with the correct path for your system) to profiler.ini file.
Jaroslav Urban
CloverCARE Support
CloverETL | Rapid Data Integration

Visit us online at http://www.cloveretl.com

jurban
Posts: 162
Joined: Fri Jul 20, 2007 9:25 am

Re: Profiler - known issues

Postby jurban » Wed Oct 26, 2011 1:58 pm

Processing data sources with large number of fields(columns)

When processing data sources with many fields or columns (e.g. 200 and more), you might encounter the following error when running a job:

Code: Select all

Exception in thread "main" java.lang.OutOfMemoryError: Direct buffer memory


To overcome this, please increase the available memory for the profiling job via the run configuration of the job (accessed via the Profiler > Run Configurations menu, see attached screenshots). For example, 250 fields usually require around 600MB of memory.
Attachments
run configuration memory size.png
run configuration memory size.png (61.19 KiB) Viewed 4042 times
run configuration menu.png
run configuration menu.png (44.88 KiB) Viewed 4042 times
Jaroslav Urban
CloverCARE Support
CloverETL | Rapid Data Integration

Visit us online at http://www.cloveretl.com

jurban
Posts: 162
Joined: Fri Jul 20, 2007 9:25 am

Re: Profiler - known issues

Postby jurban » Wed Nov 30, 2011 4:55 pm

UPDATE: Processing data sources with large number of fields(columns)

The issue described in the previous post will be very rare in the upcoming beta 2 of CloverETL Profiler. The new version profiles data with a much more compact CloverETL graph. The only situation when the issue will occur is if you enable time consuming metrics (median, modus or unique count) on a very high number of fields (e.g. 200).
Jaroslav Urban
CloverCARE Support
CloverETL | Rapid Data Integration

Visit us online at http://www.cloveretl.com