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

Enum properties cannot be written [DATACASS-260] #435

Closed
spring-projects-issues opened this issue Mar 17, 2016 · 1 comment
Closed

Enum properties cannot be written [DATACASS-260] #435

spring-projects-issues opened this issue Mar 17, 2016 · 1 comment
Assignees

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Mar 17, 2016

Mark Paluch opened DATACASS-260 and commented

Mapping of enum types is not supported yet. The mapping converter uses the property data type to determine a converter. The value is not converted into a string or numeric value because the source and target type are the same. Spring Data Cassandra has no built-in support for enums and also @CassandraType annotations are not used while writing an Entity (insert/update/delete).

Example code expected to work:

@Table("book")
public class Book {

	@PrimaryKey
	private String isbn;
	
	private Condition condition;

	// getter/setter omitted.
}

public enum Condition {
	MINT, MHHKAY, NOT_SO_GOOD;
}

Affects: 1.3.2 (Gosling SR2), 1.4 M1 (Hopper)

Issue Links:

  • DATACASS-277 Enum mapping using ordinal value
    ("is depended on by")
  • DATACASS-141 Support for enumeration mapping
    ("supersedes")

Referenced from: pull request #47

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Mar 31, 2016

Mark Paluch commented

Shifting to the next release as we passed Hopper RC1 already

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants