GeoServer

RetypeDataStore does not properly handle the case of a feature type renamed to a target name that is also available the native name of another feature type

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.0.3
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    1

Description

Say the original data store has names "table1" and "table" and "table1" is renamed to "table2".
The store should hide the original "table2", but instead it ends up using the original "table2" when "table1" is queried.

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. GEOS-2545 ResourcePool uses significant resources building renaming datastores

  • Major - Major loss of function.
  • Reopened - This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrea Aime added a comment -

The patch I'm about to attach solves both this issue and GEOS-2545. Justin, want to have a look before I commit?

Show
Andrea Aime added a comment - The patch I'm about to attach solves both this issue and GEOS-2545 . Justin, want to have a look before I commit?
Hide
Permalink
Justin Deoliveira added a comment -

Patch looks good. I wonder though if this could be a potential pitfall though. It seems like some sort of warning should be omitted when the user picks an alias that clashes with a native name. Maybe not... just thinking out loud.

Show
Justin Deoliveira added a comment - Patch looks good. I wonder though if this could be a potential pitfall though. It seems like some sort of warning should be omitted when the user picks an alias that clashes with a native name. Maybe not... just thinking out loud.
Hide
Permalink
Andrea Aime added a comment -

Maybe not. the retyping store is built only for that layer, and the real one will still be visible when creating new layers. That will generate a name conflict in the layers that can be resolved by renaming the layer again (two renames at the price of one, how is that for an offer???)

Show
Andrea Aime added a comment - Maybe not. the retyping store is built only for that layer, and the real one will still be visible when creating new layers. That will generate a name conflict in the layers that can be resolved by renaming the layer again (two renames at the price of one, how is that for an offer???)
Hide
Permalink
Andrea Aime added a comment -

Fixed on 2.0.x and trunk

Show
Andrea Aime added a comment - Fixed on 2.0.x and trunk
Hide
Permalink
Andrea Aime added a comment -

Mass closing all issues that have been in "resolved" state for 2 months or more without any feedback or update

Show
Andrea Aime added a comment - Mass closing all issues that have been in "resolved" state for 2 months or more without any feedback or update

People

  • Assignee:
    Andrea Aime
    Reporter:
    Andrea Aime
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: