search for: path_id

...to update a document. The document is identified by the document path e.g. /home/user/file.txt. To find the doc id by the path I need to assign the path to the document. In the FAQ is supposed to add the doc id (the path) as a term to the document. My idea is to at the path as a value by #define PATH_ID 0 add_value(PATH_ID, "/home/user/file.txt") and then do a query: Query (Query::op op_, PATH_ID, "/home/user/file.txt", "/home/user/file.txt") Is there a drawback to do such a query on a value? Or is a query on a value even faster? thank you Clemens -- Using Oper...

...;/sbin/dasd_id", SYMLINK="disk/by-id/ccw-%c" KERNEL="dasd*[0-9]", PROGRAM="/sbin/dasd_id", SYMLINK="disk/by-id/ccw-%c-part%n" SYMLINK="disk/by-id/scsi-%c" SYMLINK="disk/by-id/scsi-%c-part%n" KERNEL="sd*", PROGRAM="/sbin/path_id", SYMLINK="disk/by-path/%c" KERNEL="hd*", PROGRAM="/sbin/path_id", SYMLINK="disk/by-path/%c" KERNEL="dasd*", PROGRAM="/sbin/path_id", SYMLINK="disk/by-path/%c" KERNEL="sd*", PROGRAM="/sbin/scsi_id", SYMLI...

I have 3 tables keywords (keywords attached to a file) files (info about the file) paths (path for the file) [This is a legacy database, so I can''t change this] keyword belongs_to file and file belongs_to path. Users need to be able to search the keywords, but they only have access to certain volumes, so the results need to be limited by the path. I also need to show paging,

On Tue, Aug 25, 2015 at 1:58 PM, Kay Sievers <kay at vrfy.org> wrote: > On Tue, Aug 25, 2015 at 1:52 PM, Michael S. Tsirkin <mst at redhat.com> wrote: >> On Tue, Aug 25, 2015 at 01:46:49PM +0200, Kay Sievers wrote: >>> On Tue, Aug 25, 2015 at 1:43 PM, Michael S. Tsirkin <mst at redhat.com> wrote: >>> > On Mon, Aug 24, 2015 at 06:10:01PM +0200, Tom

On Thu, Mar 27, 2014 at 7:59 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Thu, Mar 27, 2014 at 07:43:34PM +0100, Kay Sievers wrote: >> On Thu, Mar 27, 2014 at 6:30 PM, Michael S. Tsirkin <mst at redhat.com> wrote: >> >> > If the virtio device is a PCI device, it is really best to >> > treat it like you treat any other PCI function (I guess you

...vstorPacket->operation, vstorPacket->status); goto Cleanup; } - storDevice->PathId = vstorPacket->StorageChannelProperties.PathId; - storDevice->TargetId = vstorPacket->StorageChannelProperties.TargetId; + storDevice->PathId = vstorPacket->storage_channel_properties.path_id; + storDevice->TargetId + = vstorPacket->storage_channel_properties.target_id; DPRINT_DBG(STORVSC, "channel flag 0x%x, max xfer len 0x%x", - vstorPacket->StorageChannelProperties.Flags, - vstorPacket->StorageChannelProperties.MaxTransferBytes); + vstorPacket-&...

...vstorPacket->operation, vstorPacket->status); goto Cleanup; } - storDevice->PathId = vstorPacket->StorageChannelProperties.PathId; - storDevice->TargetId = vstorPacket->StorageChannelProperties.TargetId; + storDevice->PathId = vstorPacket->storage_channel_properties.path_id; + storDevice->TargetId + = vstorPacket->storage_channel_properties.target_id; DPRINT_DBG(STORVSC, "channel flag 0x%x, max xfer len 0x%x", - vstorPacket->StorageChannelProperties.Flags, - vstorPacket->StorageChannelProperties.MaxTransferBytes); + vstorPacket-&...

On Thu, Mar 27, 2014 at 8:13 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Thu, Mar 27, 2014 at 08:06:15PM +0100, Kay Sievers wrote: >> On Thu, Mar 27, 2014 at 7:59 PM, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Thu, Mar 27, 2014 at 07:43:34PM +0100, Kay Sievers wrote: >> >> On Thu, Mar 27, 2014 at 6:30 PM, Michael S. Tsirkin <mst at

On Wed, Sep 02, 2015 at 01:53:33PM +0200, Tom Gundersen wrote: > On Tue, Aug 25, 2015 at 1:58 PM, Kay Sievers <kay at vrfy.org> wrote: > > On Tue, Aug 25, 2015 at 1:52 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > >> On Tue, Aug 25, 2015 at 01:46:49PM +0200, Kay Sievers wrote: > >>> On Tue, Aug 25, 2015 at 1:43 PM, Michael S. Tsirkin <mst at

On Wed, Sep 02, 2015 at 01:53:33PM +0200, Tom Gundersen wrote: > On Tue, Aug 25, 2015 at 1:58 PM, Kay Sievers <kay at vrfy.org> wrote: > > On Tue, Aug 25, 2015 at 1:52 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > >> On Tue, Aug 25, 2015 at 01:46:49PM +0200, Kay Sievers wrote: > >>> On Tue, Aug 25, 2015 at 1:43 PM, Michael S. Tsirkin <mst at

On Thu, Mar 27, 2014 at 09:24:10PM +0100, Tom Gundersen wrote: > On Thu, Mar 27, 2014 at 8:25 PM, Kay Sievers <kay at vrfy.org> wrote: > > On Thu, Mar 27, 2014 at 8:13 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > >> On Thu, Mar 27, 2014 at 08:06:15PM +0100, Kay Sievers wrote: > >>> On Thu, Mar 27, 2014 at 7:59 PM, Michael S. Tsirkin <mst at

On Thu, Mar 27, 2014 at 07:43:34PM +0100, Kay Sievers wrote: > On Thu, Mar 27, 2014 at 6:30 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > > > If the virtio device is a PCI device, it is really best to > > treat it like you treat any other PCI function (I guess you mean > > function and not device, right? We support multifunction > > devices and some

On Thu, Mar 27, 2014 at 07:43:34PM +0100, Kay Sievers wrote: > On Thu, Mar 27, 2014 at 6:30 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > > > If the virtio device is a PCI device, it is really best to > > treat it like you treat any other PCI function (I guess you mean > > function and not device, right? We support multifunction > > devices and some

On Thu, Mar 27, 2014 at 08:06:15PM +0100, Kay Sievers wrote: > On Thu, Mar 27, 2014 at 7:59 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > > On Thu, Mar 27, 2014 at 07:43:34PM +0100, Kay Sievers wrote: > >> On Thu, Mar 27, 2014 at 6:30 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > >> > >> > If the virtio device is a PCI device, it is

On Thu, Mar 27, 2014 at 08:06:15PM +0100, Kay Sievers wrote: > On Thu, Mar 27, 2014 at 7:59 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > > On Thu, Mar 27, 2014 at 07:43:34PM +0100, Kay Sievers wrote: > >> On Thu, Mar 27, 2014 at 6:30 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > >> > >> > If the virtio device is a PCI device, it is

On Thu, Mar 27, 2014 at 8:25 PM, Kay Sievers <kay at vrfy.org> wrote: > On Thu, Mar 27, 2014 at 8:13 PM, Michael S. Tsirkin <mst at redhat.com> wrote: >> On Thu, Mar 27, 2014 at 08:06:15PM +0100, Kay Sievers wrote: >>> On Thu, Mar 27, 2014 at 7:59 PM, Michael S. Tsirkin <mst at redhat.com> wrote: >>> > On Thu, Mar 27, 2014 at 07:43:34PM +0100, Kay

On Thu, Mar 27, 2014 at 8:25 PM, Kay Sievers <kay at vrfy.org> wrote: > On Thu, Mar 27, 2014 at 8:13 PM, Michael S. Tsirkin <mst at redhat.com> wrote: >> On Thu, Mar 27, 2014 at 08:06:15PM +0100, Kay Sievers wrote: >>> On Thu, Mar 27, 2014 at 7:59 PM, Michael S. Tsirkin <mst at redhat.com> wrote: >>> > On Thu, Mar 27, 2014 at 07:43:34PM +0100, Kay

...ogram: '/lib/udev/scsi_id' (stdout) 'ID_SERIAL=' run_program: '/lib/udev/scsi_id' (stdout) 'ID_TYPE=cd' run_program: '/lib/udev/scsi_id' (stdout) 'ID_BUS=scsi' run_program: '/lib/udev/scsi_id' returned with status 0 run_program: '/lib/udev/path_id /block/sr0' run_program: '/lib/udev/path_id' (stdout) 'ID_PATH=pci-0000:00:1f.2-scsi-1:0:0:0' run_program: '/lib/udev/path_id' returned with status 0 udev_rules_get_name: add symlink 'disk/by-path/pci-0000:00:1f.2-scsi-1:0:0:0' udev_device_event: device '/b...

Further cleanup of the hv drivers: 1) Cleanup the reference counting mess for both stor and net devices. 2) Handle all block devices using the storvsc driver. 3) Accomodate some host side scsi emulation bugs. 4) In case of scsi errors off-line the device. Regads, K. Y

Further cleanup of the hv drivers: 1) Cleanup the reference counting mess for both stor and net devices. 2) Handle all block devices using the storvsc driver. 3) Accomodate some host side scsi emulation bugs. 4) In case of scsi errors off-line the device. Regads, K. Y