From: "Kevin Frey" <kevin.frey@internode.net.au>
To: ceph-devel@vger.kernel.org
Subject: How Might a Full-Text Searching Capability be Integrated with Ceph?
Date: Thu, 29 Aug 2013 14:56:32 +1000 [thread overview]
Message-ID: <018901cea474$23119700$6934c500$@internode.net.au> (raw)
Hello All,
This is my first post to the list, and my question is very general to
encourage discussion (perhaps derision).
I am the team-leader involved with the development of an application of
which one common capability is a document management like facility that
permits a user to attach (in a logical sense) files to given data records
in the database. The kinds of files being attached would be Microsoft Word
documents, spreadsheets, PDF files, and so on. For various reasons we dont
store these files in the SQL database but instead in an associated file
store.
This file store is not very large at present (a few hundred Gb perhaps) and
the storage methodology is fairly naïve in the sense it stores onto a single
volume using RAID as the durability component.
Our file store effectively does two things for us however: act as a basic
store for the files; provides the feed for a full-text indexing system so
that the files can be searched on.
Ceph is a product Ive been following for a while now and I have no question
it can handle the storage aspect, but my question relates to how I would
achieve my second requirement?
From what Ive read, CephFS is not production ready but one obvious
strategy to achieve a searchable database would be to just expose the whole
directory namespace (or a single pool?) via CephFS and point a standard file
indexing product at it. Would this work? Would it be a good or a bad idea
(ignoring the status of CephFS itself).
Or would you suggest something that is perhaps more tightly integrated with
the RADOS object store? I need to be wary of not putting myself in the
position of having to write an entire file indexing suite also in terms of
weighing up design possibilities.
Thanks in advance
Kevin
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2013-08-29 4:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 4:56 Kevin Frey [this message]
2013-08-30 2:57 ` How Might a Full-Text Searching Capability be Integrated with Ceph? Gregory Farnum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='018901cea474$23119700$6934c500$@internode.net.au' \
--to=kevin.frey@internode.net.au \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox