[jira] [Updated] (SOLR-10521) sort by string field of the nested child when searching with {!parent}
[
https://issues.apache.org/jira/browse/SOLR-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10521:
Attachment: SOLR-10521-doc.patch
[~ctargett], would you mind to look at [^SOLR-10521-doc.patch]?
> sort by string field of the nested child when searching with {!parent}
> --
>
> Key: SOLR-10521
> URL: https://issues.apache.org/jira/browse/SOLR-10521
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Mikhail Khludnev
> Fix For: 6.6, master (7.0)
>
> Attachments: SOLR-10521-6x.patch, SOLR-10521-doc.patch,
> SOLR-10521.patch, SOLR-10521.patch, SOLR-10521.patch, SOLR-10521.patch,
> SOLR-10521-raw.patch
>
>
> The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
> The approach to hookup -it- is -a little bit tricky-:
> -{{sort=\{!childfield bjq=$q field=COLOR_s}desc}}-
> {{sort=\childfield(COLOR_s,$q) desc}}
> the question no.1 wdyt about the syntax?
> internally it creates a function query with valueSource which produces
> {{ToParentBlockJoinSortField}}
> The main challenge is picking Solr field type from
> {{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
> ByteRefs need to be properly marshaled and unmarshalled by a field type from
> the child scope.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10521) sort by string field of the nested child when searching with {!parent}
[
https://issues.apache.org/jira/browse/SOLR-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10521:
Description:
The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
The approach to hookup -it- is -a little bit tricky-:
-{{sort=\{!childfield bjq=$q field=COLOR_s}desc}}-
{{sort=\childfield(COLOR_s,$q) desc}}
the question no.1 wdyt about the syntax?
internally it creates a function query with valueSource which produces
{{ToParentBlockJoinSortField}}
The main challenge is picking Solr field type from
{{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
ByteRefs need to be properly marshaled and unmarshalled by a field type from
the child scope.
was:
The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
The approach to hookup -it- is -a little bit tricky-:
-{{sort=\{!childfield bjq=$q field=COLOR_s}desc}}-
{{sort=\childfield(COLOR_s,) desc}}
the question no.1 wdyt about the syntax?
internally it creates a function query with valueSource which produces
{{ToParentBlockJoinSortField}}
The main challenge is picking Solr field type from
{{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
ByteRefs need to be properly marshaled and unmarshalled by a field type from
the child scope.
> sort by string field of the nested child when searching with {!parent}
> --
>
> Key: SOLR-10521
> URL: https://issues.apache.org/jira/browse/SOLR-10521
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Mikhail Khludnev
> Fix For: 6.6, master (7.0)
>
> Attachments: SOLR-10521-6x.patch, SOLR-10521.patch, SOLR-10521.patch,
> SOLR-10521.patch, SOLR-10521.patch, SOLR-10521-raw.patch
>
>
> The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
> The approach to hookup -it- is -a little bit tricky-:
> -{{sort=\{!childfield bjq=$q field=COLOR_s}desc}}-
> {{sort=\childfield(COLOR_s,$q) desc}}
> the question no.1 wdyt about the syntax?
> internally it creates a function query with valueSource which produces
> {{ToParentBlockJoinSortField}}
> The main challenge is picking Solr field type from
> {{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
> ByteRefs need to be properly marshaled and unmarshalled by a field type from
> the child scope.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10521) sort by string field of the nested child when searching with {!parent}
[
https://issues.apache.org/jira/browse/SOLR-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10521:
Attachment: SOLR-10521-6x.patch
[^SOLR-10521-6x.patch] with stats instead of metrics
> sort by string field of the nested child when searching with {!parent}
> --
>
> Key: SOLR-10521
> URL: https://issues.apache.org/jira/browse/SOLR-10521
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Mikhail Khludnev
> Attachments: SOLR-10521-6x.patch, SOLR-10521.patch, SOLR-10521.patch,
> SOLR-10521.patch, SOLR-10521.patch, SOLR-10521-raw.patch
>
>
> The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
> The approach to hookup -it- is -a little bit tricky-:
> -{{sort=\{!childfield bjq=$q field=COLOR_s}desc}}-
> {{sort=\childfield(COLOR_s,) desc}}
> the question no.1 wdyt about the syntax?
> internally it creates a function query with valueSource which produces
> {{ToParentBlockJoinSortField}}
> The main challenge is picking Solr field type from
> {{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
> ByteRefs need to be properly marshaled and unmarshalled by a field type from
> the child scope.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10521) sort by string field of the nested child when searching with {!parent}
[
https://issues.apache.org/jira/browse/SOLR-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10521:
Description:
The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
The approach to hookup -it- is -a little bit tricky-:
-{{sort=\{!childfield bjq=$q field=COLOR_s}desc}}-
{{sort=\childfield(COLOR_s,) desc}}
the question no.1 wdyt about the syntax?
internally it creates a function query with valueSource which produces
{{ToParentBlockJoinSortField}}
The main challenge is picking Solr field type from
{{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
ByteRefs need to be properly marshaled and unmarshalled by a field type from
the child scope.
was:
The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
The approach to hookup it is a little bit tricky:
{{sort=\{!childfield bjq=$q field=COLOR_s}desc}}
the question no.1 wdyt about the syntax?
internally it creates a function query with valueSource which produces
{{ToParentBlockJoinSortField}}
The main challenge is picking Solr field type from
{{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
ByteRefs need to be properly marshared and unmarshalled by a field type from
child scope.
> sort by string field of the nested child when searching with {!parent}
> --
>
> Key: SOLR-10521
> URL: https://issues.apache.org/jira/browse/SOLR-10521
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Mikhail Khludnev
> Attachments: SOLR-10521.patch, SOLR-10521.patch, SOLR-10521.patch,
> SOLR-10521.patch, SOLR-10521-raw.patch
>
>
> The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
> The approach to hookup -it- is -a little bit tricky-:
> -{{sort=\{!childfield bjq=$q field=COLOR_s}desc}}-
> {{sort=\childfield(COLOR_s,) desc}}
> the question no.1 wdyt about the syntax?
> internally it creates a function query with valueSource which produces
> {{ToParentBlockJoinSortField}}
> The main challenge is picking Solr field type from
> {{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
> ByteRefs need to be properly marshaled and unmarshalled by a field type from
> the child scope.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10521) sort by string field of the nested child when searching with {!parent}
[
https://issues.apache.org/jira/browse/SOLR-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10521:
Attachment: SOLR-10521.patch
[^SOLR-10521.patch] is a new hope. It wraps the _true_
{{FieldComparator}} with a simple {{utf8ToString()}} converter. Let's
take a one day timeout, and kick it off then.
> sort by string field of the nested child when searching with {!parent}
> --
>
> Key: SOLR-10521
> URL: https://issues.apache.org/jira/browse/SOLR-10521
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Mikhail Khludnev
> Attachments: SOLR-10521.patch, SOLR-10521.patch, SOLR-10521.patch,
> SOLR-10521.patch, SOLR-10521-raw.patch
>
>
> The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
> The approach to hookup it is a little bit tricky:
> {{sort=\{!childfield bjq=$q field=COLOR_s}desc}}
> the question no.1 wdyt about the syntax?
> internally it creates a function query with valueSource which produces
> {{ToParentBlockJoinSortField}}
> The main challenge is picking Solr field type from
> {{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
> ByteRefs need to be properly marshared and unmarshalled by a field type from
> child scope.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10521) sort by string field of the nested child when searching with {!parent}
[
https://issues.apache.org/jira/browse/SOLR-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10521:
Attachment: SOLR-10521.patch
[^SOLR-10521.patch] ByteRefs from Comparator are converted to byte[] and then
unmarshalled back explicitly. Yet another one spaghetti. It seems like
no-commit to me.
> sort by string field of the nested child when searching with {!parent}
> --
>
> Key: SOLR-10521
> URL: https://issues.apache.org/jira/browse/SOLR-10521
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Mikhail Khludnev
> Attachments: SOLR-10521.patch, SOLR-10521.patch, SOLR-10521.patch,
> SOLR-10521-raw.patch
>
>
> The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
> The approach to hookup it is a little bit tricky:
> {{sort=\{!childfield bjq=$q field=COLOR_s}desc}}
> the question no.1 wdyt about the syntax?
> internally it creates a function query with valueSource which produces
> {{ToParentBlockJoinSortField}}
> The main challenge is picking Solr field type from
> {{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
> ByteRefs need to be properly marshared and unmarshalled by a field type from
> child scope.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10521) sort by string field of the nested child when searching with {!parent}
[
https://issues.apache.org/jira/browse/SOLR-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10521:
Attachment: SOLR-10521.patch
[^SOLR-10521.patch] here we go!
the valuesource syntax is {{sort=childfield(field,$bjq) asc}} or
{{sort=childfield(field) asc}} assuming {{$q}}.
The sad thing is that, I cant' improve QueryComponent change (it's brilliant
already).
So, far it can be only used for sorting. But can be extended to regular value
source functionality in future. This might even work numerics, but I havent'
checked it yet.
Reviews and suggestions are urgently required!
> sort by string field of the nested child when searching with {!parent}
> --
>
> Key: SOLR-10521
> URL: https://issues.apache.org/jira/browse/SOLR-10521
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Mikhail Khludnev
> Attachments: SOLR-10521.patch, SOLR-10521.patch, SOLR-10521-raw.patch
>
>
> The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
> The approach to hookup it is a little bit tricky:
> {{sort=\{!childfield bjq=$q field=COLOR_s}desc}}
> the question no.1 wdyt about the syntax?
> internally it creates a function query with valueSource which produces
> {{ToParentBlockJoinSortField}}
> The main challenge is picking Solr field type from
> {{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
> ByteRefs need to be properly marshared and unmarshalled by a field type from
> child scope.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10521) sort by string field of the nested child when searching with {!parent}
[
https://issues.apache.org/jira/browse/SOLR-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10521:
Attachment: SOLR-10521.patch
[^SOLR-10521.patch] done with equality testing, has a cool cloud test.
I want to experiment with value source syntax, WDYT about
{{sort=childfield(name,$q) asc}}?
> sort by string field of the nested child when searching with {!parent}
> --
>
> Key: SOLR-10521
> URL: https://issues.apache.org/jira/browse/SOLR-10521
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Mikhail Khludnev
> Attachments: SOLR-10521.patch, SOLR-10521-raw.patch
>
>
> The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
> The approach to hookup it is a little bit tricky:
> {{sort=\{!childfield bjq=$q field=COLOR_s}desc}}
> the question no.1 wdyt about the syntax?
> internally it creates a function query with valueSource which produces
> {{ToParentBlockJoinSortField}}
> The main challenge is picking Solr field type from
> {{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
> ByteRefs need to be properly marshared and unmarshalled by a field type from
> child scope.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10521) sort by string field of the nested child when searching with {!parent}
[
https://issues.apache.org/jira/browse/SOLR-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10521:
Attachment: (was: SOLR-10500.patch)
> sort by string field of the nested child when searching with {!parent}
> --
>
> Key: SOLR-10521
> URL: https://issues.apache.org/jira/browse/SOLR-10521
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Mikhail Khludnev
> Attachments: SOLR-10521.patch, SOLR-10521-raw.patch
>
>
> The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
> The approach to hookup it is a little bit tricky:
> {{sort=\{!childfield bjq=$q field=COLOR_s}desc}}
> the question no.1 wdyt about the syntax?
> internally it creates a function query with valueSource which produces
> {{ToParentBlockJoinSortField}}
> The main challenge is picking Solr field type from
> {{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
> ByteRefs need to be properly marshared and unmarshalled by a field type from
> child scope.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10521) sort by string field of the nested child when searching with {!parent}
[
https://issues.apache.org/jira/browse/SOLR-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10521:
Attachment: SOLR-10500.patch
Made a cool test. Caching and equality aren't addressed yet.
Is there are any thoughts about the syntax?
> sort by string field of the nested child when searching with {!parent}
> --
>
> Key: SOLR-10521
> URL: https://issues.apache.org/jira/browse/SOLR-10521
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Mikhail Khludnev
> Attachments: SOLR-10500.patch, SOLR-10521-raw.patch
>
>
> The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
> The approach to hookup it is a little bit tricky:
> {{sort=\{!childfield bjq=$q field=COLOR_s}desc}}
> the question no.1 wdyt about the syntax?
> internally it creates a function query with valueSource which produces
> {{ToParentBlockJoinSortField}}
> The main challenge is picking Solr field type from
> {{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
> ByteRefs need to be properly marshared and unmarshalled by a field type from
> child scope.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10521) sort by string field of the nested child when searching with {!parent}
[
https://issues.apache.org/jira/browse/SOLR-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10521:
Attachment: SOLR-10521-raw.patch
Attaching the first raw scratch with a smoke only coverage. The significant gap
is a lack of caching for bitsets. I also want to make QueryComponent change
nicer.
WDYT about it overall; regarding end user syntax; is there a way to fix
marshalling in a better way (it's QueryComponent changes now)?
> sort by string field of the nested child when searching with {!parent}
> --
>
> Key: SOLR-10521
> URL: https://issues.apache.org/jira/browse/SOLR-10521
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Mikhail Khludnev
> Attachments: SOLR-10521-raw.patch
>
>
> The idea is to integrate Lucene's {{ToParentBlockJoinSortField}}
> The approach to hookup it is a little bit tricky:
> {{sort=\{!childfield bjq=$q field=COLOR_s}desc}}
> the question no.1 wdyt about the syntax?
> internally it creates a function query with valueSource which produces
> {{ToParentBlockJoinSortField}}
> The main challenge is picking Solr field type from
> {{ToParentBlockJoinSortField}}, because as-is it's broken on {{mergeIds}} -
> ByteRefs need to be properly marshared and unmarshalled by a field type from
> child scope.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
