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

Errors parsing STRING value in NT format #1594

Open
Dyfeomorfizm opened this issue Oct 28, 2024 · 2 comments
Open

Errors parsing STRING value in NT format #1594

Dyfeomorfizm opened this issue Oct 28, 2024 · 2 comments

Comments

@Dyfeomorfizm
Copy link

Hello,

Im trying to index my NT data and get following error

ERROR: Parse error at byte position 22324: Parse error at byte position 22324: Value STRING could not be parsed as a floating point value

Is QLEVER unable to parse STRINGs? Or is there any parameter I should add to qleverfile to parse it?

That log file also have such error

ERROR: Could not parse 10,000 Within 1,048,576MB of Turtle input 2024-10-24 12:34:54.523 - ERROR: If you really have Turtle input with such a long structure please recompile with adjusted constants in ConstantsIndexCreation.h or decompress your file and use --file-format mmap

Even though It's a small nt file 1.4GB in size.

I run it on GKE using qlever-control and qlever index command.

Command: index echo '{ "ascii-prefixes-only": false, "num-triples-per-batch": 1000 , "parallel-parsing" : false}' > GDS.settings.json podman run --rm -u root -v /etc/localtime:/etc/localtime:ro -v $(pwd):/index -w /index --init --entrypoint bash --name qlever.index.GDS docker.io/adfreiburg/qlever:latest -c 'cat one.nt | IndexBuilderMain -F nt -f - -i GDS -s GDS.settings.json --stxxl-memory 1000G | tee GDS.index-log.txt'

@joka921
Copy link
Member

joka921 commented Oct 28, 2024

Hi,
Was this the actual error message, or is STRING something you substituted to not disclose the contents of your RDF data?
The message indicates that you probably had the literal "STRING"^^xsd:float" in your datatset (the datatype might also be xsd:double or xsd:decimal for this message to occur.
QLever knows that this datatype represents a number and tries to parse it as such. If this fails, a hard error is thrown.
The easiest way is to fix your dataset. Another possibility (we use this for other datatypes) issome fallback mechansims that for example ignores the datatype for such invalid literals.

@Dyfeomorfizm
Copy link
Author

It has been this one

"STRING"^^http://www.w3.org/2001/XMLSchema#double

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

No branches or pull requests

2 participants