the older branch that has newforms,
both of which have an impact on what I'm trying to do.
It's getting closer to being resolved, and it's down to your advice, so
thanks again.
--
View this message in context:
http://www.nabble.com/problems-getting-data-into-solr-index-tf39
On 20-Jun-07, at 6:38 AM, vanderkerkoff wrote:
Hello Mike, Brian
My brain is approcahing saturation point and I'm reading these two
opinoins
as opposing each other.
I'm sure I'm reading it incorrectly, but they seem to contradict
each other.
Are they?
solr.py takes unicode and enco
ascii codec and fail.
--
View this message in context: http://www.nabble.com/problems-
getting-data-into-solr-index-tf3915542.html#a11213488
Sent from the Solr - User mailing list archive at Nabble.com.
--
http://variogr.am/
[EMAIL PROTECTED]
default codec. If you end up with utf-8, it will try to convert to
> unicode using the ascii codec and fail.
>
--
View this message in context:
http://www.nabble.com/problems-getting-data-into-solr-index-tf3915542.html#a11213488
Sent from the Solr - User mailing list archive at Nabble.com.
On 18-Jun-07, at 6:27 AM, vanderkerkoff wrote:
Cheesr Mike, read the page, it's starting to get into my brian now.
Django was giving me unicode string, so I did some encoding and
decoding and
now the data is getting into solr, and it's simply not passing the
characters that are cuasing prob
27;optimise'
>
> You don't know what that is about do you?
>
> I'm still on solr1.1 as we were having trouble getting this sort of
> interaction to work with 1.2, not sure if it's related.
>
>
--
View this message in context:
http://www.nabble.com/pr
s is a bytestring
> u.encode('ascii', 'ignore') # assuming u is a unicode string
>
> -Mike
>
--
View this message in context:
http://www.nabble.com/problems-getting-data-into-solr-index-tf3915542.html#a11174969
Sent from the Solr - User mailing list archive at Nabble.com.
uot;shit" being copied and
pasted into your app, and what python datatype is handling it? I
suspect it is encoded somehow, which could be problematic. Is it
going through a web browser? How is it getting into mysql?
-MIke
--
View this message in context: http://www.nabble.com/p
> going through a web browser? How is it getting into mysql?
>
> -MIke
>
>
>
>
--
View this message in context:
http://www.nabble.com/problems-getting-data-into-solr-index-tf3915542.html#a11136156
Sent from the Solr - User mailing list archive at Nabble.com.
On 14-Jun-07, at 4:30 AM, vanderkerkoff wrote:
Hi Brian
I've now set the mysqldb to be default charset utf8, and everything
else is
utf8. collation etc etc.
I think I know what the problem is, and it's a really old one and I
feel
foolish now for not realising it earlier.
Our content p
solr.py in JIRA.
>
--
View this message in context:
http://www.nabble.com/problems-getting-data-into-solr-index-tf3915542.html#a8400
Sent from the Solr - User mailing list archive at Nabble.com.
tcat on solr's port
> nc -l -p 8983
> 3) send your update message from the client as you normally would
>
> -Yonik
>
>
--
View this message in context:
http://www.nabble.com/problems-getting-data-into-solr-index-tf3915542.html#a6020
Sent from the Solr - User mailing list archive at Nabble.com.
--
regards
jl
r update message from the client as you normally would
>
> -Yonik
>
>
--
View this message in context:
http://www.nabble.com/problems-getting-data-into-solr-index-tf3915542.html#a6020
Sent from the Solr - User mailing list archive at Nabble.com.
e you talk to solr,
> and just read the data from mysql and throw it to /dev/null you'd still
> see that message.
>
> http://wiki.wxpython.org/UnicodeDecodeError
>
>
> -Hoss
>
>
>
--
View this message in context:
http://www.nabble.com/problems-getting-data-into-solr-index-tf3915542.html#a5954
Sent from the Solr - User mailing list archive at Nabble.com.
On Jun 13, 2007, at 11:37 AM, vanderkerkoff wrote:
Hello everyone
I'm running solr1.1 and Jetty, I'm having problems looping through
a mysql
database with python and putting the data into the solr index.
Here's the error
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in
posit
: I'm running solr1.2 and Jetty, I'm having problems looping through a mysql
: database with python and putting the data into the solr index.
:
: Here's the error
:
: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 369:
: ordinal not in range(128)
I may be missing something h
>
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position
> 369: ordinal not in range(128)
>
What character is at position 369? make sure it is valid unicode...
Is there a simple way to tell solr to accept UTF8 characters?
Solr can accept UTF8 characters... check the utf8
On 6/13/07, vanderkerkoff <[EMAIL PROTECTED]> wrote:
I'm running solr1.2 and Jetty, I'm having problems looping through a mysql
database with python and putting the data into the solr index.
Here's the error
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 369:
ordinal not i
ers?
I've read about this topic on your site and on others, so far I'm more
confused than when I started.
--
View this message in context:
http://www.nabble.com/problems-getting-data-into-solr-index-tf3915542.html#a11102282
Sent from the Solr - User mailing list archive at Nabble.com.
19 matches
Mail list logo