LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Delta_V

Having an issue with the default viewer in BRE 4.6. When I right-click on any output and I select "Data Viewers(All) -> default" the default brd viewer doesn't initialize. However, it does work if I select the "View Data" option. At first I thought it was just me but another BRE user on my team was reporting the same issue.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: stonysmith

How many records are in the file? If it's many millions of records, then the file can take quite some time to appear on the screen.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Delta_V

I've tried it on as few 18 records and it still doesn't work. However, let me clarify my original post because when I go to view all, the brdviewer does open up with the same columns as the source data but the columns themselves do not contain any data. I've attached a screenshot of what I'm seeing.

BRE_Example.jpg

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Tim Meagher

Hi,

This issue appears to occur when connecting to a remote server (i.e. not while using the Lavastorm Desktop) and when using the "Data Viewers(All) -> default" option on the node.
In this case, the data viewer opens correctly, but does not display the data on the node.
This has been raised as issue# 4845 in our bug tracking system.

Tim.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Delta_V

Hi Tim, our group just upgraded to 4.6.1 BRE and server but we're still seeing the issue with the view all records. I checked the release notes and didn't see anything about the issue being resolved in 4.6.1 so I didn't know if this was something server side we needed to change or if we just needed to wait. The records come thru fine for view all if we use an external data viewer like Excel, it just doesn't seem to work with the default viewer.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Tim Meagher

Hi,

This issue has not been resolved in LAE 4.6.1, but will be addressed in an upcoming release.
I will post here when this is released.

Regards,
Tim.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: aop

Currently there is also a problem with the viewer when selecting data viewers->default. When the code page is changed in the viewer it always loads the whole data isntead of the number of lines defined in settings under viewer max records. This happens at least with the Lavvastrom Desktop. Any info about this?

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Tim Meagher

Hi,

Is the problem the following?:
If you set the Tools->Preferences "Viewer Max Records" preference on the General tab to some value less than the total amount of data on a nodes input/output, then choose to view the input/output via right click->Data Viewers->Default, then it will display correctly in the BRD Viewer with the restricted number of records.
However, if in the BRD Viewer, you choose Preferences->Set Codepages, and modify the codepage, then the entire data is loaded into the BRD Viewer.
Upon closing the BRD viewer, any subsequent attempt to view the records in the viewer using the same right click->Data Viewers->Default mechanism will again correctly display the limited number of rows specified in "Viewer Max Records"

If so, this issue is already raised in our bug tracking system as issue #4755.

Bear in mind that the codepage in the BRD Viewer should generally be set to the same as the character set of the server - which should always be set to the same character set as that specified in BRE, therefore this value should rarely change and the problem should only exhibit at the time when this value is changed in the BRD Viewer.

Regards,
Tim.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: aop

Yes that's exactly the issue.

We change the codepage via the viewer (I've never changed the setting of the server and don't even know how) on every day between utf-8 and windows-1252 depending on the input data format. I think I haven't really understood the way BRE handles character sets. Are we doing something wrong here. Should we convert all utf-8 data to windows-1252 prior to taking them in to BRE?

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Tim Meagher

Hi,

Within the LAE, any field that is of type "string", and all metadata will be encoded in a single byte character set.
The character set to use can be specified via a server property ls.brain.server.characterSet.
This must be the actual name of the character set (e.g. windows-1252, not just "1252").
The property can be set in the ls_brain.prop file which can be found in your LAE server installation directory under conf/brain/ls_brain.prop.

It is the server property which governs how all nodes handle their string data along with the character set used for the metadata of all nodes.
The BRE preference is just used to tell BRE what the character set of the server is.
Since the character set is currently used for the string encoding, the metadata encoding, and the communication mechanism between BRE and the server, these must be the same value on BRE as on the server.
This BRE preference can be set under Tools->Preferences->Advanced->Server Code Page.
However, BRE only accepts windows code page numbers.

Therefore, if you set your server character set property to "windows-1251" for example, you would need to set your BRE "Server Code Page" preference to "1251".

The BRD Viewer preference, similarly just tells the BRD Viewer the code page that was used for the encoding of the metadata and the string data.
These can be in the same format as that of the server character set property.
The BRD Viewer has a separate value for the metadata and the string data type.
However, since the LAE will always currently produce BRD files with the string and metadata encoded in the same character set, these should always be the same value.
If running the BRD Viewer outside of BRE, this should be the same value as the character set of the server which produced the data.

For example, when using windows-1251 as the character set, the BRE "Server Code Page" preference should be set to "1251" and the BRD Viewer preference would be set to "windows-1251, windows-1251".

Note that since this needs to be a single-byte character set, it isn't possible for the server to have a utf-8 etc character set specified.
This may not throw an error immediately, but as soon as you start using characters that have multiple bytes then you'll run into troubles.

For any multi-byte or unicode data, this needs to be in a field with "unicode" type.

While it is possible within the BRD Viewer to view "string" data in different character sets like utf-8, this doesn't really make much sense, since all of the nodes will be treating them as if they are in the character set of the server (which - again, must be single byte).

So when bringing unicode data into the LAE, it must be brought into a unicode field type.

FYI - I know that having three separate preferences to specify the same thing to different components is stupid, but that's just the way it is at the moment, and hopefully this will be tidied up at some stage in the near future.

Hope this clarifies things somewhat,

Tim.