You can translate the question and the replies:

remove parameters from query output

Hi, Parameters added in a selection or join are always shown in the query output as a new column, is it possible to hide these columns in the query output? The reason I use parameters in some views, is due to the parameter is mandatory for execution, otherwise I could set a where clause on execution. If it is not an option to hide columns generated with the parameter name, is this some strategy from denodo?
user
23-04-2018 09:48:39 -0400
code

4 Answers

Hi, When a parameter is added to the derived view then the view will have a new output field in the query output. You could not hide these columns from the query output because they are mainly used to change the condition provided at runtime. As the parameter has a default value it is easy to query based on it. For more information, refer the section [Parameters of Derived Views](https://community.denodo.com/docs/html/browse/6.0/vdp/administration/creating_views/creating_derived_views/creating_selection_views#parameters-of-derived-views) of the Virtual DataPort Administration Guide. Hope this helps.
Denodo Team
24-04-2018 08:44:18 -0400
code
Hi, thank you for this information, so we do not have to look for any option to hide these columns. For some actions, it could be interesting if we can hide these parameter columns. For example, by adding an extra column in the parameters window to indicate of a parameter will be shown in the output or not. We created some parameterized views, having the same columns, different purposes, and changing parameter fields, if we could remove these parameter columns from the output, we could use the minus or union operator for some actions. kind regards
user
26-04-2018 05:47:17 -0400
Hi, The main purpose of adding parameter is to provide runtime conditions hence it cannot be hided or removed from the output. You could perform union or minus operation by providing the value for the parameterized views. Hope this helps.
Denodo Team
17-05-2018 08:42:49 -0400
code
Hello, In a project I'm working on, I had the same need expressed in the original question, so I wanted to share the solution we found. our need was to materialise (export) the result of some views, but the exported file shouldn't include the parameter column (same need), so the solution we came with is to create a derived view on top of the view we need to materialise, this new derived view contains a single column (we named DATA) in wich all the non parameter columns of the principal view are concatenated with a sepeartor caracter. Of course, the parameter columns will remane in the new derived view, but they can be eliminated in the export section of the materialisation job by mapping the column Data only of the derived view. The exported file will contain only the data with no header (the column names) this also could be adressed if you need to do so. Hope this could help anyone having the same need. Rgards Ali Ben Tahar
user
04-07-2023 13:09:19 -0400
You must sign in to add an answer. If you do not have an account, you can register here