diff options
author | Joey Hess <joeyh@joeyh.name> | 2015-08-19 13:16:01 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2015-08-19 13:16:01 -0400 |
commit | 74ecad87ca4ceac174279d54b09b4dfdd5fa7905 (patch) | |
tree | b905e48e9dee4573e603a9dfc81204b2a3128b6b | |
parent | 10ae7490f83fddc5b2d05d8b2e3ac5244da0fbe1 (diff) |
response
-rw-r--r-- | doc/forum/Searching_metadata_and_file_content__63__/comment_3_67715b73349dc92e9746b234024057ef._comment | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/forum/Searching_metadata_and_file_content__63__/comment_3_67715b73349dc92e9746b234024057ef._comment b/doc/forum/Searching_metadata_and_file_content__63__/comment_3_67715b73349dc92e9746b234024057ef._comment new file mode 100644 index 000000000..56986b55c --- /dev/null +++ b/doc/forum/Searching_metadata_and_file_content__63__/comment_3_67715b73349dc92e9746b234024057ef._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2015-08-19T17:11:41Z" + content=""" +Nice script to use recoil, and I imagine similar approaches could be used +to integrate with other search engines. + +Note that `git annex metadata --json` yields a format better suited to +machine parsing. Especially because metadata values can contain arbitrary +content, even potentially newlines. + +There are plans to eventually make git-annex use a caching database for +things, including metadata. This would automatically get updated whenever there +are changes to the metadata, and SQL queries could then be run against it. +Or, `git annex metadata` queries could boil down to SQL queries and so run +a lot faster than they do now. +"""]] |