Arcgis. Cygnus is using case sensitivity with attributes although arcgis is not case sensitive about fiware-cygnus HOT 5 OPEN

It seems the responsible for checking the existence of the attribute taking in account the case is the method containsKey () in:

because when attributes that don't match the method hasAttribute cygnus throws:

time=2023-10-26T14:17:05.542Z | lvl=DEBUG | corr=4edfa531-7443-4537-b94c-0b9b5717a52e; cbnotif=1 | trans=d2a0be73-29f7-41af-843c-200fc013a089 | srv=N/A | subsrv=N/A | comp=cygnus-ngsi | op=cleanFeature | msg=com.telefonica.iot.cygnus.backends.arcgis.restutils.ArcgisFeatureTable[693] : ArcgisFeatureTable, cleanFeature: Field not found in table, ignoring it, LA10

from fiware-cygnus.

It seems the responsible for checking the existence of the attribute taking in account the case is the method containsKey () in:

fiware-cygnus/cygnus-common/src/main/java/com/telefonica/iot/cygnus/backends/arcgis/restutils/ArcgisFeatureTable.java

Lines 624 to 626 in 8bcbbed

	public boolean hasAttribute(String attName) {
	return arcGISFeatureTable.getTableAttributes().containsKey(attName);
	}

because when attributes that don't match the method hasAttribute cygnus throws:

time=2023-10-26T14:17:05.542Z | lvl=DEBUG | corr=4edfa531-7443-4537-b94c-0b9b5717a52e; cbnotif=1 | trans=d2a0be73-29f7-41af-843c-200fc013a089 | srv=N/A | subsrv=N/A | comp=cygnus-ngsi | op=cleanFeature | msg=com.telefonica.iot.cygnus.backends.arcgis.restutils.ArcgisFeatureTable[693] : ArcgisFeatureTable, cleanFeature: Field not found in table, ignoring it, LA10

Done in db8f423

from fiware-cygnus.

PR #2319 with the fix has been merged.

@danielvillalbamota could you have a look and close this issue if it is already solved by that PR, pls? (or specify what's missing or not working in negative case)

from fiware-cygnus.

PR #2319 with the fix has been merged.

@danielvillalbamota could you have a look and close this issue if it is already solved by that PR, pls? (or specify what's missing or not working in negative case)

That PR included the last commit that was not enough to solve this issue, in fact, it introduced a not desired behavior, so it has been reverted in this PR #2321.

This issue still exists but can be avoided by using name mappings

from fiware-cygnus.

In version 3.3.0 we have provided a solution that solves this issue but requires NM.

The definitive solution for this issue will be a solution which doesn't need NM usage.

from fiware-cygnus.