Matthias Heuser ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c8f9a10ac771b2c5de5c440
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiY2JjYTZmNDhjN2RhNDk3N2JlODkwZDcxMzNkZjlmOWEiLCJwIjoiaiJ9
 ) / Bug ( 
https://osgeo-org.atlassian.net/browse/GEOS-10593?atlOrigin=eyJpIjoiY2JjYTZmNDhjN2RhNDk3N2JlODkwZDcxMzNkZjlmOWEiLCJwIjoiaiJ9
 ) GEOS-10593 ( 
https://osgeo-org.atlassian.net/browse/GEOS-10593?atlOrigin=eyJpIjoiY2JjYTZmNDhjN2RhNDk3N2JlODkwZDcxMzNkZjlmOWEiLCJwIjoiaiJ9
 ) Creating SQL View via REST API is not possible ( 
https://osgeo-org.atlassian.net/browse/GEOS-10593?atlOrigin=eyJpIjoiY2JjYTZmNDhjN2RhNDk3N2JlODkwZDcxMzNkZjlmOWEiLCJwIjoiaiJ9
 )

Issue Type: Bug Affects Versions: 2.21.0 Assignee: Unassigned Components: REST 
Created: 21/Jul/22 2:31 PM Priority: Medium Reporter: Matthias Heuser ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=5c8f9a10ac771b2c5de5c440
 )

I am trying to create a layer by adding a feature type via the REST API that is 
using a virtual table (SQL View).
In the past (version 2.20.x) this worked without issue, but after the upgrade 
to 2.21.0 the creation fails with the following error:

Failed to access data source to check attribute customization

I then tried to add the layer manually to see if this still works and I was 
able to add this layer.

Further investigation of the changes between saving via the web application and 
saving via REST showed the following:

* saving via web creates a virtual table entry in the JDBCDataSource
* saving via REST does not create this virtual table entry in the data source
* a new validation for FeatureTypeInfo (the FeatureTypeValidator) was 
introduced in 2.21.x
* this validation fails because the virtual table entry is missing in the data 
source and there is no database table matching the native name of feature type 
I am trying to create.

When I added the virtual table entry (using a debugger) in the data source 
before the validation happens, the saving of the feature type was able to 
continue successfully.

( 
https://osgeo-org.atlassian.net/browse/GEOS-10593#add-comment?atlOrigin=eyJpIjoiY2JjYTZmNDhjN2RhNDk3N2JlODkwZDcxMzNkZjlmOWEiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-10593#add-comment?atlOrigin=eyJpIjoiY2JjYTZmNDhjN2RhNDk3N2JlODkwZDcxMzNkZjlmOWEiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100202- 
sha1:c075b5d )
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to