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

Error 'could not store action: Illegal primitive value for property date', after trying to adding reference to existing dataobject #991

Closed
laura-ham opened this issue Sep 27, 2019 · 5 comments
Assignees
Labels

Comments

@laura-ham
Copy link
Contributor

The POST request to http://localhost:8080/v1/actions/22cc3380-ef73-48f8-9e3c-c603fae0f4b0/references/toCompany leads to the error message:

{
    "error": [
        {
            "message": "could not store action: Illegal primitive value for property date, value is \"2019-03-24T14:25:57Z\""
        }
    ]
}

The data object where the reference should be added to has a property date with the dataType date, which is filled with the abovementioned date. This is previously added to the Weaviate instance without any problems. Adding a reference to another property of this same action class however suddenly gives an error message about the date.

@stale
Copy link

stale bot commented Apr 6, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Apr 6, 2020
@stale stale bot closed this as completed Apr 13, 2020
@bobvanluijt
Copy link
Member

Still a relevant bug

@bobvanluijt bobvanluijt reopened this Apr 14, 2020
@stale stale bot removed wontfix labels Apr 14, 2020
@etiennedi
Copy link
Member

etiennedi commented Apr 15, 2020

Fair point, I'm configuring the stale bot not to close issues with the label bug, as bugs don't just magically disappear on their own (unfortunately).

EDIT: done.

@etiennedi
Copy link
Member

Still a relevant bug

@bobvanluijt How did you determine this? Based on the description I would have expected that this was fixed with #1069, but it's hard to validate without building a reproducing example. So if you already have one, please share.

@bobvanluijt
Copy link
Member

Because it is a relevant feature, didn't test it but assumed it from the fact that it was still open and had no commits.

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

No branches or pull requests

3 participants