You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 18, 2026. It is now read-only.
There's a couple of issues I noticed with the column_names field that I'll just include here because I think they're linked.
Issue 1: client.models.get_data_view()
As it's currently implemented, this method does not specify the column_names parameter in the DataView object that it creates+returns. Therefore, the following code prints different things:
client=CitrinationClient(os.environ['CITRINATION_API_KEY'], 'https://citrination.com')
models_client=client.modelsview_id=7530data_view=models_client.get_data_view(view_id)
print('Names of columns: {0}'.format([c.nameforcindata_view.columns])) # as expectedprint('Column_names: {0}'.format(data_view.column_names)) # empty
Issue 2: client.views
Not sure if I missed this somewhere, but I don't think views/ML configured using the DataViewsClient specifies column_names anywhere, either in the client or builder. If you change the view_id in the above code to 8001, which is the same mapping but created using the API instead of UI, you'll see None everywhere.
Don't know how often this parameter column_names will be accessed/used, but I wanted to point it out. Let me know if I overlooked a field somewhere.