on 01-31-2013 9:52 AM
Hi everyone,
I have created Attribute Views by joining two tables using text join and when I tried to change the default language(for example default language EN to DE) in the properties I could not find the option for changing .can anyone please help me in solving it.
Regards,
Hemanth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi again,
ok - one thing after the next.
In HANA Studio you can configure the locale to be used by right-clicking onto the system/logon-entry in the 'Navigator' -> [Properties] -> [Database User Logon] -> [Additional Properties].
Once you found your way to it the dialogue window should look somewhat like this:
Select the LOCALE entry you want to use and click on [OK].
After a reconnect the session context variable LOCALE should reflect the change.
BTW: the context variables are case-sensitive, therefore 'LOCALE' and 'locale' are different from each other.
As long as you're using HDB Studio it really doesn't help to manually set the LOCALE since this is a per connection setting and HANA Studio opens new connections all the time (e.g. for the data preview).
So the setting you've setup in one session won't be active in the other sessions.
- Lars
Hi all!
I already have the locale = 'S' in HANA studio, but when i open the CV with
Lumira, i recibe all the description characteristics, in another language, i tried to
configure the language in the Lumira's preferences pane, and i doesn't Work.
Finally i have to make an attribute view with a filter in the language for achieve the
requierement, but i want to know, why Lumira is not using the expected language.
Regards...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Widerman,
I am having an issue similar to the one you have reported: I have setup the HANA Studio with locale = 'S' and Predictive Analyisis with Spanish Language. When I retrieve information from an attribute view with language dependent texts, SAP HANA returns the English texts.
Having a look at the HANA session context I've realized the locale parameter is not set (It seems SAP Predictive Analyisis doesn't pass the locale parameter when connecting to SAP HANA):
Hey guys (i.e. , @Ravindra Channe - sorry Ravi, looks like tagging isn't working),
I'm sure I'm missing something obvious here, but not quite getting text join to work.
If I look at my system settings, English has already been set (defaulted) for locale:
When I check M_SESSION_CONTEXT though, it doesn't show up (and strangely enough, nothing here is showing up aside from PROTOCOL_VERSION, even though before I went to lunch, I was also seeing APPLICATION, APPLICATIONVERSION, etc...) :
(And to give the context of my test - I queried the base text table and see languages 'E' and 'S', but when I query the distinct SPRAS or description fields from the Analytic View, no results are returned).
I'd rather avoid hard-coded language filters (even though for now reporting will only be done in English), and it of course doesn't make sense to set session locale via SQL - it should be picked up dynamically from the client.
Suggestions on anything obvious that I'm missing?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
While this doesn't reply to your question, apparently LOCALE is not a supported (or at least, not documented) KEY vale anymore for this reference view.
http://help.sap.com/saphelp_hanaplatform/helpdata/en/20/c50b73751910148ae9d5b996ff1e84/content.htm
I'd recommend following up with a discussion thread.
Hey Jody,
what revisions are you using and which client do you use here?
As long as simply ENGLISH (no specific English version) is selected in SAP HANA Studio, then no locale setting is provided via the logon string.
Also no LOCALE/LOCALE_SAP variables are set in this case.
However, these variables simply override the default language, which is in turn English anyway.
In short: even when you don't see the variables, the text filter should work.
- Lars
Hi Thanks Lars I have changed the locale and it worked
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Hemanth,
I think it is an authorization issue. If you check properly, the first three rows are for system section, including the Locale information. Even I see only three rows with only one row for system.
One more suggestion, kindly mark Lars' replies as helpful. That is the way of saying thank you on this forum. He has shared very valuable information on this discussion thread.
Regards,
Ravi
Pretty sure that this is not about authorizations.
Question here would be: what versions of HANA Studio and Server are actually used?
Up to rev. 38 or so the locale wasn't visible via context variables.
This had been introduced rather recently.
Also: m_session_context really is always available - you basically can not have no authorizations on it .
- Lars
Hi thank for responding Lars,Ravindra can you please check it out the below screenshots
SP04:
In the previous version we had the option to change the default language, based on the default language the text used to be displayed
For Example if we change the default language to DE the text also used to display in German.
SP05:
In the latest version I could not find that option in the properties to change the Default Language.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
As Lars wonderfully explained, earlier, in SP 04 the setting was not completely dynamic, the way you mentioned. It was sort of hard coded when you select the language setting value.
Now you can check the locale as specified by Lars and check what value has been set for your session. You will have to change the locale for your session to change it to another language. The locale setting is mostly what is expected in the real life scenario and now can be achieved.
Regards,
Ravi
Hi Hemanth,
there is no way to change the "default" language for text joins in SPS 5.
The purpose of the text join is to support variable languages - if you need to have the language fixed to a specific value, you may simply create an outer join to the text table with a filter on the language column.
- Lars
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good question.
As I'm not too deep into the Modeler development I can't really comment on this.
The thing is: when you selected the default language before SPS 5, the language was not just defaulted, but fixed instead.
So, technically it didn't matter if you selected text join, what you got was the outer join with a constant filter.
The text join really only works with dynamic language selection (that's what makes the text join a text join if you want), so I guess, the developers removed it for simplicity.
Cheers, Lars
Hi Lars,
Sorry for asking this again, but earlier there was a setting for language called Dynamic,now that it is removed, how can I ensure that when I log in, I should see the text in English and when my colleague logs in, he should see it in Deutsche.
I thought it would depend on the default language set for my profile in BW or BO tool and it will be passed on to the underlying HANA Information models accordingly.
Does this understanding correct ?
Regards,
Ravi
Right Ravi, I should have mentioned that specifically...
Now in SPS 5, whenever you create a text join it always uses the dynamic language filter (the $$language$$) filter.
The actual value is determined by the session context variable (LOCALE) of the current session.
select * from m_session_context where connection_id=current_connection;
HOST | PORT | CONNECTION_ID | KEY | VALUE | SECTION |
xxx | 30003 | 200918 | CLIENT | SYSTEM | |
xxx | 30003 | 200918 | PROTOCOL_VERSION | 4.1 (1, 1) | SYSTEM |
xxx | 30003 | 200918 | LOCALE | en | SYSTEM |
xxx | 30003 | 200918 | APPLICATIONVERSION | 1.0.49.201301220705 | USER |
xxx | 30003 | 200918 | APPLICATION | HDBStudio | USER |
These setting are usually set by the respective HANA clients (e.g HDBStudio).
If and how BW or BO sets it, is something I don't know, but I assume they do it correctly to match the locale of the end-users setups.
Cheers, Lars
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.