On 20.09.2010, at 08:32, Lukas Kahwe Smith wrote:
> Hi,
>
> ok since it didnt seem like there was interest to document this approach on
> the wiki i have simply documented it on my blog:
> http://pooteeweet.org/blog/1827
sorry for the spam. Lance (and Erik) did think it would be good to add i
Thank you very much Shawn.
Paul
On Fri, Sep 17, 2010 at 12:11 PM, Shawn Heisey wrote:
> On 9/17/2010 3:01 AM, Paul Dhaliwal wrote:
>
>> Another feature missing in DIH is ability to pass parameters into your
>> queries. If one could pass a named or positional parameter for an entity
>> query, i
Hi,
ok since it didnt seem like there was interest to document this approach on the
wiki i have simply documented it on my blog:
http://pooteeweet.org/blog/1827
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
On 9/17/2010 3:01 AM, Paul Dhaliwal wrote:
Another feature missing in DIH is ability to pass parameters into your
queries. If one could pass a named or positional parameter for an entity
query, it will give them lot of freedom to optimize their delta or full load
queries. One can even get creati
Another feature missing in DIH is ability to pass parameters into your
queries. If one could pass a named or positional parameter for an entity
query, it will give them lot of freedom to optimize their delta or full load
queries. One can even get creative with entity and delta queries that can
take
On 17.09.2010, at 05:40, Lance Norskog wrote:
> Database optimization is not like program optimization- it is wildly
> unpredictable.
well an RDBMS that cannot handle true != false as a NOP during the planning
stage doesn't even do basics in optimization.
But this approach is so much more eff
Database optimization is not like program optimization- it is wildly
unpredictable.
What bugs me about the delta approach is using the last time DIH ran,
rather than a timestamp from the DB. Oh well. Also, with SOLR-1499 you
can query Solr directly to see what it has.
Lukas Kahwe Smith wrote
Hi,
I think i have mentioned this approach before on this list, but I really think
that the deltaQuery approach which is currently explained as the "way to do
updates" is far from ideal. It seems to add a lot of redundant queries.
I therefore propose to merge the initial import and delta querie
