Various SQL fragments refer to non-existant column type in CalEvent table.
See following file and search for "calEvent.type ":
As can be see in the portal-tables.sql file, the CalEvent table has a column named "type_", not a column named "type".
Attached see error.log for this error in action when calling CalEventServiceUtil.getEvents(). Although I never ran into this issue during Liferay OOB behavior, it did come up while implementing multi-filter functionality. In any case, there should be no hard-coded reference to a non-existent column anyway, correct?