spectacles: [Error] There is already a "field" named
There is an error complaining about duplicate field name between two views [Error] There is already a "field" named, even when Looker’s LookML validation is not showing an error. Even after deleting the view which contains same names, the error still exists. Any idea what’s causing this?
About this issue
- Original URL
- State: open
- Created a year ago
- Comments: 16
For those wondering - we have downgraded our JDK to v8 and it does seem to have fixed the issue! They confirmed that it indeed shouldn’t have any impact on performance or features.
I will report here again should we find ourselves needing to revert back to 11 or disabling the validator!
Partial answer from Looker: “This is only an issue with JDK 11 but not JDK 8, so if downgrading JDK is a possibility for you that may resolve the issue for now.”
You should be able to get in touch with support and ask them to downgrade your version. It shouldn’t result in any feature differences or performance issues, but support should hopefully be able to confirm that.
Hi @attrivivekFF. I’ve just followed up with Looker to get an ETA.
The Looker issue ID for this is 288376313.