Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SO-2022 Change complex map field types #110

Merged

Conversation

nagyo
Copy link
Member

@nagyo nagyo commented Sep 21, 2016

Complex map's map group and map priority fields were stored as byte which made it impossible to import maps with group/priority numbers higher than Byte.MAX_VALUE (127), so the fields were changed to integer.

- this is necessary to support values greater than Byte.MAX_VALUE (127)

https://snowowl.atlassian.net/browse/SO-2022

Conflicts:
	snomed/com.b2international.snowowl.snomed.datastore/src/com/b2international/snowowl/snomed/datastore/index/entry/SnomedRefSetMemberIndexEntry.java
	snomed/com.b2international.snowowl.snomed.datastore/src/com/b2international/snowowl/snomed/datastore/index/refset/RefSetMemberMutablePropertyUpdater.java
	snomed/com.b2international.snowowl.snomed.refset.core/src/com/b2international/snowowl/snomed/refset/clone/SnomedRefSetCloner.java
@apeteri apeteri self-assigned this Feb 24, 2017
@apeteri apeteri changed the title Change complex map field types SO-2022 Change complex map field types Feb 24, 2017
@apeteri apeteri self-requested a review February 24, 2017 12:48
Copy link
Member

@apeteri apeteri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me otherwise!

@@ -67,7 +69,7 @@ private void validateMapCategory(final List<String> row) {
final String uuid = row.get(0);
final String effectiveTime = row.get(1);
final String mapCategory = row.get(12);
if (!isComponentExists(mapCategory, ReleaseComponentType.CONCEPT)) {
if (getComponentCategory(mapCategory) == ComponentCategory.CONCEPT && !isComponentExists(mapCategory, ReleaseComponentType.CONCEPT)) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should reject reference set rows where the mapCategoryId value is not a valid SCTID. But that also holds true for all reference set validators, not just this one (report an error if one of the component SCTIDs in a column is nonsensical or does not match the expected type).

@apeteri
Copy link
Member

apeteri commented Feb 24, 2017

Changing the base of this PR to be included in #131.

@apeteri apeteri changed the base branch from develop to feature/SO-2154-refset-api-enhancement February 24, 2017 12:58
@apeteri apeteri merged commit cf78e90 into feature/SO-2154-refset-api-enhancement Feb 24, 2017
@cmark cmark deleted the change_complex_map_field_types branch January 20, 2020 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants