(1) The Feature Namespace URI was used to force a namespace for all feature type loaded through GeoServer. The better alternative is to support changing the namespace during ingest. The only remaining concern is construction of the feature as part of defining a layer in the UI. GeoServer does not support changing the name space in this case. However, the forced namespace for all features using a data store is too broad of a solution.

(2) Add a unit test for namespace preservation in the feature data adapter. It does work. Just need to continuously check it.