Issue with wdsub command #10
Comments
|
As an additional data point, I tried compiling on my computer as well (WSL on Windows 10) and got the following log messages. Different than @sabahzero's, but similarly couldn't find a |
|
Ops, I missed the first issue raised by Sabah. You were right that the README was not ok. The instructions to generate the binary were wrong, instead of Once you run: The binary will be available as a compressed file at: If you uncompress that file, the running scripts are at folder I have updated the README to repair that mistake. Thanks a lot for using |
|
Thank you! And no worries, I know I submitted a few that same day so I thought the tag might help. After following your instructions, now I get |
|
You mean that $ bin/wdsubroot dump --help
Usage:
wdsub dump --count [--out <file>] [--verbose] [--processor <string>] <dumpFile>
wdsub dump --show [--maxStatements <integer>] [--out <file>] [--verbose] [--processor <string>] <dumpFile>
wdsub dump --schema <file> [--out <file>] [--verbose] [--processor <string>] <dumpFile>
Process example dump file.
Options and flags:
--help
Display this help text.
--count
count entities
--show
show entities
--maxStatements <integer>
max statements to show
--schema <file>, -s <file>
ShEx schema
--out <file>, -o <file>
output path
--verbose
Verbose mode
--processor <string>
Dump processor library. Possible values: Fs2,WDTKAssuming you have a dump file located, for example, at folder $ bin/wdsubroot dump --schema examples/cities.shex --processor WDTK --out out/cities.json.gz examples/dump.json.gzwhich would generate the subset If you want to play with that same example, you can use the following schema: and this example dump: https://github.com/weso/sparkwdsub/blob/master/examples/dump.json.gz |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @labra, @andrewsu pointed out to me that I could be more clear in my compilation output from the
sbt packageBincommand (see below). Still unable to find the wdsub command for execution. Thoughts?Many thanks!
The text was updated successfully, but these errors were encountered: